You secure applications deployed to your Oracle Java Cloud Service instance through the capabilities of Oracle Cloud, Java EE standards and Oracle WebLogic Server
An Oracle Java Cloud Service instance includes an Oracle WebLogic Server domain, which is comprised of an Administration Server and one or more Managed Servers. A domain also defines a security realm that controls authentication, authorization, role mapping, credential mapping and security auditing across all of the servers in the domain. Java applications deployed to this WebLogic Server domain can be associated with security roles and policies that protect the applications against unauthorized access. WebLogic Server supports various security providers that assign an identity to the requesting user. By default, users, groups, roles and policies are all maintained in WebLogic Server’s embedded LDAP. If this default security configuration does not meet your requirements, you can modify the security realm or create a new one with any combination of security providers. For large production applications, Oracle recommends that you use a proper identity management system such as Oracle Identity Management instead of the embedded LDAP.
To provide the highest level of network security, Oracle Java Cloud Service implements an “access by exception” architecture. You must explicitly grant network access to your service instance for administrators, application users or other cloud services. By default, a service instance is accessible only through secure protocols like SSL and SSH, and only using specific ports. You’re also able to customize the default network security configuration to support different access rules and security policies.
To learn more about Oracle Java Cloud Service security see:
To learn more about the Java EE and WebLogic Server security architecture see:
To learn more about the security capabilities of an Oracle Coherence data grid see these topics in Securing Oracle Coherence: