Pluggable Authentication

Goals

• Provide new authentication mechanisms inclusive of a foundational framework that allows specific authentication providers.  Best in class for this situation appears from a cursory standpoint to be JAAS
• Build the needed extensions and configuration to allow for multiple providers along the likes of LDAP, Kerberos, OAuth/OpenID Connect, etc.
• Extend the UI to provide a consistent user experience for interfacing with any of the various providers 

Background and strategic fit

Current security mechanisms are Spring based and heavily bound to exclusively a PKI powered system.  There has been wide community request for supporting of additional mechanisms as they look to provide integration of NiFi into existing enterprise facilities.  

Assumptions

Requirements

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Not Doing