1. Version # Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Sponsored by the U.S. Department of Defense © 1999 by Carnegie Mellon University Delete this red box (from the title master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Enterprise JavaBeans. - page 1 EJB Security Management

2. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 2 Security Management Overview The enterprise bean class provider should not hard-code security policies and mechanisms into the business methods allows appropriate deployment for the operational environment of the enterprise The application assembler may define security roles for an application -semantic grouping of permissions method permissions for each security role -permission to invoke a specified group of methods

3. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 3 Security Management Overview - 2 Security Roles Method Permissions EJBEJB Bean Provider Application Assembler Deployer Users Groups System Admins

4. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 4 Bean Provider’s Responsibilities The bean provider should not implement security mechanisms or security policies in the enterprise beans’ business methods rely instead on the security mechanisms provided by the EJB Container It is possible, however, to programmatically access a Caller’s Security Context...

5. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 5 Programmatically Accessing a Caller’s Security Context Two methods allow the bean provider to access security information about the enterprise bean’s caller getCallerPrincipal isCallerInRole In general, security management should be enforced by the container the security API should is used infrequently

6. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 6 Declaring Security Roles Security roles are declared in the deployment descriptor... WombatPayroll com.wombat.PayrollBean This security role should be assigned to the employees allowed to update employees’ salaries. payroll …

7. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 7 Application Assembler’s Responsibilities Define security roles in the deployment descriptor Specify the methods of the remote and home interface that each security role is allowed to invoke Link declared security role references to security roles

8. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 8 Specifying Security Roles... Allows employees to access their own information employee Allowed to view/update payroll entries for employees payroll-department...

9. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 9 Method permissions employee WombatPayroll findByPrimaryKey WombatPayroll getEmployeeInfo WombatPayroll updateEmployeeInfo

10. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 10 Linking Security Role References to Security Roles... WombatPayroll com.wombat.PayrollBean This security role should be assigned to the employees allowed to update employees’ salaries. payroll payroll-department …

11. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 11 Deployer’s Responsibilities Ensures that an application is secure after it has been deployed in the operational environment Assigns principals and/or groups of principals used for managing security in the operational environment to defined security roles not specified in the EJB architecture! specific to that operational environment Can use the security view defined in the deployment descriptor merely as “hints”

12. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 12 EJB Container Provider’s Responsibilities The EJB container provider provides the implementation of the security infrastructure A security domain can be implemented, managed, and administered by the EJB Server e.g., the EJB Server may store X509 certificates The EJB specification does not define the scope of the security domain the scope may be defined by the boundaries of the application, EJB Server, operating system, network, or enterprise

13. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 13 System Administrator’s Responsibilities Typically responsible for creating a new user account adding a user to a user group removing a user from a user group removing or freezing a user account Security domain administration is beyond the scope of the EJB specification...

14. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 14 Proceed with Caution… Insecure Secure EJB Specification EIS EJB Server Vendor Threats

15. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 15 Summary The EJB architecture does not specify how an enterprise should implement its security architecture assignment of security roles to the operational environment’s security concepts is specific to the operational environment identification and authentication left to EJB Server vendor’s Security will be vendor specific for some time no plans to address problem in EJB 2.0

16. © 1999 by Carnegie Mellon University Version # Delete this red box (from the slide master) after creating all of your slides. Keep everything inside the “safe area” for correct display. Course or Lecture or Module Info. - page 16 References [1] Java Authentication and Authorization Service (JAAS) http://java.sun.com/security/jaas/. [2]Java Cryptography Extension (JCE) http://java.sun.com/security/JCE1.2/spec/apidoc/index.html