10 Security Integration

Whilst Oracle Utilities Application Framework applications provide a set of security facilities natively or via Oracle WebLogic, it is possible to augment the security with additional security features or security products.

LDAP Integration

By default, Oracle WebLogic includes an internal security repository that uses the Lightweight Directory Access Protocol (LDAP) to provide authentication facilities.

Note:

It also provides authorization services, but these are not typically utilized by the product.

It is possible to replace the internal security repository with another LDAP compliant security source.

To use an alternative source as a security repository the following process must be used:

Oracle WebLogic must be configured to use the external LDAP security source for authentication. Refer to the documentation provided with Oracle WebLogic for more details. For Oracle WebLogic customers, refer to the Configuring LDAP Authentication Providers section of the Oracle Fusion Middleware Administering Security Oracle WebLogic Server guide.

The product LDAP import feature can be used to initially populate the authorization model from the LDAP source as outlined in the Technical Best Practices For Oracle Utilities Application Framework Based Products (KB679040) document available from My Oracle Support.

Note:

Whilst LDAP sources are the most common security repository, it is possible to use alternative security authentication sources as supported by Oracle WebLogic. Refer to the documentation provided with Oracle WebLogic for more details.

Single Sign On Integration

One of the common security integrations is the ability to implement Single Sign On with your application. This enables end users to access the product minimizing the need to re- authenticate each time.

Oracle WebLogic in association with other technologies can be configured to support Single Sign On. For more details refer to the Technical Best Practices For Oracle Utilities Application Framework Based Products (KB679040) document available from My Oracle Support.

Kerberos Support

Single Sign-On (SSO) with Microsoft clients allows cross-platform authentication between Web applications running in Oracle WebLogic and .NET Web service clients or browser clients (for example, Microsoft Internet Explorer) in a Microsoft domain. The Microsoft clients must use Windows authentication based on the Simple and Protected Negotiate (SPNEGO) mechanism.

Refer to Configuring Single Sign-On with Microsoft Clients for details of configuring Oracle WebLogic to use Kerberos.

Oracle Identity Management Suite Integration

Oracle offers a comprehensive set of security products as part of the Oracle Identity Management Suite that can be used to augment the security setup at your site. The product can be integrated with the following components of Oracle Identity Management Suite:

Component Description
Oracle Identity Manager Oracle Identity Manager can be used to centralize user provisioning to the product, password rule management and identity administration.
Oracle Access Manager Oracle Access Manager can be used to provide authentication, single sign on, access controls and user tracking.
Oracle Adaptive Access Manager Oracle Adaptive Access Manager can be used to provide fraud tracking and multi-faceted authentication.
Oracle Virtual Directory Oracle Virtual Directory can be used to provide virtualized LDAP security access to LDAP and non-LDAP security sources.
Oracle Internet Directory Oracle Internet Directory can be used as a LDAP security store.

Refer to the Technical Best Practices For Oracle Utilities Application Framework Based Products (KB679040) document available from My Oracle Support for more information.

OAuth2 Support

Note:

For customers using OAuth2 for Federated Security, refer to the dedicated section in this guide for detailed instructions.

OAuth2 is supported for delegated access to API's within the product. From the configuration perspective the following is required for Oauth2:

  • The CLIENT-CERT setting should be specified for security in the product. This indicates that the security is coming from an external source to the domain.
  • Configure Oracle WebLogic domain security realm to support OAuth2 using the instructions provided with the relevant version of Oracle WebLogic.
  • If you are using a service provider like Oracle Identity Suite or Oracle Access Manager in association with Oracle WebLogic, then refer to the documentation provided with those products for domain specific setup instructions.
  • If you are using a third-party provider in association with Oracle WebLogic, refer to the documentation provided with that provider with additional setup instructions.