1.4 Application Server Security

This topic describes about application server security.

Refer to the Oracle Web Logic Security specification document for make the environment more safer and secure.

Oracle Banking Cash Management support the following authentication schemes for the online web application.

• Standard LDAP Directory (e.g., OUD/AD/Embedded Weblogic)
• SSO with OAM (Oracle Access Manager – Part of the Oracle Identity Management Suite)
• SAML assertions with a Service Provider protecting the resource and an Identity Provider.

Oracle Banking Cash Management Solution supports the following authentication scheme for the API layer.

• OAuth (CLIENT CREDENTIALS) with OAM
• OAuth (CLIENT CREDENTIALS) without OAM

In case the customer does not have OAM, they can use OAUTH without OAM or it is expected that the customer has an enterprise API Management Layer that protects Oracle Banking Cash Management API layer with the same controls (i.e., OAuth)

Support for SSL (Secure Transformation of Data)

The Oracle Banking Cash Management should be configured that all HTTP connections to the application are over SSL/TLS. In other words, all HTTP traffic in the clear will be prohibited; only HTTPS traffic will be allowed. It is highly recommended to enable this option in a production environment, especially when WebLogic Server acts as the SSL terminator.