Log in to Fusion Middleware Control and navigate to Domain Security

Configuring the OPSS Security Store 8-17 access to entry by dn=userDN browse,add,delete by none access to attr= by dn=userDN search,read,write,compare by none where storeRootDN stands for a node typically the root node of the store, and userDN stands for the DN of the administrator data the same userDN that was entered to perform reassociation. 2. Use the Oracle Internet Directory utility ldapmodify to apply these specifications to the Oracle Internet Directory. Here is an example of an LDIF file specifying an ACL: dn: cn=jpsRootNode changetype: modify add: orclACI access to entry by dn=cn=myAdmin,cn=users,dc=us,dc=oracle,dc=com browse,add,delete by none access to attr= by dn=cn=myAdmin,cn=users,dc=us,dc=oracle,dc=com search,read,write,compare by none For more information about access control lists and the command ldapmodify, see chapter 18 in Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory.

8.5.2 Reassociating with the Script reassociateSecurityStore

The OPSS store can be reassociated with the OPSS script reassociateSecurityStore. For details, see Section 9.3.29, reassociateSecurityStore.

8.6 Migrating the OPSS Security Store

A domain includes one and only one policy store. Applications can specify their own policies, but these are stored as policies in the policy store when the application is deployed to a server. All applications deployed in a domain use a common policy store, the policy store. The policy store is logically partitioned in stripes, one for each application name specified in the file DOMAIN_HOMEconfigfmwconfigsystem-jazn-data.xml under the element applications. Migrating the OPSS security store consists in relocating the policy, credential, and key stores from one repository to another one. The source can be file-, LDAP-, or DB-based; the target can be LDAP- or DB-based. The OPSS binaries and the target policy store must have compatible versions; for details, see Section L.20, Incompatible Versions of Binaries and Policy Store. During application development, an application specifies its own policies, and these can be migrated to the OPSS security store when the application is deployed with Fusion Middleware Control. Policies can also be migrated manually; in addition, each application component can specify the use of anonymous user and role, authenticated role, and JAAS mode. The configuration of the policy store is performed by an administrator. These topics are explained in the following sections: ■ Migrating with Fusion Middleware Control ■ Migrating with the Script migrateSecurityStore