Management Tools Oracle Fusion Middleware Online Documentation Library

About Oracle Platform Security Services Scenarios 4-5 For details about managing Oracle Fusion Middleware on WebSphere Application Server, see Oracle Fusion Middleware Third-Party Application Server Guide. Common Scenario 1 This scenario describes a Java EE application during development. Authentication: The application uses the Default Authenticator, typical in development environments. Authorization: The policy and credential stores are file-based. Variation: The application uses the WebLogic support for SSO and Java EE security. For details about WebLogic support for SSO, see section Configuring Single Sign-On with Web Browsers and HTTP Clients in Oracle Fusion Middleware Securing Oracle WebLogic Server. Common Scenario 2 This scenario describes a Java EE application during development. Authentication: The application uses the Default Authenticator, typical in development environments. Authorization: The policy and credential stores are LDAP-based using the services of the same instance of an Oracle Internet Directory LDAP server. Variation: JAAS is enabled and policies include permissions for the anonymous and the authenticated roles. For details about configuring support for the anonymous and authenticated roles, see Section 2.3, The Authenticated Role, and Section 2.4, The Anonymous User and Role. Common Scenario 3 This scenario describes a Java EE application during development. Authentication: The application uses the Default Authenticator, typical in development environments. Authorization: The policy and credential stores are LDAP-based using the services of the same instance of an Oracle Internet Directory LDAP server. Variation: The application uses Java EE security, JAAS is enabled, and policies include permissions for the anonymous and the authenticated role. It also uses the Credential Store Framework CSF APIs to query, retrieve, and manage policies. For details about configuring support for the anonymous and authenticated roles, see Section 2.3, The Authenticated Role, and Section 2.4, The Anonymous User and Role. For details about CSF APIs, see Section 24.1, About the Credential Store Framework API.

4.5 Other Scenarios

The following scenarios differ from the common scenarios in that the application uses an authenticator other than the DefaultAuthenticator typically used in the application development phase or some API to access security data. 4-6 Oracle Fusion Middleware Application Security Guide Scenario 4 Authentication: The application uses an LDAP authenticator other than the DefaultAuthenticator. Authorization: Both, the policy and credential use the same Oracle Internet Directory LDAP-based store. Variation: The application uses the User and Role API to access user profiles in the DB and the Credential Store Framework CSF APIs to access credentials. For details about User and Role API, see Chapter 25, Developing with the User and Role API. For details about CSF APIs, see Section 24.1, About the Credential Store Framework API. Scenario 5 Authentication: The application uses the Oracle Internet Directory LDAP authenticator, typical in test and production environments. Authorization: The policy and credential stores are file-based and packaged with the application. These data is automatically mapped to domain security data at deployment. Variation: Post-deployment, the policy and credential stores are reassociated to an LDAP-based store configured through one-way SSL transmission channel. For details about automatic migration of application security data at deployment, see Section 8.6, Migrating the OPSS Security Store. For details about reassociation, see Section 8.5, Reassociating the OPSS Security Store. For details about SSL configuration and related topics, see the following: ■ Section Configuring SSL in Oracle Fusion Middleware Securing Oracle WebLogic Server. ■ Oracle Fusion Middleware Administrators Guide. ■ Section Set up SSL in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help. ■ Section Using SSL Authentication in Java Clients in Oracle Fusion Middleware Programming Security for Oracle WebLogic Server. Scenario 6 This scenario describes a Java SE application using OPPS APIs. Authentication: The application the LoginService API. Authorization: The application uses the method CheckPermission. In addition, the application uses the User and Role API to query attributes into the domain authenticator, and the Credential Store Framework API to query the credential store. Part II Part II Basic OPSS Administration This part describes basic OPSS administration features in the following chapters: ■ Chapter 5, Security Administration ■ Chapter 6, Deploying Secure Applications