What's the point of JAAS if I have to write my own {whatever}LoginModule and everything else?
The Java Authentication and Authorization Service (JAAS) API supplies user authentication and authorization services for Java applications. Ambari adds the following settings to the file. (Note: serviceName="kafka" is required for connections from other brokers.)
We can use JAAS for two purposes: Authentication: Identifying the entity that is currently running the code. Authorization: Once authenticated, ensure that this entity has the required access control rights or permissions to execute sensitive code.
JAAS authentication is performed in a pluggable fashion, so applications can remain independent from underlying authentication technologies. A system administrator determines the authentication technologies, or LoginModules, to be used for each application and configures them in a login Configuration.
The Java Authentication and Authorization Service (JAAS) is a set of application program interfaces (APIs) that can determine the identity of a user or computer attempting to run Java code and ensure that the entity has the right to execute the functions requested.
JAAS provides an abstraction layer between your application and the underlying authentication mechanism. Therefore, you could change the authentication mechanism used by your application without having to change any of your application code.
Well that is the beauty of it really..
We used JAAS in a big mortgage application system, and while we used a LoginModule based on properties, the big mortage bank used an own implemented LoginModule based on active directory, without we ever having to change something in code.
Just like with any other standard you get portability, plugability, and extensibility for free (or almost for free).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With