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. Optional. |
Specifies the location of the Java security policy file. |
|
|
Enables or disables the delegation of calls to JDK API AccessController.checkPermission, which reduces runtime and debugging overhead. Optional. Valid values: No default value. |
|
Controls server logging output. Default value: FALSE. For details, see Section L.1.2.1, "jps.auth.debug." See also java.security.debug. Optional. |
|
Controls server logging output. Default value: FALSE. For details, see Section L.1.2.2, "jps.auth.debug.verbose." See also java.security.debug. Optional. |
|
Enables or disables the caching of a subject's protection domain. Optional. Valid values: Default value: |
|
Enables or disables the evaluation of a subject's protection domain when a check permission is triggered. Optional. Valid values: Default value: |
|
Enables or disables the migration of policies and credentials for applications deployed in a WebLogic Server. Valid only for the 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. Optional. Valid values: Default value: |
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. Optional. Valid values: Default value: |
|
Specifies the number of seconds after which group membership changes are in effect. This value must be kept in sych with the value of the WebLogic authenticator Optional. Valid values: Default value: |
|
|
Specifies the path to the domain configuration files Required. No default value. |
|
Specifies the path to the directory of a code source URL. Optional. No default value. For an example of use, see <url>. |
|
Specifies the extension of code source URL. Optional. No default value. For an example of use, see <url>. |
|
Logs the name of an application role that contains a specified substring; if the substring to match is unspecified, it logs all application role names. Optional. No default value. For an example of use and further details, see Section L.1.2.3, "Debugging the Authorization Process." |
oracle.security.jps.log.for.permeffect |
Logs a grant that was granted or denied according to a specified value; if the value is unspecified, it logs all grants (regardless whether they were granted or denied). Optional. No default value. For an example of use and further details, see Section L.1.2.3, "Debugging the Authorization Process." |
oracle.security.jps.log.for.permclassname |
Logs the name of the permission class that matches exactly a specified name; if the name to match is unspecified, it logs all permission class names. Optional. No default value. For an example of use and further details, see Section L.1.2.3, "Debugging the Authorization Process." |
oracle.security.jps.log.for.permtarget.substring |
Logs the name of a permission target that contains a specified substring; if the substring to match is unspecified, it logs all permission targets. Optional. No default value. For an example of use and further details, see Section L.1.2.3, "Debugging the Authorization Process." |
oracle.security.jps.log.for.enterprise.principalname |
Logs the name of the principal (enterprise user or enterprise role) that matches exactly a specified name; if the name to match is unspecified, it logs all principal names. Optional. No default value. For an example of use and further details, see Section L.1.2.3, "Debugging the Authorization Process." |
This section describes the properties of various instances in the following sections:
The policy store properties are described in the following sections:
The policy store provider class that can be used with LDAP- or DB-based instances is the following:
oracle.seurity.jps.internal.policystore.ldap.LdapPolicyStoreProvider
Table F-2 describes the properties of policy store instances. The properties are listed in three blocks according to the kind of application they can be used in.
Table F-2 Policy Store Properties
Name | Description |
---|---|
The following properties are valid in both Java EE and Java SE applications |
|
|
The key for the password credentials to access the LDAP policy store, stored in the CSF store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. No default value. The out-of-the-box value is |
|
The map for the password credentials to access the LDAP policy store, stored in the CSF store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. Default value: |
|
The RDN format of the domain node in the LDAP policy store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. No default value. |
|
The RDN format of the root node in the LDAP policy store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. No default value. |
|
The URL of the LDAP policy store, with the format Valid in Java EE and Java SE applications. Applies only to LDAP stores. Required. No default value. |
|
The type of the LDAP policy store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. No default value. Value examples: |
Controls the throwing of exceptions if any of the following checks fail:
If set to If set to Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: Valid values: |
|
|
Indicates the frequency, in milliseconds, at which the system checks the domain files In production environments, it is recommended a frequency of about 10 min. (600000 milliseconds). In development environments, it is recommended a frequency of about 3 min. (180000 milliseconds). Default value: 1000 |
The following properties are valid in Java EE applications only |
|
|
The JNDI name of the JDBC data source instance. Valid in only Java EE applications. Applies to only DB stores. Required. No default value. |
|
The number of retry attempts. Valid in only Java EE applications. Applies to only DB stores. Optional. Default value: 3 |
|
The number of seconds between retry attempts. Valid in only Java EE applications. Applies to only DB stores. Optional. Default value: 15 |
The following properties are valid in Java SE applications only |
|
|
The clear text name of the principal to use instead of the user name specified in the bootstrap. Not recommended. Valid in only Java SE applications. Applies to LDAP and DB stores. Optional. No default value. |
|
The clear text password for the security principal to use instead of the password specified in the bootstrap. Not recommended. Valid in only Java SE applications. Applies to LDAP and DB stores. Optional. No default value. |
|
The JDBC driver. Valid in only Java SE applications. Applies to only DB stores. Required. No default value. Value example: |
|
The URL of the JBDC. Valid in only Java SE applications. Applies to only DB stores. Required. No default value. Value example: |
|
The minimum number of connections allowed in the JDBC read connection pool. Valid in only Java SE applications. Applies to only DB stores. Optional. Default value: 5 |
|
The maximum number of connections allowed in the JDBC read connection pool. Valid in only Java SE applications. Applies to only DB stores. Optional. Default value: 20 |
The following fragment illustrates the configuration of an LDAP-based policy store instance for a Java EE 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 an LDAP-based policy store instance for a Java SE 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>
For additional configurations samples for Java SE applications, see Section 23.1.2, "Configuring LDAP-Based Policy and Credential Stores."
The following fragment illustrates the configuration of DB-based stores (including an instance of a runtime service provider) for a Java EE application:
<jpsConfig> ... <propertySets> <!-- property set props.db.1 common to all DB services --> <propertySet name="props.db.1"> <property name="datasource.jndi.name" value="opssds"/> <property value="cn=farm" name="oracle.security.jps.farm.name"/> <property value="cn=jpsroot" name="oracle.security.jps.ldap.root.name"/> <property value="dsrc_lookup_key" name="bootstrap.security.principal.key"/> <property value="credential_map" name="bootstrap.security.principal.map"/> </propertySet> </propertySets> <serviceProviders> <serviceProvider class="oracle.security.jps.internal.policystore.ldap.LdapPolicyStoreProvider" type="POLICY_STORE" name="rdbms.policystore.provider" > <description>RDBMS based PolicyStore provider</description> </serviceProvider> <serviceProvider type="KEY_STORE" name="keystore.provider" class="oracle.security.jps.internal.keystore.KeyStoreProvider"> <description>PKI Based Keystore Provider</description> <property name="provider.property.name" value="owsm"/> </serviceProvider> <serviceProvider name="pdp.service.provider" type="PDP" class="oracle.security.jps.az.internal.runtime.provider.PDPServiceProvider"> <description>OPSS Runtime Service provider</description> </serviceProvider> </serviceProviders> <serviceInstances> <serviceInstance name="policystore.rdbms" provider="rdbms.policystore.provider"> <property value="DB_ORACLE" name="policystore.type"/> <propertySetRef ref = "props.db.1"/> <property name="session_expiration_sec" value="60"/> <property name="failover.retry.times" value="5"/> </serviceInstance> <serviceInstance name="credstore.rdbms" provider="rdbms.credstore.provider"> <propertySetRef ref = "props.db.1"/> </serviceInstance> <serviceInstance name="keystore.rdbms" provider="rdbms.keystore.provider"> <propertySetRef ref = "props.db.1"/> <property name="keystore.provider.type" value="db"/> </serviceInstance> <serviceInstance name="pdp.service" provider="pdp.service.provider"> <property name="sm_configuration_name" value="permissionSm"/> <property name="work_folder" value="../../tempdir/permissionSm-work"/> <property name="authorization_cache_enabled" value="true"/> <property name="role_cache_enabled" value="true"/> <property name="session_eviction_capacity" value="500"/> <property name="session_eviction_percentage" value="10"/> <property name="session_expiration_sec" value="60"/> <property name="failover.retry.times" value="5"/> <property name="failover.retry.interval" value="20"/> <property name="oracle.security.jps.policystore.purge.timeout", value="30000"/> <propertySetRef ref = "props.db.1"/> </serviceInstance> </serviceInstances> <jpsContexts default="default"> <jpsContext name="default"> <serviceInstanceRef ref="pdp.service"/> <serviceInstanceRef ref="policystore.rdbms"/> <serviceInstanceRef ref="credstore.rdbms"/> <serviceInstanceRef ref="keystore.rdbms"/> </jpsContext> </jpsContexts> ... </jpsConfig>
The following fragment illustrates the configuration of a DB-based policy store instance for a Java SE application:
<serviceInstance name="policystore.rdbms" provider="policy.rdbms"> <property name="policystore.type" value="DB_ORACLE"/> <property name="jdbc.url" value="jdbc:oracle:thin:@sc.us.oracle.com:1722:orcl"/> <property name="jdbc.driver" value="oracle.jdbc.driver.OracleDriver"/> <property name="bootstrap.security.principal.key" value="bootstrap_DWgpEJgXwhDIoLYVZ2OWd4R8wOA=" /> <property name="oracle.security.jps.ldap.root.name" value="cn=jpsTestNode"/> <property name="oracle.security.jps.farm.name" value="cn=view_steph.atz"/> </serviceInstance>
For additional configurations samples for Java SE applications, see Section 23.1.3, "Configuring DB-Based OPSS Security Stores."
The runtime policy store provider class that can be used with LDAP- or DB-based instances is the following:
oracle.seurity.jps.az.internal.runtime.provider.PDPServiceProvider
Table F-3 lists the runtime properties of policy store instances.
Table F-3 Runtime Policy Store Properties
Name | Description |
---|---|
|
The type of the role member cache. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values:
Default value: |
|
The type of strategy used in the role member cache. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values:
Default value: |
|
The number of the roles kept in the member cache. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: 1000. |
|
Enables or disables the policy lazy load. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values: Default value: |
|
The type of strategy used in the permission cache. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values:
Default value: |
|
The number of permissions kept in the permission cache. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: 1000. |
|
Enables or disables the policy store refresh. If this property is set, then Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values: Default value: |
|
Enables or disables the refresh of the cache. If this property is set, then Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values: Default value: |
|
The time, in milliseconds, after which the policy store cache is purged. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: 43200000 (12 hours). |
|
The interval, in milliseconds, at which the policy store is polled for changes. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: 600000 (10 minutes). |
|
The number of user's permissions after which the permission cache is invalidated. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: 50. |
|
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 in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Valid values: Default value: |
|
The folder for temporary storage. Valid in Java EE and Java SE applications. Applies to XML, LDAP, and DB stores. Optional. Default value: the system temporary folder. |
|
Specifies whether the authorization cache should be enabled. Valid in Java EE and Java SE applications. Applies to XML, LDAP, and DB stores. Optional. Valid values: Default value: |
|
The percentage of sessions to drop when the eviction capacity is reached. Valid in Java EE and Java SE applications. Applies to XML, LDAP, and DB stores. Optional. Default value: 10 |
|
The maximum number of authorization and role mapping sessions to maintain. When the maximum is reached, old sessions are dropped and reestablished when needed. Valid in Java EE and Java SE applications. Applies to XML, LDAP, and DB stores. Optional. Default value: 500 |
|
The number of seconds during which session data is cached. Valid in Java EE and Java SE applications. Applies to XML, LDAP, and DB stores. Optional. Default value: 60 |
Controls the throwing of exceptions if any of the following checks fail:
If set to If set to Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Optional. Default value: Valid values: |
Table F-4 lists the properties of credential store instances. The properties are listed in two blocks according to the kind of application they can be used in.
Table F-4 Credential Store Properties
Name | Description |
---|---|
The following properties are valid in Java EE applications only |
|
|
The key for the password credentials to access the LDAP credential store, stored in the CSF store. Valid only in Java EE applications. Applies to LDAP and DB stores. Required. No default value. The out-of-the-box value is |
|
The map for the password credentials to access the LDAP credential store, stored in the CSF store. Valid only in Java EE applications. Applies to LDAP and DB stores. Required. Default value: |
The following properties are valid in both Java EE and Java SE applications |
|
|
The RDN format of the domain node in the LDAP credential store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. No default value. |
|
The RDN format of the root node in the LDAP policy store. Valid in Java EE and Java SE applications. Applies to LDAP and DB stores. Required. No default value. |
|
Specifies the URL of the LDAP credential store using the format Valid in Java EE and Java SE applications. Applies only to LDAP stores. Required. No default value. |
|
Specifies whether to encrypt credentials. Valid in Java EE and Java SE applications. Applies only to file and LDAP stores. Valid values: Optional. Default value: |
The following fragment illustrates the configuration of a credential store in a Java EE 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"/> <property value="true" name="encrypt"/> </serviceInstance>
Table F-5 lists the properties of LDAP-based identity store instances. Extended properties are explicitly stated. User and Role API properties corresponding to a property are also stated.
Table F-5 LDAP-Based Identity Store Properties
Note:
If the authenticator attribute username
is changed (because, for example, of post-provisioning or migrating from a test to a production environment), then the identity store service parameter username.attr
in the identity store service must also be changed accordingly. Those two values should be kept equal.
The following fragment illustrates the configuration of an LDAP-based identity store for a Java SE application:
<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 any service instance.
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. Valid in Java EE and Java SE applications. Optional. Values: Default value: |
|
Specifies the maximum number of connections in the LDAP connection pool. Valid in Java EE and Java SE applications. Optional. Value example: 30 |
|
Specifies the minimum number of connections in the LDAP connection pool. Valid in Java EE and Java SE applications. Optional. Value example: 5 |
|
Specifies the protocol to use for the LDAP connection. Valid in Java EE and Java SE applications. Optional. Values: Default value: |
|
Specifies the connection pool to use. Valid in Java EE and Java SE applications. Optional. Values: Default value: |
|
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. Valid in Java EE and Java SE applications. Optional. Default value: 300000 (5 minutes) |
|
Specifies the maximum number of retry attempts if there are problems with the LDAP connection. Valid in Java EE and Java SE applications. Optional. Value example: 5 |
The following fragment illustrates a configuration of several properties:
<jpsConfig ... > ... <!-- common properties used by all LDAPs --> <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 that can be used to configure file-, LDAP-, or DB-based anonymous users, anonymous roles, and authenticated roles.
Table F-7 Anonymous and Authenticated Roles Properties
Name | Description |
---|---|
|
Specifies a description of the anonymous role. Valid in Java EE and Java SE applications. Optional. No default value. |
|
Specifies the name of the principal in the anonymous role. Valid in Java EE and Java SE applications. Optional. Default value: |
|
Specifies the name of the anonymous role. Valid in Java EE and Java SE applications. Optional. Default value: |
|
Specifies the name of the principal in the anonymous user. Valid in Java EE and Java SE applications. Optional. Default value: |
|
Specifies a description of the authenticated role. Valid in Java EE and Java SE applications. Optional. No default value. |
|
Specifies the name of the principal in authenticated user roles. Valid in Java EE and Java SE applications. Optional. Default value: |
|
Specifies the name of the authenticated role. Valid in Java EE and Java SE applications. Optional. Default value: |
|
Specifies whether the anonymous role should be removed from the subject after a user is authenticated. Valid in Java EE and Java SE applications. Optional. Valid values: Default value: |
Table F-8 lists the properties that can be used to configure the trust service.
Table F-8 Trust Service Properties
Name | Description |
---|---|
|
Specifies the alias to use to get an X.509 certificate and private key from the keystore. Valid in Java EE and Java SE applications. Optional. Default: the name of the WLS domain of the WAS cell. |
|
Specifies the name to be included in the token. It is used by the destination trust service to pick up and validate the token. Valid in Java EE and Java SE applications. Optional. Default: the name of the WLS domain of the WAS cell. |
|
Specifies the map of the credential to access the keystore. Valid in Java EE and Java SE applications. Optional. Default: the value of the keystore instance property |
|
Specifies the key of the credential to access the private key (the map is set by Valid in Java EE and Java SE applications. Optional. Default: the value of the keystore instance property |
|
Specifies the key of the credential to acces the keystore (the map is set by Valid in Java EE and Java SE applications. Optional. Default: the value of the keystore instance property |
The following sample illustrates the configuration of a trust service:
<propertySet name="trust.provider.embedded"> <property name="trust.provider.className" value="oracle.security.jps.internal.trust.provider.embedded.EmbeddedProviderImpl"/> <property name="trust.clockSkew" value="60"/> <property name="trust.token.validityPeriod" value="1800"/> <property name="trust.token.includeCertificate" value="false"/> <property name="trust.aliasName" value="orakey"/> <property name="trust.issuerName" value="orakey"/> <property name="trust.csf.map " value="my-csf-map"/> <property name="trust.csf.keystorePass" value="my-keystore-csf-key"/> <property name="trust.csf.keypass" value="my-signing-csf-key"/> </propertySet>
Table F-9 lists the properties used to configure the audit service:
Table F-9 Audit Service Properties
Property | Description | Required? | Values | Default Value |
---|---|---|---|---|
auditstore.type |
The audit metadata store type |
yes |
file, ldap, or db |
file |
audit.filterPreset |
The level of auditing - None, Low, Medium, and Custom |
no |
None, Low, Medium, or All |
None |
audit.customEvents |
For Custom, a list of audit events that should be audited. The events must be qualified using the component type. Commas separate events and a semicolon separates component types. Example: JPS:CheckAuthorization, CreateCredential; OIF:UserLogin |
no |
||
audit.specialUsers |
list of one or more users whose activity is always audited, even if filterPreset is None. Usernames that contain commas must be escaped properly. For example, when using Fusion Middleware Control, specify three users like this - "admin, fmwadmin, cn=test\,cn=user\,ou:ST\,L=RS\,c=is\," In setAuditPolicy(addSpecialUsers="cn=orcladmin\\\,cn=com") For more information, see Section C.4.3, "setAuditPolicy". |
no |
||
audit.maxDirSize |
Controls the size of the directory where the audit files will be written. Integer is in Bytes. |
no |
102400000 |
|
audit.maxFileSize |
Controls the size of a bus stop file where audit events are written. Integer is in Bytes |
no |
104857600 |
|
audit.loader.interval |
Controls the frequency with which audit loader uploads to database. Integer is in Seconds. |
no |
15 seconds |
|
audit.loader |
Store type for the audit events. If type is Database (Db), also define audit.loader.jndi or JDBC property. |
yes |
File, DB |
File |
audit.loader.jndi |
JNDI name of the data source in application servers for uploading audit events into database. |
no |
jdbc/AuditDB |
|
audit.db.principal.map / audit.db.principal.key |
The map and key for the JDBC user name and password credential in bootstrap credential store,when running in JavaSE, and repositoryType is DB. |
no |
||
audit.loader.jdbc.string |
The JDBC string for JDBC connection when running in JavaSE, and repositoryType is DB. |
no |
||
audit.logDirectory |
The base directory for bus-stop files. |
required for JavaSE |
jse |
The following is an example of audit service configuration:
<serviceInstance name="audit" provider="audit.provider" location="./audit-store.xml"> <property name="audit.filterPreset" value="None"/> <property name="audit.loader.jndi" value="jdbc/AuditDB"/> <property name="audit.loader.repositoryType" value="File" /> <property name="auditstore.type" value="file"/> </serviceInstance>
Table F-10 lists the properties used to configure the Keystore Service:
Table F-10 Keystore Service Properties
Property | Description | Required? | Values | Default |
---|---|---|---|---|
keystore.provider.type |
Keystore repository type |
Yes |
file, ldap, db |
file |
keystore.file.path |
Location of the file keystores.xml when file provider is configured |
Yes, if a file-based keystore provider is configured. |
- |
./ |
ca.key.alias |
Key alias within "system/castore" of the third party CA used for Keystore service instance |
No |
- |
- |
location |
Location of the keystore; can be absolute or relative path. |
Yes, if keystore.type is JKS.No, if keystore.type is PKCS11 or HSM (LunaSA) |
Path to keystore |
./default-keystore.jks |
keystore.type |
Type of keystore |
Yes |
JKS, PKCS11, Luna |
JKS |
keystore.csf.map |
Credential store map name used by Oracle Web Services Manager. |
Yes |
Credential store map name |
oracle.wsm.security |
keystore.pass.csf.key |
Credential store key that points to Keystore password. |
Yes, for JKS and PKCS11. No, for HSM |
Credential store csf key name |
keystore-csf-key |
keystore.sig.csf.key |
Credential store key name that points to alias and password of signing key in keystore.For HSM, it is the direct key alias name rather than the credential store key name. |
Yes |
Credential store csf key name or, for HSM, the direct alias |
sign-csf-key |
keystore.enc.csf.key |
Credential store key name that points to alias and password of encryption key in keystore.For HSM, it is the direct key alias name rather than the credential store key name. |
Yes |
Credential store csf key name or, for HSM, the direct alias |
enc-csf-key |
The following is an example of Keystore Service configuration for a file-based provider :
<serviceInstance name="keystore" provider="keystore.provider" location="./default-keystore.jks"> <description>Default JPS Keystore Service</description> <property name="keystore.provider.type" value="file"/> <property name="keystore.file.path" value="./"/> <property name="keystore.type" value="JKS"/> <property name="keystore.csf.map" value="oracle.wsm.security"/> <property name="keystore.pass.csf.key" value="keystore-csf-key"/> <property name="keystore.sig.csf.key" value="sign-csf-key"/> <property name="keystore.enc.csf.key" value="enc-csf-key"/> </serviceInstance>
The following is an example of Keystore Service configuration for an LDAP-based provider :
<serviceInstance name="keystore" provider="keystore.provider" location="./default-keystore.jks"> <description>Default JPS Keystore Service</description> <property name="keystore.provider.type" value="ldap"/> <property name="keystore.type" value="JKS"/> <property name="keystore.csf.map" value="oracle.wsm.security"/> <property name="keystore.pass.csf.key" value="keystore-csf-key"/> <property name="keystore.sig.csf.key" value="sign-csf-key"/> <property name="keystore.enc.csf.key" value="enc-csf-key"/> <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"/> </serviceInstance>
The following is an example of Keystore Service configuration for an RDBMS-based provider :
<propertySet name="props.db.1"> <property name="datasource.jndi.name" value="opssds"/> <property value="cn=farm" name="oracle.security.jps.farm.name"/> <property value="cn=jpsroot" name="oracle.security.jps.ldap.root.name"/> <property value="dsrc_lookup_key" name="bootstrap.security.principal.key"/> <property value="credential_map" name="bootstrap.security.principal.map"/> </propertySet> … … <serviceInstance name="keystore.rdbms" provider="keystore.provider" location="./default-keystore.jks"> <propertySetRef ref = "props.db.1"/> <property name="keystore.provider.type" value="db"/> <property name="keystore.type" value="JKS"/> <property name="keystore.csf.map" value="oracle.wsm.security"/> <property name="keystore.pass.csf.key" value="keystore-csf-key"/> <property name="keystore.sig.csf.key" value="sign-csf-key"/> <property name="keystore.enc.csf.key" value="enc-csf-key"/> </serviceInstance>