Database Reference
In-Depth Information
its password. The
listCred()
command displays the updated key in the con-
sole:
Wls:offline>connect('<
userName
>','<
password
>', '<
host
>:<
adminPort
>')
wls:/[Domain]/serverConfig>
createCred
(map="oracle.wsm.security",key="basic-credential",user="owsm",password="welcome1",desc="Keystore key")
wls:/[Domain]/serverConfig>
updateCred
(map="oracle.wsm.security",key="basic-credentials",user="owsm",password="welcome123",desc="Update Password")
wls:/[Domain]/serverConfig>
listCred
(map="oracle.wsm.security",key="basic-credential")
Configuring custom authorization policies
Oracle SOA Suite 11g ships a set of preconfigured application role based au-
thorization policies that are available in the
system-jazn-data.xml
file.
However, there may be cases where you just want to create custom authoriza-
tion policies and map principles to them. Or, for instance, you may even think of
moving your file-based policy store to a database or an LDAP-based store. In
this section, you will see how we can perform both.
Changing default policy store
You may want to do away with a file-based policy store, which is less protected
and more prone to corruption, and have a more sophisticated mechanism to per-
sist application and system security policies in a database (with a preconfigured
schema) or an active directory. Follow the next steps to view the default policy
store and change it to an LDAP-based one:
1.
Log in to Oracle Enterprise Manager Fusion Middleware Control.
2.
Right-click on
soa-infra
and navigate to
SOA Infrastructure
|
Security
|
Ap-
plication Policies
.
3.
Under
Application Policies
|
Policy Store Provider
, you will notice that the
default policy store is an XML-based
system-jazn-data.xml
file.
