Owie, The authentication model is not extension point at the moment. You are correct that the only means of authentication is certificate based. The authorization model is what is extensible. Basically the application will tell the AuthorityProvider who the user is and it provides what it is that they are allowed to do.
I am not sure how a pluggable authentication model would work within the context of NiFi but it's something that could certainly be considered. Adding direct support for another type of authentication like basic when a certificate is not present may also be a possibility. Matt On Fri, Mar 20, 2015 at 4:07 AM, owieboy <[email protected]> wrote: > When I first read in the admin guide that NiFi comes with authentication > feature I was expecting a HTTPS form based login page. After trying it for > myself, I found that it uses a mutual certificate authentication which I > read is more secured than the form-based scheme. > > If I want a form based login page, I guess I would have to implement it as > an extension. Unless there's already an available implementation for such > requirement and there's only lacking in the documentation. Please advice. > Thanks > > Owie > > > > -- > View this message in context: > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/NiFi-LDAP-Authentication-tp1007p1017.html > Sent from the Apache NiFi (incubating) Developer List mailing list archive > at Nabble.com. >
