Database Reference
In-Depth Information
By now, you must have realized that security policies don't work all by them-
selves. Defining security mechanisms through policies provides ease and flex-
ibility to use them as reusable services that can be plugged on and off at will.
As discussed above, they need the infrastructure to be set up first to provide the
required implementation support. In the coming sections, you will learn in detail
various methods to configure the necessary changes to your infrastructure so as
to set up a backbone for the OWSM-based security framework to work.
Oracle Platform Security Services
Oracle Platform Security Services (OPSS)
is the default out-of-the-box secur-
ity configuration that OWSM relies on for most password protected and identity
related services. The OPSS architecture externalizes security to let application
developers focus on business logic and system administrators to manage secur-
ity.
The following diagram shows the OPSS layered architecture that allows it to
support different security and identity systems without needing to change any-
thing at the application level:
At runtime, OWSM hooks to OPSS via the
jps-config.xml
file (located at
$DOMAIN_HOME/config/fmwconfig)
from the
jpsContext
element with
an attribute named
default
. An extract of
default jpsContext
in the
standard
jps-config.xml
looks like this:
