This appendix documents OPSS system properties (set through the switch -D at server start) and configuration properties (set with elements <property> and <extendedProperty> in the configuration file jps-config.xml) in the following sections:
To manage server properties programmatically, use OPSS MBeans. For details and example, see Section E.2.3, "Programming with OPSS MBeans."
Note:
All OPSS configuration changes (manual or through JpsConfiguration MBean) require server restart to take effect.OPSS data domain changes do not require server restart to take effect. Data changes include modifying an application policy and creating, deleting, or updating a credential.
A system property that has been introduced or modified is not in effect until the server is restarted. In order to set a system property the administrator must edit the setDomainEnv.sh shell script and add the property to the environment variable EXTRA_JAVA_PROPERTIES in that script.
Table F-1 lists the Java system properties available with OPSS.
Table F-1 Java System Properties Used by OPSS
| Name | Description |
|---|---|
|
|
Notifies about a permission failure when the method JpsAuth.checkPermission is called inside a Subject.doAs block and the permission check fails. Note that setting jps.auth.debug or jps.auth.debug.verbose is not enough to get a failure notification in this case. |
|
Specifies the location of the OPSS policy file. |
|
|
|
Enables or disables the delegation of calls to JDK API AccessController.checkPermission, which reduces runtime and debugging overhead. Default value: FALSE. |
|
|
Controls server logging output. Default value: FALSE. For details, see Section J.1.2.1, "jps.auth.debug." See also java.security.debug. |
|
|
Controls server logging output. Default value: FALSE. For details, see Section J.1.2.2, "jps.auth.debug.verbose." See also java.security.debug. |
|
|
Enables or disables the caching of a subject's protection domain. Default value: FALSE. |
|
|
Enables or disables the evaluation of a subject's protection domain when a check permission is triggered. Default value: FALSE. |
|
|
Enables or disables the migration of policies and credentials for applications deployed in a WebLogic Server. Set to TRUE to disable the migration of application policies and credentials for all applications deployed in the server regardless of the particular application settings in the application file weblogic-application.xml. Default value: FALSE. |
|
Enables or disables the hybrid mode. The hybrid mode is used to facilitate the transition from the Sun java.security.Policy to the OPSS Java PolicyProvider. When the hybrid mode is enabled, the OPSS Java Policy Provider reads from both files, java.policy and system-jazn-data.xml. Default value: TRUE. |
|
|
|
Specifies the path to the domain configuration files |
This section describes the properties of various instances in the following sections:
Table F-2 lists the properties of LDAP-based policy store instances.
Table F-2 LDAP-Based Policy Store Properties
| Name | Description |
|---|---|
|
|
The key for the password credentials to access the LDAP policy store, stored in the CSF store. Valid only in J2EE applications. No default value. When the policy store is migrated from a file-based to an LDAP-base store, the out-of-the-box value in the jps-config.xml file is |
|
|
The map for the password credentials to access the LDAP policy store, stored in the CSF store. Valid only in J2EE and J2SE applications. Default value: BOOTSTRAP_JPS. |
|
|
The RDN format of the domain node in the LDAP policy store. Valid in J2EE and J2SE applications. No default value. |
|
|
The RDN format of the root node in the LDAP policy store. Valid in J2EE and J2SE applications. No default value. |
|
|
The URL of the LDAP policy store, with the format Valid in J2EE and J2SE applications. No default value. |
|
|
The type of the LDAP policy store. Valid in J2EE and J2SE applications. No default value. |
|
|
The type of the role member cache. Valid only in J2EE applications. Valid values:
Default value: STATIC. |
|
|
The type of strategy used in the role member cache. Valid only in J2EE applications. Valid values:
Default value: FIFO. |
|
|
The size of the role member cache. Valid only in J2EE applications. Default value: 1000. |
|
|
Enables or disables the policy lazy load. Valid only in J2EE applications. Default value: TRUE. |
|
|
The type of strategy used in the permission cache. Valid only in J2EE applications.
Default value: PERMISSION_FIFO. |
|
|
The size of the permission cache. Valid only in J2EE applications. Default value: 1000. |
|
|
Enables or disables the refresh of the policy store. Valid only in J2EE applications. Default value: TRUE. |
|
|
The time, in milliseconds, after which the policy store is refreshed. Valid only in J2EE applications. Default value: 43200000 (12 hours). |
|
|
The interval, in milliseconds, at which the policy store is polled for changes. Valid only in J2EE applications. Default value: 600000. |
|
|
The number of user's permissions after which the permission cache is invalidated. Valid only in J2EE applications. Default value: 50. |
|
|
This property controls the way the ApplicationRole membership cache is created. If set to TRUE, the cache is created at server startup; otherwise, it is created on demand (lazy loading). Set to TRUE when the number of users and groups is significantly higher than the number of application roles; set to FALSE otherwise, that is, when the number of application roles is very high. Valid only in J2EE applications. Default value: FALSE. |
The following fragment illustrates the configuration of the above properties for a J2EE application:
<serviceInstance provider="ldap.policystore.provider" name="policystore.ldap">
<property value="OID" name="policystore.type"/>
<property value="bootstrap" name="bootstrap.security.principal.key"/>
<property value="cn=wls-jrfServer" name="oracle.security.jps.farm.name"/>
<property value="cn=jpsTestNode" name="oracle.security.jps.ldap.root.name"/>
<property value="ldap://stadk06.us.oracle.com:3060" name="ldap.url"/>
<property value="STATIC" name="oracle.security.jps.policystore.rolemember.cache.type"/>
<property value="FIFO" name="oracle.security.jps.policystore.rolemember.cache.strategy"/>
<property value="1000" name="oracle.security.jps.policystore.rolemember.cache.size"/>
<property value="true" name="oracle.security.jps.policystore.policy.lazy.load.enable"/>
<property value="PERMISSION_FIFO" name="oracle.security.jps.policystore.policy.cache.strategy"/>
<property value="1000" name="oracle.security.jps.policystore.policy.cache.size"/>
<property value="true" name="oracle.security.jps.policystore.refresh.enable"/>
<property value="43200000" name="oracle.security.jps.policystore.refresh.purge.timeout"/>
<property value="600000" name="oracle.security.jps.ldap.policystore.refresh.interval"/>
</serviceInstance>
The following fragment illustrates the configuration of the above properties for a J2SE application:
<serviceInstance name="policystore.oid" provider="policy.oid"> <property value="OID" name="policystore.type"/> <property value="bootstrap" name="bootstrap.security.principal.key"/> <property name="ldap.url" value="ldap://sttt:3060"/> <property name="oracle.security.jps.ldap.root.name" value="cn=jpsNode"/> <property name="oracle.security.jps.farm.name" value="cn=domain1"/> </serviceInstance>
Table F-3 lists the reload/refresh properties of LDAP-based policy store instances.
Table F-3 LDAP-Based Policy Store Reload/Refresh Properties
| Name | Description |
|---|---|
|
|
Enables or disables the refresh of the cache. Default value: TRUE. |
|
|
The time, in milliseconds, after which the existing cache will be purged and the whole cache will be reloaded. Default value: 43200000 (12 hours). |
|
|
The interval, in milliseconds, at which the policies will be scanned for any change in LDAP store such as additions, deletions, or updates. Default value: 43200000 (12 hours). |
|
|
The load factor for the cache object. Default value: 0.7. |
|
|
The initial default capacity, in MB, of the cache. Default value: 20. |
Table F-4 lists the properties of LDAP-based credential store instances.
Table F-4 LDAP-Based Credential Store Properties
| Name | Description |
|---|---|
|
|
The key for the password credentials to access the LDAP credential store, stored in the CSF store. Valid only in J2EE applications. No default value. When the policy store is migrated from a file-based to an LDAP-base store, the out-of-the-box value in the jps-config.xml file is |
|
|
The map for the password credentials to access the LDAP credential store, stored in the CSF store. Valid only in J2EE and J2SE applications. Default value in J2EE applications: BOOTSTRAP_JPS. |
|
|
The RDN format of the domain node in the LDAP credential store. Valid in J2SE and J2EE applications. No default value. |
|
|
The RDN format of the root node in the LDAP policy store. Valid in J2SE and J2EE applications. No default value. |
|
|
The URL of the LDAP credential store, with the format Valid in J2SE and J2EE applications. No default value. |
The following fragment illustrates the configuration of the above properties for a J2EE application:
<serviceInstance provider="ldap.credentialstore.provider" name="credstore.ldap">
<property value="bootstrap" name="bootstrap.security.principal.key"/>
<property value="cn=wls-jrfServer" name="oracle.security.jps.farm.name"/>
<property value="cn=jpsTestNode" name="oracle.security.jps.ldap.root.name"/>
<property value="ldap://stttt.us.oracle.com:3060" name="ldap.url"/>
</serviceInstance>
Table F-5 lists the properties of LDAP-based identity store instances.
Table F-5 LDAP-Based Identity Store Properties
The following fragment illustrates the configuration of the above properties:
<serviceInstance name="idstore.ldap" provider="idstore.ldap.provider">
<property name="idstore.type" value="OID"/>
<property name="security.principal.alias" value="MAP_NAME"/>
<property name="security.principal.key" value="KEY_NAME"/>
<property name="ldap.url" value="ldap://stadk06:3060"/>
<extendedProperty>
<name>user.search.bases</name>
<values>
<value>cn=users,dc=us,dc=oracle,dc=com</value>
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases</name>
<values>
<value>cn=groups,dc=us,dc=oracle,dc=com</value>
</values>
</extendedProperty>
</serviceInstance>
Table F-6 lists generic properties of LDAP-based stores that can be specified in service instances. In the case of an LDAP-based identity store service instance, to ensure that the User and Role API picks up the connection pool properties when it is using the JNDI connection factory, the identity store service instance must include the following property:
<property name="INITIAL_CONTEXT_FACTORY" value="com.sun.jndi.ldap.LdapCtxFactory"/>
Table F-6 Generic LDAP Properties
| Name | Description |
|---|---|
|
|
Specifies the type of LDAP connection that the JNDI connection pool uses. Values: none, simple, and DIGEST-MD5. Default: simple. |
|
|
Specifies the maximum number of connections in the LDAP connection pool. Values: integer Example: 30 |
|
|
Specifies the minimum number of connections in the LDAP connection pool. Values: integer Example: 5 |
|
|
Specifies the protocol to use for the LDAP connection. Values: plain, ssl. Default: plain. |
|
|
Specifies the connection pool to use. Values: JNDI, IDM. Default: JNDI. |
|
|
Specifies the number of milliseconds that an idle connection can remain in the pool; after timeout, the connection is closed and removed from the pool. Values: an integer in string form. Defaults to 300000 (5 minutes) |
|
|
Specifies the maximum number of retry attempts if there are problems with the LDAP connection. Values: integer Example: 5 |
The following fragment illustrates the configuration of the above properties:
<jpsConfig ... >
...
<!-- These are various JPS common properties used for LDAP operations -->
<property name="oracle.security.jps.farm.name" value="cn=OracleFarmContainer"/>
<property name="oracle.security.jps.ldap.root.name"
value="cn=OracleJpsContainer"/>
<property name="oracle.security.jps.ldap.max.retry" value="5"/>
...
</jpsConfig>
Table F-7 lists the properties of anonymous users, anonymous roles, and authenticated roles. Some of them may also be used to configure the anonymous service or an identity store login module.
Table F-7 Anonymous and Authenticated Roles Properties
| Name | Description |
|---|---|
|
|
Provides a description of the anonymous role. Example: |
|
|
Specifies the principal name of the anonymous role. Default value: |
|
|
Specifies the name of the anonymous role. Default value: |
|
|
Specifies the principal name of the anonymous user. Default value: |
|
|
Provides a description of the authenticated role. Example: |
|
|
Specifies the principal name of the role used for authenticated users. Default value: |
|
|
Specifies the name of the authenticated role. Default value: |
|
|
Specifies whether the anonymous role should be removed from the subject after a user is authenticated. Default value: FALSE. |
Table F-8 lists the properties of the policy provider framework.
Table F-8 Policy Provider Framework Properties
| Name | Description |
|---|---|
|
|
Specifies the fully qualified class name of the permission that extends PolicyDelegationPermission. This is used in runtime for custom provider delegation by the policy framework. By default, this property is not specified in |
|
|
Specifies the attribute of a static LDAP role object that specifies the distinguished names (DNs) of the members of the role. Example: |
|
|
Specifies the name of the LDAP attribute that uniquely identifies the name of the role. Example: |
|
|
Specifies LDAP schema object classes that represent a role. If specifying multiple classes, separate the classes with a space. The default for Sun Java System Directory Server is Example: |
|
|
Specifies a list of space-delimited distinguished names (DN) in the LDAP directory that contains roles. Example: |
|
|
Specifies how deep in the LDAP directory tree to search for roles. Default values: |
The following example illustrates the configuration of a policy store service provider, using an Oracle Internet Directory, and its use in a jpscontext.
<jpsConfig ... >
...
<serviceProviders>
<serviceProvider type="POLICY_STORE" name="policystore.ldap.provider"
class= "oracle.security.jps.internal.policystore.ldap.LdapPolicyStoreProvider">
<description>LDAP-based PolicyStore</description>
<property name="policystore.type" value="OID"/>
<property name="connection.pool.max.size" value="30"/>
<property name="connection.pool.provider.type" value="IDM"/>
</serviceProvider>
</serviceProviders>
...
<serviceInstances>
<serviceInstance name="policystore.oid" provider="policystore.ldap.provider">
<property name="max.search.filter.length" value="4096"/>
<property name="bootstrap.security.principal.key" value="bootstrap"/>
<property name="ldap.url" value="ldap://xyz.us.oracle.com:389"/>
<property name="policystore.jpsbase" value="cn=jps,cn=oraclecontext"/>
<property name="policystore.role.objectclass" value="orclrole"/>
<property name="policystore.role.searchbase" value="cn=roles"/>
<property name="policystore.role.searchscope" value="subtree"/>
<property name="policystore.role.nameattr" value="cn"/>
<property name="policystore.role.memberattr" value="uniquemember"/>
<property name="policystore.role.roleheirarchyattr" value="assignedRoles"/>
</serviceInstance>
</serviceInstances>
...
<jpsContexts default="default">
<jpsContext name="default">
<serviceInstanceRef ref="policystore.oid"/>
</jpsContext>
</jpsContexts>
</jpsConfig>
Table F-9 lists the properties that configure keystore services. When using encryption or signing, you specify a password to retrieve the private key and provide the map to access the keystore credential.
| Name | Description |
|---|---|
|
|
The path to the keystore. |
|
|
The type of keystore. |
|
|
The map of the keystore credentials in the credential store. |
|
|
The key to the private password in the credential store. |
|
|
The private key in the credential store when using signing. |
|
|
The private key in the credential store when using encryption. |
The following example illustrates the configuration of the above properties:
<serviceInstance provider="keystore.provider" name="keystore">
<description>Default JKS Keystore Service</description>
<property value="${oracle.instance}/config/default-keystore.jks" name="keystore.path"/>
<property value="JKS" name="keystore.type"/>
<property value="oracle.wsm.security" name="keystore.csf.map"/>
<property value="keystore-csf-key" name="keystore.pass.csf.key"/>
<property value="sign-csf-key" name="keystore.sig.csf.key"/>
<property value="enc-csf-key" name="keystore.enc.csf.key"/>
</serviceInstance>