Database Reference
In-Depth Information
Understanding
the
OWSM-based
policy
framework
in
Oracle
SOA
Suite 11g
OWSM lays the foundation to implement security through runtime enforcement
and declarative policy attachment for different types of use case scenarios.
For instance, OWSM has policies supporting
Security Assertion Markup Lan-
guage (SAML)
token profiles, Kerberos,
Web Service Security (WSS)
1.0/1.1,
and
Secure Socket Layer (SSL)
, allowing you to easily attach policies for se-
curity, auditing, and management of components, services, and references in a
composite as well as any standalone web services deployed to the infrastruc-
ture. It also provides consistency and ease of use in such a way that developers
can attach a particular security policy at design time and system administrators
can prepare the infrastructure for the policies to work. Security policies can be
attached to any web service-based client apart from all the artifacts in the ser-
vice composite assembly.
The policy framework is built using the
Web Services Policy (WS-Policy)
standard wherein each policy describes the capabilities and requirements of a
service such as whether and how a message must be secured, whether and
how a message must be delivered reliably, and so on. You can read about WS-
Policy Framework in more detail at
http://www.w3.org/Submission/WS-Policy/
.
Oracle SOA Suite 11g has support for the following types of security policies:
•
WS-Reliable Messaging:
These policies implement the WS-RM standard
over a wire-level protocol that allows guaranteed delivery of SOAP mes-
sages and can maintain the order of sequence in which a set of messages
are delivered.
•
Management:
Management policies log request, response, and fault mes-
sages to a message log. Management policies may include custom policies
and are useful to audit security implementations.
