1. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Developing with JAAS Presented by Maciej Zawadzki mbz@urbancode.com

2. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. What is JAAS Java Authentication and Authorization Service Introduced as an optional package in J2SE 1.3 Integrated into J2SE 1.4 Implements a Java Pluggable Authentication Module (PAM) framework Access decisions are based on CodeSource and the user running the code

3. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Goals JAAS is an extensive and complicated library. The goals for this presentation are: –To give an overview JAAS and its constituent parts and illustrate how they all work together –Provide enough information that you will be able to decide when it is appropriate to use JAAS –Provide an introduction on how to use JAAS; code examples to help you get started

4. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Outline Introduction –What is JAAS –Authentication vs. Authorization –Subject –Principal Authentication Authorization

5. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Authentication vs. Authorization Authentication is the process of verifying the users’ identity. Typically this entails obtaining a user name and a password or some other credential from the user. Authorization is the process of verifying whether a user has access to protected resources.

6. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Overview of the Subject The Subject is a container for associated Principals, Public Credentials (public keys), and Private Credentials (passwords, private keys).

7. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Subject

8. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Principal A Principal identifies a Subject. The Subject can a person, a corporation, and application, etc. A single Subject may have many Principals that serve to identify the entity. For example, a user can have a user name principal, an employee id principal, social security number principal, etc.

9. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Obtaining a Specific Principal from a Subject Applications (and app. servers) typically adopt a convention stating that the Set of Principals on a Subject can only contain one instance of a particular Principal class.

10. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Outline Introduction Authentication Authorization

11. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Pluggable Authentication Modules An application using JAAS for authentication can remain independent of the underlying authentication technology.

12. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. LoginConfiguration File The default implementation parses a configuration file in the above format Configuration file specified via java.security.auth.login.config System parameter

13. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. LoginConfiguration Control Flags Required – The LoginModule is required to succeed. Regardless of success, authentication proceeds to next LoginModule Requisite – Is required to succeed. If succeeds, authentication proceeds. If fails, control returned. Sufficient – Not required to succeed. If suceeds, control returned. If fails, authentication proceeds. Optional – Not required to succeed. Regardless of success, authentication proceeds. Overall authentication succeeds if all Required and Requisite modules before a Sufficient module succeed. If not Required or Requisite modules are configured, then at least one Sufficient or Optional module must succeed.

14. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Authentication Overview 1.The application creates a LoginContext and calls login() 2.The LoginContext refers to the LoginConfiguration to set up the appropriate LoginModules 3.The LoginContext delegates the authentication to the LoginModules 4.The LoginModules use the CallbackHandler to communicate with the application

15. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Login Example

16. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Login Example Once the login succeeds we can get the principal from the LoginContext and get the authenticated Principals from the Subject.

17. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Creating a LoginContext The name parameter is used to retrieve the appropriate login Configuration If a login Configuration with the specified name is not found, a default entry with the name “ other ” is used. If there is no Configuration with the name “ other ”, a LoginException is thrown

18. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Creating a LoginContext The constructors without a CallbackHandler either: –Rely on the default CallbackHandler specified in the java.security file under property named auth.login.defaultCallbackHandler –Do not use a CallbackHandler and rely on the LoginModule s to have another means of obtaining the information Callers of a LoginContext constructor require an AuthPermission with target “ createLoginContext. ”

19. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Logging In Authentication occurs with a call to the login() method The login() method invokes all the configured LoginModules to perform authentication When authentication succeeds, the Subject can be retrieved using the getSubject() method The logout() method logs out the Subject and removes its authenticated Principal s NTLoginModule – Authenticates against Windows Security Domain

20. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. LoginModule Two-phase authentication: –login() is 1 st phase method –commit() and abort() are 2 nd phase methods

21. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. LoginModules in J2SE 1.4 JndiLoginModule – Authenticates against an LDAP tree Krb5LoginModule – Authenticates against a Kerberos domain UnixLoginModule – Authenticates against Unix security

22. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Custom LoginModule Example

23. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Callbacks javax.security.auth.callback.Callback Marker interface used to indicate a callback. Callbacks provide a means for the underlying authentication implementation to communicate with the application and obtains security data such as user name and password as well as provide information such as error and warning messages. Included callbacks: –NameCallback –PasswordCallback –TextOutputCallback –TextInputCallback –ChoiceCallback –ConfirmationCallback –LanguageCallback

24. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. CallbackHandler

25. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Custom CallbackHandler Example

26. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Custom LoginConfiguration javax.security.auth.login.Configuration is an abstract Class used to specify which LoginModule s should be used to Authenticate a user for a particular application

27. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Custom LoginConfiguration You can configure the security system to use your own Configuration implementation by specifying the login.configuration.provider property in the /lib/security/java.security file.

28. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Outline Introduction Authentication Authorization

29. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. CodeSource Based Authorization Before the integration of JAAS with Java security, authorization decisions were strictly based on the CodeSource A Trusted Library may be given access to sensitive resources while an Applet or another Library may have that access restricted.

30. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. CodeSource and Principal Based Authorization With the integration of JAAS and J2SE Security, authorization decisions can be made based on the CodeSource and the Principal. A Library may not have access privileges to resources when running without a User context or when being executed by User Bart, but when User Andy executes the Library those permissions may be granted.

31. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. CodeSource & ProtectionDomain The CodeSource of a piece of Java code is the URL location that the code was loaded from and the Certificates that we used to sign the code The ProtectionDomain is a holder for the CodeSource and a Principal Each class is assigned a ProtectionDomain upon being loaded. The Principal is null when the class is first loaded.

32. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. AccessControlContext – a Context for Authorization Decisions When making access decisions, the security system looks at every ProtectionDomain involved in the call. Access is granted only if every ProtectionDomain in the Context can have access. A less privileged PD can not gain privilege by calling a more privileged PD. And a more privileged PD must lose privilege when calling a less privileged PD. This is the principle of least privilege.

33. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Permission Permissions represent access to resources. All Permission object have a name. The meaning of the name parameter is implementation dependent. Typically the name identifies the resource to be accessed.

34. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Permission The implies() method is implementation dependent. A permission p1 implies permission p2 if the grant of p1 is also meant to grant p2. Additional parameter called actions can be used to identify the type of access to the resource allowed. New Permissions are subclassed from Permission or from one of its existing subclasses such as java.security.BasicPermission. A special permission exists to indicate unrestricted access to all resource: java.security.AllPermission

35. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Policy The mapping between PDs and associated Permissions is stored by the Policy. Policy is a singleton.

36. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Policy The default implementation of Policy accepts text based configuration in the above format Each grant entry is composed of an optional CodeSource, Signers, Principals, and a list of Permissions Default security policy is /lib/security/java.policy Can provide supplemental policy file location via –-Djava.security.policy= JVM parameter Can override the default policy file with: –-Djava.security.policy== JVM parameter

37. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. AccessController Your code would verify that the current context has a permission by creating a new instance of the permission in question and calling AccessController.checkPermission(p) ;

38. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. AccessController The AccessController embodies the access control algorithm. It obtains the current AccessControlContext, which has an array of PDs and then for each PD checks whether the PD has the requested permission.

39. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. AccessController

40. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. PrivilegedAction When a trusted library invokes a PrivilegedAction, the permissions of PDs in the call stack prior to the PrivilegedAction do not get checked.

41. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. PrivilegedAction Invoking a privileged action is done via a static method on the AccessController. PrivilegedExceptionAction can throw an Exception. Methods invoking a PrivilegedAction should not return references to resources.

42. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Associating a Subject with an Access Control Context To associate a Subject with the current execution context, one of the Subject.doAs(…) methods must be used.

43. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Custom Policy You can substitute your own Policy implementation for the default one in one of two ways: –At runtime by calling Policy.setPolicy() –By changing the value of policy.provider property in /lib/security/java.security The specified class name must point to a subclass of Policy, and The specified class must be in the boot classpath Example included (you must change the java.security property on your JRE)

44. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Downloads All source code is included on your CDs You can check http://www.urbancode.com/presentations/ for updates http://www.urbancode.com/presentations/

45. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Evaluations Please fill out your speaker evaluations and drop them off at the registration desk Please fill out the comments: –What was the best part of the presentation –What part put you most to sleep

46. Copyright  2002 Urbancode Software Development, Inc. All Rights Reserved. Thank you! Maciej Zawadzki mbz@urbancode.com