Web Application Access Control with Java SE Security

Transcription

1 Web Application Access Control with Java SE Security Java Forum Stuttgart 2009 Jürgen Groothues Stuttgart,

2 Agenda 1. Access Control Basics 2. The Java Authentication and Authorization Service (JAAS) 3. Enhancement and Application of JAAS 4. Role-Based Access Control 5. Instance-Based Access Control 6. Sample Application: A Personal Health Record 2

3 Access Control Basics Action Subject Access Control Resource Environment Subject: A user, system, etc. Resource: A file, printer, domain object, etc. Action: An operation on a resource (read, print, create, etc.) Environment: Access control relevant attributes not available from Subject, Action or Resource (time, location, ) Access Control: Controls performing an Action in accordance with a Policy 3

4 Access Control Architecture 1. Business request PEP 6. Business request Subject 2. Access request 5. Access decision Resource PDP 3. Attributes (optional) 4. Policy Environment PEP: Policy Enforcement Point PDP: Policy Decision Point PAP: Policy Administration Point PAP Policy Store 4

5 Agenda 1. Access Control Basics 2. The Java Authentication and Authorization Service (JAAS) 3. Enhancement and Application of JAAS 4. Role-Based Access Control 5. Instance-Based Access Control 6. Sample Application: A Personal Health Record 5

6 Limitations of JEE Security With the declarative JEE security model, it is difficult to change security policies when new requirements arise The declarative model limits the expressiveness of security policies Only one authentication method per application allowed Supports only limited set of authentication methods 6

7 Java Authentication and Authorization Service (JAAS) Originally, Java SE Authorization was based exclusively on the code accessing resources and authentication was based on digital signatures applied to the code JAAS was designed to address this shortcoming and is part of Java SE since V. 1.4 JAAS authentication is an implementation of the Pluggable Authentication Module (PAM) framework and allows applications to authenticate independently from the underlying technology (user/password, certificate, ) JAAS authorization allows access control based on who is executing the code 7

8 JAAS Authentication API javax.security.auth.login.logincontext login() throws javax.security.auth.login.loginexception JAAS Authentication javax.security.auth.spi.loginmodule JAAS Configuration SPI initialize(subject s, CallbackHandler c, Map sharedstate, Map options); login() throws LoginException; commit() throws LoginException; abort() throws LoginException; logout() throws LoginException; 8

9 JAAS Authorization API java.security.accesscontroller checkpermission(java.security.permission) throws java.security.accesscontrolexception JAAS Authorization java.security.policy implies(java.security.protectiondomain, java.security.permission) SPI Permission: encapsulates access control relevant attributes of Action and Resource AccessControlException: thrown if access to Resource is denied ProtectionDomain: provides Subject 9

10 Agenda 1. Access Control Basics 2. The Java Authentication and Authorization Service (JAAS) 3. Enhancement and Application of JAAS 4. Role-Based Access Control 5. Instance-Based Access Control 6. Sample Application: A Personal Health Record 10

11 Application of JAAS Authentication Servlet Filter Servlet Filter Servlet Filter Servlet Filter FormLogin Filter BasicLogin Filter CertificateLogin Filter PinLogin Filter ServletFilter-driven Enforcement LoginContext JAAS Authentication LoginModule JAAS Configuration DefaultLoginModule User Store Pluggable Authenticator 11

12 Subject and Principals A successful authenticated subject is represented in Java by a javax.security.auth.subject instance A subject is associated with identities. In Java an identity is represented by the java.security.principal interface An application provides Principal implementations javax.security.auth.subject * java.security.principal UserPrincipal RolePrincipal 12

13 Application of JAAS Authorization Subject AccessController Security Annotation Framework (SAF) Resource Annotation-driven Enforcement JAAS Authorization Policy Access Decision Framework Extensible Access Decision 13

14 Security Annotation Framework (SAF) 1 1 Subject Spring AOP AspectJ RT Spring AOP Proxy 2 Method Interceptor CT Enhanced Bytecode 2 AspectJ Advice 4 Domain Object 4 Spring Bean Resource Resource RT Created at runtime SAF Access Manager CT Created at compile time 3 JAAS Adapter 3 14

15 SAF Service Annotations public interface RecordService public Set<Record> findall(); } public Record create (@Secure (SecureAction.CREATE) Record record); 15

16 SAF Domain Object public class Record { private Set<Medication> medications; (SecureAction.UPDATE) public void addmedication(medication medication) { medications.add(medication); }... 16

17 Access Decision Framework 1 java.security. Policy 1 * AccessDecision Voter AccessPolicy AccessDecision Combiner Product Product AccessDecision Combiner Product AccessDecision Voter A Product AccessDecision Voter B use via runtime configuration implements extends use 17

18 Enabling JAAS in a Web Application A JEE-compliant Web Application Server (WAS) is required to support JAAS However, the JEE specification does not require a WAS to use JAAS as its own authentication and authorization mechanism JAAS has to be enabled by the web application itself: Set the JAAS policy during application startup, i.e. call java.security.policy.setpolicy(custompolicy) in the ContextListener Use one (or more) JAAS authentication servlet filter/s Use a JAAS authorization servlet filter that adds a Subject to the JAAS access control context (i.e. call javax.security.auth.subject.doasprivileged( ) request JAAS Authentication Filter request JAAS Authorization Filter request Servlet e.g. FormLoginFilter, PinLoginFilter, etc DoAsPrivilegedFilter 18

19 Agenda 1. Access Control Basics 2. The Java Authentication and Authorization Service (JAAS) 3. Enhancement and Application of JAAS 4. Role-Based Access Control 5. Instance-Based Access Control 6. Sample Application: A Personal Health Record 19

20 Role-Based Access Control (RBAC) P1 P2 P3 Role A Role B Role C P4 JAAS Subject Bob : Role Assignment Bob Principal Bob Permission P4 Pn Permission n Permission Assignment Role A Role B Role C P1 - P2,P3 Effective Permissions for Subject Bob : P1,P2,P3,P4 20

21 Hierarchical Role-Based Access Control (HRBAC) User P1 P4 P2 Physician Professional Pharmacist Non- Professional P3 JAAS Subject Bob : Principal Permission Bob - Physician P4 Professional P2 User P1 Bob Effective Permissions for Subject Bob : P1,P2,P4 Pn Permission n Permission Assignment Parent Role Assignment 21

22 Principal Provider Pattern LoginContext JAAS Authentication LoginModule PrincipalProvider * JAAS Configuration DefaultLoginModule Composite PrincipalProvider Product Role PrincipalProvider Organization PrincipalProvider use via JAAS configuration implements use 22

23 Agenda 1. Access Control Basics 2. The Java Authentication and Authorization Service (JAAS) 3. Enhancement and Application of JAAS 4. Role-Based Access Control 5. Instance-Based Access Control 6. Sample Application: A Personal Health Record 23

24 Instance-Based Access Control (IBAC) Instances of domain objects are secured resources Access decisions are based on the state of the instances :Record owner= Sue :Record owner= Bob :Record owner= Alice :Record owner= Paul :Record owner= No Access on other Records Policy: Bob has access on Records where owner = Alice or Bob Bob 24

25 Annotation-Driven public class Record private String owner; }... The PEP extracts all security relevant attributes from the domain object instance and puts them into a java.security.permission implementation. 25

26 Agenda 1. Access Control Basics 2. The Java Authentication and Authorization Service (JAAS) 3. Enhancement and Application of JAAS 4. Role-Based Access Control 5. Instance-Based Access Control 6. Sample Application: A Personal Health Record 26

27 Sample Application Domain Model Personal Health Record User Management Record owner 1 User * * Medication Observation * Role * Use Cases - Create a new user with roles and an associated new record - Grant access rights to a user - Add medications and observations to a record 27

28 Sample Application Technology Libraries: Testing Build Platform Java SE 6 Spring IOC / AOP / MVC V. 2.5 Security Annotation Framework (SAF) V. 0.9 Servlets V. 2.5 AspectJ V. 1.6 JUnit V. 4.4 EasyMock V.2.4 Maven V. 2.0 Tomcat V

29 Resources Java SE Security Security Annotation Platform (SAF) OASIS extensible Access Control Markup Language (XACML) Enterprise Java Security: Building Secure J2EE Applications by Marco Pistoia et al., Addison Wesley, 2004 Creative Commons Icons 29

30 Contact InterComponentWare AG Jürgen Groothues Industriestraße Walldorf, Germany