[ 
https://issues.apache.org/jira/browse/NIFI-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011696#comment-15011696
 ] 

ASF subversion and git services commented on NIFI-655:
------------------------------------------------------

Commit 7d04dfeac012307201e84dd00883dd6a79e6e2cc in nifi's branch 
refs/heads/NIFI-655 from Andy LoPresto
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7d04dfe ]

NIFI-655. - Changed issuer field to use FQ class name because some classes 
return an empty string for getSimpleName(). - Finished refactoring JWT logic 
from request parsing logic in JwtService. - Updated AccessResource and 
JwtAuthenticationFilter to call new JwtService methods decoupled from request 
header parsing. - Added extensive unit tests for JWT logic.

Signed-off-by: Matt Gilman <matt.c.gil...@gmail.com>


> Provide support for multiple authentication mechanisms
> ------------------------------------------------------
>
>                 Key: NIFI-655
>                 URL: https://issues.apache.org/jira/browse/NIFI-655
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Configuration, Core Framework, Core UI, Documentation & 
> Website
>            Reporter: Mark Payne
>            Assignee: Matt Gilman
>             Fix For: 0.4.0
>
>
> NiFi provides a pluggable authorization mechanism but authentication is done 
> only via browser certificates. We should offer support for multiple 
> authentication mechanisms. A feature proposal has been created [1].
> Important implementations to support include Active Directory, LDAP, and 
> Kerberos.
> [1] https://cwiki.apache.org/confluence/display/NIFI/Pluggable+Authentication



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to