Database Reference
In-Depth Information
A restart of the application to which the policies are attached
is required in order to activate the configuration changes.
This can be verified by either viewing the output from the
listWebServicePolicies()
command or locating the
new attached policy from Oracle Enterprise Manager Fusion
Middleware Control.
Customizing OWSM policies
Security management in most organizations is increasingly being tasked off from
developers and handed over to platform administrators. Up until now you have
learned how you can accomplish various facets of security policy administration
using Oracle Enterprise Manager Fusion Middleware Control.
You navigate to the attachment point and simply pick the policy you want and
the enforcement starts immediately. However, a policy is made up of multiple as-
sertions and is able to provide a more fine-grained level of control. For example,
all predefined security policies contain an instance of the logging assertion tem-
plate,
oracle/security_log_template
, to log the entire message before
and after the primary security assertion is executed. By default, the log assertion
is not enforced. You may need to modify a policy and enable this assertion in
cases where the logging assertion has to be asserted for debugging. It is recom-
mended not to change the original policy for your customizations, but to create
a similar one and then add, change, or remove specific assertions as needed.
Policy properties can be overridden by clicking on the
Create Like
button under
WebLogic Domain
|
Farm_[Domain_Name]
|
Web Services
|
Policies
dash-
board page from Oracle Enterprise Manager Fusion Middleware Control in order
to create a new policy template. Once a similar policy is created, you can define
your own name and validate it in the console itself. Clicking on the
Save
button
will persist the policy into the policy repository.
