To create an application role, click Create to display the Create Application Role

Managing the Policy Store 9-11 ■ listResourceActions ■ createEntitlement ■ getEntitlement ■ deleteEntitlement ■ addResourceToEntitlement ■ revokeResourceFromEntitlement ■ listEntitlements ■ grantEntitlement ■ revokeEntitlement ■ listEntitlement ■ listResourceTypes ■ reassociateSecurityStore All class names specified in the above scripts must be fully qualified path names. The argument appStripe refers to the application stripe typically, identical to the application name and identifies the subset of policies pertaining to a particular application. For important information about the authenticated and the anonymous roles and WLST scripts, see Section 9.5, Granting Policies to Anonymous and Authenticated Roles with WLST Scripts. For the correct usage of the application stripe in versioned applications, see Section 9.6, Application Stripe for Versioned Applications in WLST Scripts.

9.3.1 listAppStripes

The script listAppStripes lists application stripes. This script can be run in offline or online mode. When run in offline mode, a configuration file must be passed, and it lists the application stripes in the policy store referred to by the configuration in the default context of the passed configuration file. When run in online mode, a configuration file must not be passed, and it lists stripes in the policy store of the domain to which you connect. In any mode, if a regular expression is passed, it lists the application stripes with names that match the regular expression; otherwise, it lists all application stripes. If this command is used in offline mode after reassociating to a DB-based, the configuration file produced by the reassociation must be manually edited as described in Running listAppStripes after Reassociating to a DB-Based Store . Script Mode Syntax listAppStripes.py [-configFile configFileName] [-regularExpression aRegExp] Interactive Mode Syntax listAppStripes[configFile=configFileName] [, regularExpression=aRegExp] The meanings of the arguments are as follows: ■ configFile specifies the path to the OPSS configuration file. Optional. If specified, the script runs offline; the default context in the specified configuration 9-12 Oracle Fusion Middleware Application Security Guide file must not have a service instance reference to an identity store. If unspecified, the script runs online and it lists application stripes in the policy store. ■ regularExpression specifies the regular expression that stripe names returned should match. Optional. If unspecified, it matches all names. To match substrings, use the character . Examples of Use The following online invocation returns the list of application stripes in the policy store: listAppStripes.py The following offline invocation returns the list of application stripes in the policy store referenced in the default context of the specified configuration file: listAppStripes.py -configFile homemyFilesjps-config.xml The following online invocation returns the list of application stripes that contain the prefix App: listAppStripes.py -regularExpression App

9.3.1.1 Running listAppStripes after Reassociating to a DB-Based Store

The jps configuration file produced by the reassociation to a DB-based stored cannot be passed, as is, to the script listAppStripes when the script is run in offline mode. To run the script in offline mode in this scenario, the passed file must be first manually edited as described below. The following examples illustrate fragments of jps configuration files before and after reassociating to a DB-based OPSS security store, and the changes required on the file produced by the reassociation. Before Reassociation The following fragment illustrates the configuration of a file-based policy store before being reassociated to a DB-based store: serviceInstance name=policystore.xml provider=policystore.xml.provider location=.system-jazn-data.xml descriptionFile Based Policy Store Service Instancedescription serviceInstance jpsContext name=default serviceInstanceRef ref=credstore serviceInstanceRef ref=keystore serviceInstanceRef ref=policystore.xml serviceInstanceRef ref=audit serviceInstanceRef ref=idstore.ldap serviceInstanceRef ref=trust jpsContext After Reassociation The following fragment illustrates the configuration file generated by the reassociation of the above store to a DB-based store: propertySet name=props.db.1 property value=cn=soa_domain name=oracle.security.jps.farm.name property value=cn=jpsroot name=oracle.security.jps.ldap.root.name