JPS-00001 to JPS-90642

17 JPS-00001 to JPS-90642

JPS-00001: The method {0} is not supported.
Category:: Requests/Responses
Cause:: An unsupported method was used.
Action:: This operation is not supported. It cannot be used.

JPS-00003: The HTTP response callback is null.
Category:: Session
Cause:: HTTP response callback was null.
Action:: Check the log files and provide a valid HTTP response callback.

JPS-00004: The HTTP response is null.
Category:: Session
Cause:: HTTP response was null.
Action:: Check the log files and provide a valid HTTP response.

JPS-00005: HTTP request callback is null.
Category:: Session
Cause:: HTTP request callback was null.
Action:: Check the log files and provide a valid HTTP request callback.

JPS-00006: The HTTP request is null.
Category:: Session
Cause:: HTTP request was null.
Action:: Check the log files and provide a valid HTTP request.

JPS-00007: Cannot find an application ID.
Category:: Session
Cause:
Action:

JPS-00008: The application ID {0} is invalid.
Category:: Configuration
Cause:: Application ID was NULL.
Action:: Provide a valid application ID.

JPS-00009: The subject is read-only, and it cannot modified.
Category:: Requests/Responses
Cause:: Attempted to modify a read-only subject.
Action:: A read-only subject cannot be modified.

JPS-00010: A JPS context is not available in the callback handler.
Category:: Session
Cause:: A context was not available from callback handler.
Action:: Check configuration in jps-config.xml.

JPS-00011: The service instance {0} already exists.
Category:: Configuration
Cause:: The named service instance was already in use.
Action:: Use a different name for this service instance.

JPS-00012: The service instance {0} is missing.
Category:: Configuration
Cause:: The service instance with the name {0} was not found.
Action:: Ensure the service instance name is present in the file jps-config.xml.

JPS-00013: The login module {0} already exists.
Category:: Configuration
Cause:: The login module with the name {0} was already present.
Action:: Ensure the login module name is correct.

JPS-00014: The login module with {0} is missing.
Category:: Configuration
Cause:: The login module with the name {0} did not exist.
Action:: Ensure the login module name is correct.

JPS-00015: All available service instance names are already in use.
Category:: Configuration
Cause:: All service instance names were in use.
Action:: Remove unwanted service instances from jps-config.xml.

JPS-00016: All available service provider names are already in use.
Category:: Configuration
Cause:: All service provider names were in use.
Action:: Remove unwanted service providers form jps-config.xml.

JPS-00017: The LDAP type is invalid.
Category:: Configuration
Cause:: An invalid LDAP type was specified.
Action:: Provide a valid LDAP type. Valid types are XML, OID, ACTIVE_DIRECTORY, IPLANET, OUD and OVD. See the documentation for details.

JPS-00018: The keystore path {0} is null or invalid.
Category:: Configuration
Cause:: Keystore path was null.
Action:: Provide a valid keystore path.

JPS-00019: The key type {0} is not supported.
Category:: Configuration
Cause:: Invalid key type was provided.
Action:: Provide a valid key type.

JPS-00020: LDAP URL {0} is null or invalid.
Category:: Configuration
Cause:: Invalid or null LDAP URL was provided.
Action:: Provide a valid LDAP URL.

JPS-00021: An Object named {0} does not exist.
Category:: Configuration
Cause:: Object with the name {0} did not exist.
Action:: Verify that the object name is valid and exists.

JPS-00022: Callback handler missing for this login module request.
Category:: Requests/Responses
Cause:: The callback handler was null.
Action:: Provide an appropriate callback handler to invoke this login module.

JPS-00023: The callback used for this operation has no HTTP request value.
Category:: Requests/Responses
Cause:: The callback did not have a request method.
Action:: Verify that the callback is initialized with the correct HTTP request value.

JPS-00024: The callback used for this operation has no digest response object value.
Category:: Requests/Responses
Cause:: The callback did not have any digest response object.
Action:: Verify that the callback is initialized with the correct digest response value.

JPS-00025: The {0} subscriber {1} from the HTTP header is different from the subscriber configured by the identity store as {2}.
Category:: Configuration
Cause:: Found a subscriber mismatch.
Action:: Check the identity store subscriber configuration.

JPS-00026: The value "{0}" is invalid for {1}.
Category:: Requests/Responses
Cause:: An invalid value was provided for this application.
Action:: Provide the correct value for the application.

JPS-00027: There was an internal error: {0}
Category:: Requests/Responses
Cause:: Internal system error was found.
Action:: See the log files or contact the system administrator.

JPS-00028: The property runas.mode is deprecated and supported only for backward compatibility.
Category:: Requests/Responses
Cause:: The property runas.mode has been deprecated.
Action:: Use instead the oracle.security.jps.jaas.mode property in jps-config.xml.

JPS-00029: The audit service initialization failed for the application {0}. Reason {1}.
Category:: Configuration
Cause:: Audit service failed.
Action:: Check the audit service configuration in jps-config.xml.

JPS-00030: Cannot complete exist operation.
Category:: Configuration
Cause:: Could not find entity.
Action:: Verify that the entity exist.

JPS-00031: Cannot load the required class {0}. Reason {1}.
Category:: Upgrade
Cause:: Could not load a class.
Action:: Ensure the class is in the class path.

JPS-00032: The migration cannot write directly to the specified LDAP identity store; specify an alternate LDIF file to create.
Category:: Upgrade
Cause:: Could not perform a direct LDAP write operation.
Action:: See the log files for details.

JPS-00033: The direct policy store should be XML-based, and it can be specified as an XML file or as an input stream.
Category:: Upgrade
Cause:: The policy store specification was invalid.
Action:: Check the policy store specification.

JPS-00034: Cannot find the application context.
Category:: Session
Cause:: A context was not available for the application.
Action:: Check the jps-config.xml configuration.

JPS-00035: The WSS digest value {0} is invalid.
Category:: Requests/Responses
Cause:: Found missing WSS digest value in callback.
Action:: Verify that the callback has a valid WSS digest value.

JPS-00036: The WSS digest nonce {0} is invalid.
Category:: Requests/Responses
Cause:: Found missing WSS digest nonce in callback.
Action:: Verify that the callback has a valid WSS digest nonce.

JPS-00037: The WSS digest created {0} is invalid.
Category:: Requests/Responses
Cause:: Found missing WSS digest created in callback.
Action:: Verify that the callback has a valid WSS digest created.

JPS-00038: Cannot create or retrieve a ContextFactory.
Category:: Other
Cause:: Cannot retrieve or create a JPS ContextFactory.
Action:: Check jps-config.xml for correctness.

JPS-00039: The service instance with provider {0} and name {1} is missing.
Category:: Configuration
Cause:: A service instance configuration was missing.
Action:: Check the service instance configuration.

JPS-00040: The JPS audit component events file {0} is missing or invalid.
Category:: Other
Cause:: Cannot find the audit component events file.
Action:: Make sure the audit component events file is available and valid.

JPS-00041: Cannot load the JpsAdminService class.
Category:: Other
Cause:: The class JpsAdminService or a dependent class could not be loaded.
Action:: Review the cause to resolve the error.

JPS-00042: The LDAP connection pool provider {0} is not valid; the supported providers are JNDI or IDM. If unspecified, it defaults to UCP/JNDI provider.
Category:: Configuration
Cause:: The connection.pool.provider.type property value was invalid.
Action:: Configure a supported connection.pool.provider.type value, or use the default provider by not setting the connection.pool.provider.type property.

JPS-00043: Cannot establish an LDAP connection after {0} attempts.
Category:: Requests/Responses
Cause:: The connection could not be established.
Action:: Check the LDAP configuration.

JPS-00044: The LDAP URL format must be ldap://<host>:<port> or ldaps://<host>:<port>; but found {0}.
Category:: Configuration
Cause:: Invalid LDAP URL format was found.
Action:: The format of the LDAP URL must be ldap://<host>:<port> or ldaps://<host>:<port> format.

JPS-00045: The LDAP principal {0} is invalid.
Category:: Configuration
Cause:: The LDAP principal was invalid.
Action:: Provide a correct value for principal.

JPS-00046: The LDAP credential is invalid.
Category:: Configuration
Cause:: The LDAP credential was invalid.
Action:: Provide the correct credential value.

JPS-00047: The Subject parameter cannot be null.
Category:: Programmatic
Cause:: The supplied parameter was null.
Action:: Check the Subject parameter supplied in the method call.

JPS-00048: Principals are missing in the Subject.
Category:: Programmatic
Cause:: No principals were not found in the Subject.
Action:: Verify that the supplied Subject contains principals.

JPS-00049: The authenticated user principal is missing in the Subject.
Category:: Programmatic
Cause:: Authenticated user principal was not found in the Subject.
Action:: Verify that the supplied Subject contains an authenticated user principal.

JPS-00050: Invalid Subject parameter supplied.
Category:: Programmatic
Cause:: The Subject contained an anonymous user principal and an authenticated user principal.
Action:: Ensure that the Subject does not contain the anonymous user principal.

JPS-00051: The oracle.security.jps.config property not set.
Category:: Upgrade
Cause:: The oracle.security.jps.config property was not set.
Action:: Set the oracle.security.jps.config property to an appropriate value.

JPS-00052: Failed to Refresh Audit Service with new configuration.
Category:: Configuration
Cause:: Failed to reload the audit configuration.
Action:: Check the audit configuration file to see if the lastest changes are valid.

JPS-00053: Component events file is missing for {0} at {1}.
Category:: Configuration
Cause:: The component events file for the given component type was missing.
Action:: Verify that the properties set for the component files are correct in jps-config.xml.

JPS-00054: Failed to create the auditor for {0}.
Category:: Configuration
Cause:: Failed to create the auditor object.
Action:: Ensure that the component events file is not missing or corrupt and check the log files additional errors.

JPS-00055: Bootstrap credential store service is not initialized for the service configurator.
Category:: Programmatic
Cause:: The bootstrap credetial store service was not initialised.
Action:: Make sure the bootstrap credetial store service is initialized before any other services.

JPS-00056: Failed to create identity store service instance {0}. Reason: {1}.
Category:: Configuration
Cause:: Failed to create identity store service instance {0}. Cause: {1}.
Action:: Check the log files to resolve the error.

JPS-00057: Failed to set OutputProperty for indent or XML encoding. Reason {0}.
Category:: Configuration
Cause:: Failed to setOutputProperty for indent or XML encoding. Cause: {0}
Action:: Check the XML Transformer implementation.

JPS-00058: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Reason {0}.
Category:: Configuration
Cause:: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Cause: {0}
Action:: Check the JDK OutputStreamWriter supported encodings.

JPS-00059: The specified enterprise identity is null or invalid.
Category:: Configuration
Cause:: An enterprise identity provided was null or invalid
Action:: Provide a valid enterprise identity value.

JPS-00060: The specified enterprise identity {0} is not found in identity store.
Category:: Configuration
Cause:: The specified enterprise identity {0} was not found in the identity store.
Action:: Provide a valid enterprise identity value.

JPS-00061: No platform specific factory is found to create the platform principals. Check errors in the log files.
Category:: Configuration
Cause:: No platform specific factory was found to create platform principals.
Action:: Check the log files for the errors.

JPS-00062: No identity store associated with policy store found.
Category:: Configuration
Cause:: No identity store associate with policy store found
Action:: Contact system administrator

JPS-00063: Jps servlet filter creation failed. Reason: {0}.
Category:: Configuration
Cause:: Jps Servlet Filter creation failed
Action:: Contact system administrator

JPS-00064: Jps ejb interceptor creation failed. Reason: {0}.
Category:: Configuration
Cause:: Jps EJB Interceptor creation failed
Action:: Contact system administrator

JPS-00065: Jps platform factory creation failed. Reason: {0}.
Category:: Configuration
Cause:: Jps Platform Factory creation failed
Action:: Contact system administrator

JPS-00066: Jps property value retrieval failed. Reason: {0}.
Category:: Configuration
Cause:: Jps property value retrieval failed
Action:: Check the property values in jps configuration files

JPS-00068: Ldap security checking failed. The LDAP url should start with ldaps and oracle.ldap.wltloc system property should be set. Reason : {0}.
Category:: Security
Cause:: Is LDAP secure failed
Action:: Contact system administrator

JPS-00069: Ldap credential store provider missing.
Category:: Security
Cause:: LDAP credential provider missed
Action:: Ensure ldap credential store provider is configured

JPS-00070: Ldap policy store provider missing.
Category:: Security
Cause:: LDAP policy store provider missing
Action:: Ensure ldap policy store is configured

JPS-00071: Ldap bootstrap credential retrieval failed. Reason:{0}.
Category:: Security
Cause:: Retrieval of bootstrap credential failed
Action:: Check the credential store configuration for credential types, maps and key

JPS-00072: Policy schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}
Category:: Configuration
Cause:: Comparison of policy schema version in the store against to seed schema version.
Action:: No action required

JPS-00073: Policy store schema version not found
Category:: Configuration
Cause:: Trying to determine version of the policy schema in the store
Action:: Contact Oracle Support Services.

JPS-00074: Policy store schema version {0} is less than the latest schema version {1}, upgrade the Policy store schema to latest version.
Category:: Configuration
Cause:: Comparison of the Policy schema version in the store against the schema to seed
Action:: No action required

JPS-00075: Unable to query Policy store schema version under "{0}", Cause {1}
Category:: Configuration
Cause:: Query of Policy schema from the store failed
Action:: Confirm the Policy store schema containers are present in the store

JPS-00076: Policy schema version set to {0}
Category:: Configuration
Cause:: Version of the policy schema has been set in the store
Action:: No action required

JPS-00077: Setting version of policy schema in the store failed. Cause {0}
Category:: Configuration
Cause:: Unexpected error occurred while setting the version of the Policy schema in the store
Action:: Confirm the container is present in the store and caller has sufficient privileges to perform this operation

JPS-00078: Credential store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}
Category:: Configuration
Cause:: Comparison of Credential schema version in the store against the seed schema version.
Action:: No action required

JPS-00079: Credential store schema version not found
Category:: Configuration
Cause:: Check if the DN exists, or if the Credential Store schema version attribute is present at the specificied location
Action:: Contact Oracle Support Services.

JPS-00080: Credential store schema version {0} is less than the latest schema version {1}, upgrade the Credential store schema to latest version.
Category:: Configuration
Cause:: Comparison of the Credential schema version in the store against the schema to seed
Action:: No action required

JPS-00081: Unable to query Credential store schema version under "{0}", Cause {1}
Category:: Configuration
Cause:: Query of Credential schema from store store failed
Action:: Confirm the Credential store schema container in the store is present

JPS-00082: Credential schema version set to {0}
Category:: Configuration
Cause:: Version of the credential schema has been set in the store
Action:: No action required

JPS-00083: Setting version of credential schema in the store failed. Cause {0}
Category:: Configuration
Cause:: Unexpected error occurred while setting the version of the credential schema in the store
Action:: Confirm the container is present in the store and caller has sufficient privileges to perform this operation

JPS-00084: IOException raised from FileLocker {0}.
Category:: Other
Cause:: Closing IO objects in FileLocker
Action:: Check the file system for access privileges and disk space availability.

JPS-00085: OID version is unavailable.
Category:: Other
Cause:: OID version is unavalable
Action:: Check the ldap url against the server type passed.

JPS-00086: Error while encoding search string: {0} to UTF-8 encoding
Category:: Other
Cause:: Unable to encode user string to UTF-8 encoding
Action:: Check the search string.

JPS-00087: The subject parameter is null.
Category:: Security
Cause:: The subject parameter is null
Action:: Make sure the subject parameter is not null

JPS-00088: The user name parameter is null.
Category:: Security
Cause:: The user name parameter is null
Action:: Make sure the user name parameter is not null

JPS-00089: The subject from the current AccessControlContext is null.
Category:: Security
Cause:: No subject is associated with the current AccessControlContext.
Action:: Ensure that the subject is associated with the current AccessControlContext.

JPS-00090: Failed to create policy store service instance {0}. Cause: {1}.
Category:: Configuration
Cause:: Failed to create policy store service instance {0}. Cause: {1}.
Action:: Check the log files to resolve the error.

JPS-00091: No {0} available.
Category:: Requests/Responses
Cause:: No {0} available.
Action:: Contact the administrator.

JPS-00092: The ldap service was null.
Category:: Security
Cause:: The ldap service was null.
Action:: Ensure the ldap service is not null.

JPS-00093: Class {0} was not type of {1}.
Category:: Security
Cause:: Class {0} was not type of {1}.
Action:: Ensure class name is correct.

JPS-00094: Failed to parse digest response.
Category:: Configuration
Cause:
Action:

JPS-00095: {0} system properties not set.
Category:: Configuration
Cause:: System properties {0} not set.
Action:: Set the system properties.

JPS-00096: No {0} defined for {1}.
Category:: Configuration
Cause:: No {0} defined for {1}.
Action:: Defined the specified object.

JPS-00097: {0} missing in message : {1}.
Category:: Configuration
Cause:: {0} missing in message : {1}.
Action:: Check the input.

JPS-00098: Duplicate error message.
Category:: Configuration
Cause:: Duplicate error message.
Action:: Check the input.

JPS-00099: {0} already exists.
Category:: Configuration
Cause:: {0} already exists.
Action:: Check the input.

JPS-00100: Failed to instantiate {0}.
Category:: Configuration
Cause:: Failed to instantiate {0}.
Action:: Check the object type.

JPS-00101: {0} not match {1}.
Category:: Configuration
Cause:: {0} not match with {1}.
Action:: Check the object type.

JPS-00102: Unhandled entry {0}
Category:: Configuration
Cause:: Unhandled entry {0}.
Action:: Check the entry.

JPS-00103: Invalid login module type {0}.
Category:: Configuration
Cause:: Invalid login module type {0}.
Action:: Use valid login module type.

JPS-00104: System policy does not exist.
Category:: Configuration
Cause:: System policy does not exist.
Action:: Ensure system policy exist.

JPS-00105: Failed to create temp dir {0}.
Category:: Configuration
Cause:: Failed to create temp dir {0}.
Action:: Check the log for more details.

JPS-00106: InputStream has no more data to read.
Category:: Configuration
Cause:: InputStream had no more data to read.
Action:: Check the log for more details.

JPS-00107: {0} invoked.
Category:: Security
Cause:
Action:

JPS-00108: Event {0} was ignored.
Category:: Security
Cause:
Action:

JPS-00109: Overwriting credentials is allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.
Category:: Security
Cause:
Action:

JPS-00110: Failed to decode {0}. Reason {1}.
Category:: Security
Cause:: Failed to decode {0}. Reason: {1}.
Action:: Check log for more details.

JPS-00111: Current timer interval ({0} seconds) is too short.
Category:: Security
Cause:: Current timer interval ({0} seconds) is too short.
Action:: Please set a longer interval in the configuration file.

JPS-00112: Set property {0} to value {1}.
Category:: Security
Cause:: Set property {0} to value {1}.
Action:: Check log for more details.

JPS-00113: Failed to parse condition {0}. Reason {1}.
Category:: Security
Cause:: Failed to parse condition {0}. Reason {1}.
Action:: Check log for more details.

JPS-00114: Failed to load data file {0}.
Category:: Security
Cause:: Failed to load data file {0}.
Action:: Please check file location.

JPS-00115: Failed to modify JPS Schema.
Category:: Security
Cause:: Failed to modify JPS Schema.
Action:: Check log for more details.

JPS-00116: Failed to read JPS Schema.
Category:: Security
Cause:: Failed to read JPS Schema.
Action:: Check log for more details.

JPS-00117: Failed to delete System Policy name {0}. Reason {1}.
Category:: Security
Cause:: Failed to delete System Policy name {0}. Reason {1}.
Action:: Check log for more details.

JPS-00118: {0} not found.
Category:: Security
Cause:: {0} not found.
Action:: Check log for more details.

JPS-00119: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.
Category:: Security
Cause:: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.
Action:: Check log for more details.

JPS-00120: Failed to seed attribute {0}, ldap object class {1}.
Category:: Configuration
Cause:: Failed to seed attribute {0}, ldap object class {1}.
Action:: Check the LDAP configuration to resolve the error.

JPS-00121: Failed to parse LDIF record {0}. Reason: {1}.
Category:: Configuration
Cause:: Failed to parse LDIF record {0}. Reason: {1}.
Action:: Check the LDAP configuration to resolve the error.

JPS-00122: Farm DN {0} does not exist.
Category:: Configuration
Cause:: Farm DN {0} does not exist.
Action:: Ensure farm DN is valid.

JPS-00123: RDN {0} not found under farm {1}.
Category:: Configuration
Cause:: RDN {0} not found under farm {1}.
Action:: Check LDAP server type.

JPS-00124: {0} is not supported.
Category:: Configuration
Cause:: {0} is not supported.
Action:: Use a valid type.

JPS-00125: Property {0} was null.
Category:: Requests/Responses
Cause:: Property {0} was null.
Action:: Ensure property is not null.

JPS-00126: Overwriting credentials is not allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.
Category:: Security
Cause:
Action:

JPS-00127: Failed to create igf service instance {0}. Reason: {1}.
Category:: Configuration
Cause:: Failed to create igf service instance {0}. Cause: {1}.
Action:: Check the log files to resolve the error.

JPS-00128: Keystore schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}
Category:: Configuration
Cause:: Comparison of Keystore schema version in the store against the seed schema version.
Action:: No action required

JPS-00129: Keystore schema version not found
Category:: Configuration
Cause:: Check if the DN exists, or if the Keystore schema version attribute is present at the specificied location
Action:: Contact Oracle Support Services.

JPS-00130: Keystore schema version {0} is less than the latest schema version {1}, upgrade the Keystore schema to latest version.
Category:: Configuration
Cause:: Comparison of the Keystore schema version in the store against the schema to seed
Action:: No action required

JPS-00131: Unable to query Keystore schema version under "{0}", Cause {1}
Category:: Configuration
Cause:: Query of Keystore schema from store store failed
Action:: Confirm the Keystore schema container in the store is present

JPS-00132: Keystore schema version set to {0}
Category:: Configuration
Cause:: Version of the keystore schema has been set in the store
Action:: No action required

JPS-00133: Setting version of keystore schema in the store failed. Cause {0}
Category:: Configuration
Cause:: Unexpected error occurred while setting the version of the keystore schema in the store
Action:: Confirm the container is present in the store and caller has sufficient privileges to perform this operation

JPS-00134: The offline deployment staging directory {0} does not exist.
Category:: Deployment
Cause:: The cause may be that the product was installed inproperly.
Action:: Install the product properly.

JPS-00135: Exception occurs on saving ear file {0}.
Category:: Deployment
Cause:: The cause may be due to bad ear file or insufficient permission.
Action:: Check the ear file and the file system permissiion.

JPS-00136: Exception occurs on saving offline deployment property file in application directory {0}.
Category:: Deployment
Cause:: The cause may be due to insufficient permission.
Action:: Check the file system permissiion.

JPS-00137: Found offline deployed app {0}.
Category:: Deployment
Cause:
Action:

JPS-00138: Exception occurs on opening the staging application in {0}.
Category:: Deployment
Cause:: This may be caused by bad .ear file on the disk.
Action:: Check the .ear file on the disk.

JPS-00139: Exception occurs on loading the property file of the staging application in {0}.
Category:: Deployment
Cause:: Failed to open the property file.
Action:: Check the property file on the disk.

JPS-00140: Failed to delete the staging app {0}. Migration flag file created.
Category:: Deployment
Cause:
Action:

JPS-00141: Cannot handle offline deployed application due to the required system property {0} is not set.
Category:: Deployment
Cause:: The cause may be that the product was installed inproperly.
Action:: Install the product properly.

JPS-00142: No opss-application.xml found.
Category:: Deployment
Cause:
Action:

JPS-00143: Error on migrating security artifacts.
Category:: Deployment
Cause:: Error on migrating security artifacts.
Action:: Check security related files in your application, such as opss-application.xml, jazn-data.xml, cwallet.sso, etc.

JPS-00144: Error on opening ear file {0}.
Category:: Deployment
Cause:: Error on opening ear file.
Action:: Check the ear file.

JPS-00145: Found no installed application at {0}.
Category:: Deployment
Cause:: Found no installed application at {0}.
Action:: Check the installed application at {0}.

JPS-00146: Failed to create identity store service instance {0}. Reason: the service does not enable the virtualizes flag, but references other service instance.
Category:: Configuration
Cause:: Failed to create identity store service instance {0}. Cause: the service does not enable the virtualize flag, but references other service instance.
Action:: Either make the virtualize flag true, or directly define the ldap configuration instead of using service reference

JPS-00147: Keystore re-association not supported.
Category:: Configuration
Cause:: Configuration of key store was not suitable for re-association.
Action:: Confirm the key store configuration is updated.

JPS-00148: Jps JBoss signing key seeded.
Category:: Security
Cause:
Action:

JPS-00149: Jps JBoss signing key already exists. Seeding ignored.
Category:: Security
Cause:
Action:

JPS-00150: Key 1 and Key 2 are no longer supported for system parameter -Djps.subject.cache.key, please use key 4 (default), 3, or 5 (fastest).
Category:: Security
Cause:
Action:

JPS-00151: Audit store instantiation failure, type: {0} reason: {1}
Category:: Configuration
Cause:: Audit metadata store failed to be instantiated, type: {0}, reason: {1}
Action:: Check the audit service configuration in jps-config.xml.

JPS-00152: Component not registered, name: {0}
Category:: Configuration
Cause:: Component {0} not registered and no audit configuration found.
Action:: Register component with audit service.

JPS-00153: The principal {0} is invalid.
Category:: Configuration
Cause:: The principal is invalid.
Action:: Provide a correct value for principal.

JPS-00154: The rule condition {0} is invalid.
Category:: Configuration
Cause:: The rule condition function is invalid.
Action:: Provide a correct value for rule condition function.

JPS-00155: Audit metadata store is not instantiated in audit service.
Category:: Configuration
Cause:: Audit metadata store is not instantiated.
Action:: Verify that the audit store properties for audit service are correct in jps-config.xml.

JPS-00156: Audit metadata store type {0} is invalid
Category:: Configuration
Cause:: Audit metadata store type {0} is invalid
Action:: Check the audit service configuration in jps-config.xml.

JPS-00157: The DN {0} was invalid LdapName format, see javax.naming.ldap.LdapName
Category:: Configuration
Cause:: The DN {0} was invalid LdapName format, see javax.naming.ldap.LdapName
Action:: Ensure property in format of javax.naming.ldap.LdapName.

JPS-00158: Audit store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}
Category:: Configuration
Cause:: Comparison of Audit schema version in the store against the seed schema version.
Action:: No action required

JPS-00159: Audit store schema version not found
Category:: Configuration
Cause:: Check if the DN exists, or if the Audit Store schema version attribute is present at the specificied location
Action:: Contact Oracle Support Services.

JPS-00160: Audit store schema version {0} is less than the latest schema version {1}, upgrade the Audit store schema to latest version.
Category:: Configuration
Cause:: Comparison of the Audit schema version in the store against the schema to seed
Action:: No action required

JPS-00161: Unable to query Audit store schema version under "{0}", Cause {1}
Category:: Configuration
Cause:: Query of Audit schema from store store failed
Action:: Confirm the Audit store schema container in the store is present

JPS-00162: Audit schema version set to {0}
Category:: Configuration
Cause:: Version of the audit schema has been set in the store
Action:: No action required

JPS-00163: Setting version of audit schema in the store failed. Cause {0}
Category:: Configuration
Cause:: Unexpected error occurred while setting the version of the audit schema in the store
Action:: Confirm the container is present in the store and caller has sufficient privileges to perform this operation

JPS-00164: Audit store re-association not supported.
Category:: Configuration
Cause:: Configuration of audit store was not suitable for re-association.
Action:: Confirm the audit store configuration is updated.

JPS-00165: Failed to reload component {0} runtime policy with error message {1}.
Category:: Other
Cause:: Failed to reload component runtime policy.
Action:: Check component run policy and custom fitler preset definition.

JPS-00166: Failed to retrieve Embedded LDAP store information.
Category:: Configuration
Cause:: Failed to retrieve embedded ldap store information.
Action:: Check the log files to resolve the error.

JPS-00167: Invalid xml content was found. {0} Location: {1}.
Category:: Security
Cause:: Invalid xml content was found. {0} Location: {1}.
Action:: Fix the invalid xml elements according to the xsd schema definition.

JPS-00168: OID server version {0} is not supported
Category:: Other
Cause:: OID server version {0} is not supported
Action:: Check the support matrix.

JPS-00169: Cannot get server log directory. Reason: {0}.
Category:: Security
Cause:: Cannot get server log directory. Reason: {0}.
Action:: Check server configuration.

JPS-00170: Initializing OPSS Java Policy Provider.
Category:: Configuration
Cause:
Action:

JPS-00171: OPSS Java Policy Provider initialized.
Category:: Configuration
Cause:
Action:

JPS-00172: OPSS Java Policy Provider is set as the system-wide Policy object.
Category:: Configuration
Cause:
Action:

JPS-00173: OPSS Java Policy Provider is already set as the system-wide Policy object. Skipped setting the system-wide Policy object.
Category:: Configuration
Cause:
Action:

JPS-00174: Failed to create the enterprise user principal for "{0}". Reason: {1}.
Category:: Security
Cause:: Error on creating the enterprise user principal.
Action:: Check the configuration.

JPS-00175: Failed to create the enterprise group principal for "{0}". Reason: {1}.
Category:: Security
Cause:: Error on creating the enterprise group principal.
Action:: Check the configuration.

JPS-00176: Service instance of {0} is in state {1} that does not allow invocation of {2}.
Category:: Security
Cause:: Service instance is in a state that does not allow current invocation.
Action:: Only invoke service instance's method when it is in right state.

JPS-00177: Failed to clean up application security artifacts.
Category:: Deployment
Cause:: Error on cleaning up application security artifacts.
Action:: Check the configuration.

JPS-00178: Service provider " {0} " not available from configuration service.
Category:: Security
Cause:: Service provider not available.
Action:: Check the configuration.

JPS-00179: Service context configuration for " {0} " not available from configuration service.
Category:: Security
Cause:: Service context configuration not available.
Action:: Check the configuration.

JPS-00180: Failed to create service context for tenant ID " {0} ".
Category:: Security
Cause:: Failed to create service context.
Action:: Check the configuration.

JPS-00181: Your search criteria (current search iterator) has expired(stale). Start a new search.
Category:: Other
Cause:: Your search criteria (current search iterator) has expired(stale).
Action:: Start a new search.

JPS-00182: Method getView for JpsConfigurationP was not run for RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter
Category:: Configuration
Cause:: Method getView for JpsConfigurationP was not run for RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter
Action:: Call method getView for JpsConfigurationP on RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter

JPS-00183: Jps diagnostics started.
Category:: Other
Cause:
Action:

JPS-00184: Jps diagnostics startup failed.
Category:: Other
Cause:: Failed to start JPS diagnostics.
Action:: Check the configuration.

JPS-00185: Tenant Context is not set
Category:: Security
Cause:: Tenant Context is not set
Action:: Check the configuration.

JPS-00186: Failed to validate the Tenant Context for the tenant with ID " {0} ".
Category:: Security
Cause:: Tenant Context is Invalid
Action:: Only invoke services that you signed up for

JPS-00187: A dump to execute JPS diagnostic tests.
Category:: Other
Cause:
Action:

JPS-00188: Dumps security information in current execution thread, such as application name, subject, etc.
Category:: Other
Cause:
Action:

JPS-00189: OPSS diagnostic test to execute.
Category:: Other
Cause:
Action:

JPS-00190: Tenant ID cannot be found from user "{0}" profile.
Category:: Other
Cause:: Tenant ID cannot be found from authenticated user profile.
Action:: Check user profile.

JPS-00191: Identity context not found.
Category:: Other
Cause:: IdentityContext not found from request attributes.
Action:: OAM IAP.

JPS-00192: Service instance not found for the service type.
Category:: Security
Cause:: Service instance not available for the service type.
Action:: Check the configuration.

JPS-00193: Service instance "{0}" cannot be instantiated. Reason: {1}.
Category:: Security
Cause:: Service instance cannot be instantiated.
Action:: Check the configuration.

JPS-00194: OPSS diagnostic test parameters to execute. Example: username=user1;groupname=group1
Category:: Other
Cause:
Action:

JPS-00195: Dumps properties used to initialize User/Role Api when User/Role Api initialization fails.
Category:: Other
Cause:
Action:

JPS-00196: Jps started.
Category:: Security
Cause:
Action:

JPS-00197: Failed to migrate application credential during deployment.
Category:: Configuration
Cause:: Migration of Application credential failed during deployment.
Action:: Check the server logs for details.

JPS-00198: Custom product logger set (class: {0}, name: {1}). All JPS messages would be redirected to this logger.
Category:: Configuration
Cause:
Action:

JPS-00199: JpsLogger has initialized Loggers. Cannot set custom product Logger after initializing loggers.
Category:: Configuration
Cause:: Loggers have already been initialized.
Action:: Set product logger before creating JpsLogger instance.

JPS-00200: Invalid path. Please make sure the provided config path is a directory.
Category:: Configuration
Cause:
Action:

JPS-00201: Invalid path. Please make sure the provided config directory has jps-config.xml and jps-config-jse.xml inside it.
Category:: Configuration
Cause:
Action:

JPS-00202: Jps post service activation operations started.
Category:: Security
Cause:
Action:

JPS-00203: Upgrade of file based domain not supported
Category:: Configuration
Cause:: Upgrading of file based domain not supported
Action:: Please move the file based domain to database based domain, then run reconfiguration

JPS-00204: Migrate source or destination store context lookup failure
Category:: Configuration
Cause:: Migrate source or destination context in migration could not be looked up.
Action:: Check the configuration file to verify service context settings

JPS-00205: Security store version configured is incompatible
Category:: Configuration
Cause:: Security store version configured is incompatible with this release.
Action:: Please use security store version 12.1.3 or lower

JPS-00206: Jps is already started.
Category:: Security
Cause:: Can not start Jps again since it is already started.
Action:: Please do not start JPS if it is already started

JPS-00207: Service context {0} is not in active state
Category:: Security
Cause:: Service context is not in active state.
Action:: Please check logs to see service context failure.

JPS-00208: Jps initializing.
Category:: Security
Cause:
Action:

JPS-00209: Jps startup failed.
Category:: Security
Cause:: Jps startup is failed due to some error.
Action:: Please check logs to see Jps startup failure.

JPS-00210: Jps inactive.
Category:: Security
Cause:
Action:

JPS-00211: Not supported platform type {0}.
Category:: Security
Cause:
Action:

JPS-00212: Error occurred while stopping jps due to: {0}.
Category:: Configuration
Cause:: Error occured while stopping the OPSS
Action:: Check the server logs for details.

JPS-00213: Parameter "{0}" cannot be null.
Category:: Data
Cause:: method parameter cannot be null
Action:: provide a non-null value for the parameter

JPS-00214: Operation "{0}" is not supported in OPSS Mode "{1}".
Category:: Configuration
Cause:: the invoked operation is not supported in JPS_API mode
Action:: set the OPSS Mode to one of COMPATIBLE or MULTIPLE

JPS-00215: executeAs: Switching SecurityContext from "{0}" to "{1}" is not permitted.
Category:: Configuration
Cause:: the requested SecurityContext Switch is not Permitted
Action:: Look at documentation for allowed context switches

JPS-00216: Failed to get a handle to the global audit service for tenant {0}.
Category:: Security
Cause:: Failed to get a handle to the global audit service
Action:: Check configuration

JPS-00217: The schema specified in {0} is already in use for security store. Please create a new schema.
Category:: Configuration
Cause:: The schema specified in {0} is already in use for security store.
Action:: Please create a new schema.

JPS-00218: Comparison of credential failed for map : {0}, key : {1}.
Category:: Requests/Responses
Cause:: Encryption key comparison failed.
Action:: Retry importEncryptionKey command or api.

JPS-00219: Expected keys not found in the credential map : {0}.
Category:: Requests/Responses
Cause:: Expected keys not found in the credential map
Action:: Verify the credential store content.

JPS-00220: Cannot find datasource definition {0}. Reason: {1}.
Category:: Security
Cause:: Cannot find datasource definition {0}. Reason: {1}.
Action:: Check weblogic configuration.

JPS-00221: Error occurred while resetting jps due to: {0}.
Category:: Configuration
Cause:: Error occured while resetting OPSS
Action:: Check the server logs for details.

JPS-00222: Jps is reset.
Category:: Security
Cause:
Action:

JPS-00223: Specified JPS context "{0}" not found
Category:: Security
Cause:: Specified JPS context not found
Action:: Check the input configuration that the correct context name is present and is the one supplied as input.

JPS-00224: Invalid inputted migration parameters "{0}"
Category:: Security
Cause:: Invalid inputted migration parameters
Action:: Check inputted migration parameters.

JPS-00225: Commmand: {0} is not supported.
Category:: Configuration
Cause:: Commmand: {0} is not supported.
Action:: Use a valid command. Try <command> --help for more information.

JPS-00226: Service setup check completed for configurator.
Category:: Process
Cause:: Service setup check completed for configurator.
Action:: No Action Required

JPS-00227: Completed the Migration of Policy Artifacts.
Category:: Upgrade
Cause:: Completed the Migration of Policy Artifacts.
Action:: No actions are required.

JPS-00228: Security store is not seeded with the schema.
Category:: Other
Cause:: Security store is not seeded with the schema.
Action:: Check the log files to resolve the warning.

JPS-00229: Trying to load the schema into the security store ...
Category:: Process
Cause:: Trying to load the schema into the security store ...
Action:: No action required.

JPS-00230: BootStrap Wallet file is created.
Category:: Programmatic
Cause:: BootStrap Wallet file is created.
Action:: No action required

JPS-00231: Completed the seeding of schema into the security store.
Category:: Other
Cause:: Completed the seeding of schema into the security store.
Action:: No action required.

JPS-00232: Successfully loaded the security store schema.
Category:: Process
Cause:: Successfully loaded the security store schema.
Action:: No action required.

JPS-00233: Migration of Policy Artifacts failed.
Category:: Upgrade
Cause:: Migration of Policy Artifacts failed.
Action:: Check the log files for details.

JPS-00234: Persist jps-config.xml to directory: {0} - done.
Category:: Configuration
Cause:: Persist jps-config.xml to directory: {0} - done.
Action:: No action Required.

JPS-00235: Persist jps-config-jse.xml to directory: {0} - done.
Category:: Configuration
Cause:: Persist jps-config-jse.xml to directory: {0} - done.
Action:: No action Required.

JPS-00236: Bootstrap key store service instance already present in bootstrap credential store context.
Category:: Process
Cause:: Bootstrap key store service instance already present in bootstrap credential store context.
Action:: No Action Required

JPS-00237: Adding keystore service instance to bootstrap context for the {0} file.
Category:: Process
Cause:: Adding keystore service instance to bootstrap context for the {0} file.
Action:: No Action Required

JPS-00238: Error in loading the property file.
Category:: Configuration
Cause:: Error in loading the property file.
Action:: Check the log files to resolve the error.

JPS-00239: Exception while updating the keystore service instance to bootstrap context for {0} file.
Category:: Process
Cause:: Exception while updating the keystore service instance to bootstrap context for {0} file.
Action:: Check the log files to resolve the error.

JPS-00240: JpsConfiguration object is not passed, not able to add Keystore service instance to Bootstrap context.
Category:: Configuration
Cause:: JpsConfiguration object is not passed, not able to add Keystore service instance to Bootstrap context.
Action:: Check the log files to resolve the error.

JPS-00241: No file based keystore service instance is found, not able to add Keystore service instance to Bootstrap context.
Category:: Configuration
Cause:: This operation is not supported in restricted-JRF domain
Action:: Please check document for supported operations in restricted-JRf domain

JPS-00242: This operation is not supported in restricted-JRF domain
Category:: Configuration
Cause:: No file based keystore service instance is found, not able to add Keystore service instance to Bootstrap context.
Action:: Check the log files to resolve the error.

JPS-00243: {0} cannot be started as JRF Executor serivce retrieval got failed.
Category:: Security
Cause:: {0} cannot be started as JRF Executor serivce retrieval got failed.
Action:: Check stack trace for more details.

JPS-00244: No audit log directory is set. Cannot perform audit operations for component {0}.
Category:: Configuration
Cause:: Failed to get audit log directory. Audit calls may fail.
Action:: Check if the audit log directory is set either in audit service properties or as a system property.

JPS-00245: No audit log directory is set. Disabling audit for component {0}.
Category:: Configuration
Cause:: Failed to get audit log directory.
Action:: Check if the audit log directory is set either in audit service properties or as a system property.

JPS-00246: new Startup().start() is required to be called before using OPSS API.
Category:: Configuration
Cause:: OPSS API is used without calling new JpsStartup().start() first.
Action:: Call new JpsStartup().start() before using OPSS API.

JPS-00247: Could not retrieve tenant context.
Category:: Configuration
Cause:: Tenant context could not be retrieved.
Action:: Ensure tenant has been provisioned.

JPS-00248: This JpsStartup object was cleaned up. To start OPSS again, need create a new instance of JpsStartup.
Category:: Configuration
Cause:: The start() method is called on an JpsStartup object that was cleaned up.
Action:: Create a new instance of JpsStartup, then call the start() method on it.

JPS-00249: Operation "{0}" can only be performed when OPSS is in state "{1}". Current state is {2}.
Category:: Configuration
Cause:: Operation "{0}" can only be performed when OPSS is in state "{1}". Current state is {2}.
Action:: Perform operation "{0}" only when OPSS is in state "{1}".

JPS-00250: OPSS is already pre-started.
Category:: Configuration
Cause:: preStart() is called when OPSS is already pre-started.
Action:: Do not call preStart() if OPSS is already pre-started.

JPS-00251: This JpsStartup object is already reset.
Category:: Configuration
Cause:: reset() on a JpsStartup object is called when the object is already reset.
Action:: Do not call reset() when the JpsStartup objet is already reset.

JPS-00252: The {0} operation starting for partition {1}.
Category:: Process
Cause:: Starting the operation for partition.
Action:: No Action Required

JPS-00253: The {0} operation completed for partition {1}.
Category:: Process
Cause:: Completed the operation for partition.
Action:: No Action Required

JPS-00254: Tenant services {0} successfully for partition {1}.
Category:: Process
Cause:: Tenant services operation done successfully for partition.
Action:: No Action Required

JPS-00255: JPS post service started.
Category:: Process
Cause:: JPS post service started.
Action:: No Action Required

JPS-00256: JPS default service started.
Category:: Process
Cause:: JPS default service started.
Action:: No Action Required

JPS-00257: JPS bootstrap service started.
Category:: Process
Cause:: JPS bootstrap service started.
Action:: No Action Required

JPS-00258: Bootstrap services are used by OPSS internally and clients should never need to directly read/write bootstrap credentials. If required, use Wlst or configuration management interfaces.
Category:: Configuration
Cause:: An attempt to obtain bootstrap context is made.
Action:: Use WLST commands like addBootstrapCredential /modifyBootstrapCredential if required.

JPS-00259: Cannot terminate OPSS service context for partition {0}. Reason {1}.
Category:: Configuration
Cause:: Cannot terminate OPSS service context for partition {0}. Reason {1}.
Action:: Check reason for detail

JPS-00260: Database access error. SQL state: {0}, error code: {1}.
Category:: Configuration
Cause:: Database access error. SQL state: {0}, error code: {1}.
Action:: Check log for detail.

JPS-00261: Invalid value for "order" : {0} in service instance reference {1}
Category:: Configuration
Cause:: Configuration is corrupt.
Action:: Correct the configuration

JPS-00262: Duplicate value for "order" : {0} in service instance reference {1}
Category:: Configuration
Cause:: Configuration is corrupt.
Action:: Correct the configuration

JPS-00263: Cannot modify read only artifacts
Category:: Requests/Responses
Cause:: An attempt to modify/delete read only artifacts has been made.
Action:: Read only artifacts cannot be modified at runtime.

JPS-00264: Database is disconnected. SQL state: {0}, error code: {1}.
Category:: Configuration
Cause:: Database is disconnected. SQL state: {0}, error code: {1}.
Action:: Check log for detail.

JPS-00265: executeAs: SecurityContext with name "{0}" does not exist
Category:: Configuration
Cause:: The requested SecurityContext does not exist
Action:: Input a valid SecurityContxt name

JPS-00266: System property oracle.net.tns_admin has been set, OPSS can not overwrite it.
Category:: Configuration
Cause:: System property oracle.net.tns_admin has been set, OPSS can not overwrite it.
Action:: Skip setting tns property

JPS-00267: Tenant context already exists - {0}.
Category:: Requests/Responses
Cause:: The tenant context already activated.
Action:: No actions are required.

JPS-00268: Tenant context not activated - {0}.
Category:: Requests/Responses
Cause:: The tenant context not activated.
Action:: No actions are required.

JPS-00269: Client name "{0}" is too long.
Category:: Other
Cause:: Client name is too long when calling opssRestClient to register a client.
Action:: Make client name shorter

JPS-00270: Datasource ID {0} from tenant context {1} conflicts with tenant context {2}.
Category:: Other
Cause:: Datasource ID from DataSourceCallback handler conflicts with existing tenant.
Action:: Make client name shorter

JPS-00271: Exception occurs during JpsStartup start. Reason {0}. Will retry {1} time(s) in next {2} seconds.
Category:: Other
Cause:: Exception occurs during JpsStartup start, will retry
Action:: Check cause of failure

JPS-00272: Exception occurs during JPS API "{0}" called. Reason {1}. Will retry {2} time(s) in next {3} seconds.
Category:: Other
Cause:: Exception occurs during JPS API call, will retry
Action:: Check cause of failure

JPS-00273: Tenant context activated - {0}.
Category:: Requests/Responses
Cause:: The tenant context activated.
Action:: No actions are required.

JPS-00274: Tenant context {0} activation failed. Error: {1}.
Category:: Requests/Responses
Cause:: The tenant context activation failed.
Action:: No actions are required.

JPS-00648: Operation is not supported - unable to set key entry for non-existent stripe and keystore.
Category:: Compliance
Cause:: Combining certs from two truststores into a single truststore failed
Action:: Look at the logs for any exceptions that could have caused this failure

JPS-00649: ************************************************************** * Demonstration CA was found in use in this environment. * * This deployment may be vulnerable to security attacks. * * Replace the Demonstration CA with a custom CA immediately. * ****************************************************************
Category:: Compliance
Cause:: Demonstration CA was found in use in a production environment.
Action:: Refer documentation to switch to a custom CA.

JPS-00650: Virtual KSS URI to aggregate multiple keystores already exists
Category:: Compliance
Cause:: The virtual KSS URI passed in already exists
Action:: Use a different virtual KSS URI

JPS-00651: Aggregation of multiple keystores pointed by virtual URI failed
Category:: Compliance
Cause:: Aggregation of Keystores pointed to by virtual URI failed
Action:: Check if the source Keystores pointed to by virtual URI are valid

JPS-00652: Cannot set or save entries in virtual keystore
Category:: Compliance
Cause:: Setting of an entry in a virtual Keystore failed
Action:: Entries cannot be saved to a virtual Keystore

JPS-00653: Cannot save a virtual keystore
Category:: Compliance
Cause:: Saving a virtual Keystore failed
Action:: A virtual keystore cannot be persisted

JPS-00654: Cannot delete a virtual keystore that does not exist
Category:: Compliance
Cause:: Deleting a virtual Keystore failed
Action:: Cannot delete a virtual keystore that does not exist

JPS-01000: The credential map {0} is invalid.
Category:: Requests/Responses
Cause:: The specified credential map name was invalid.
Action:: Ensure the credential map name is valid.

JPS-01001: The credential key {0} is invalid.
Category:: Requests/Responses
Cause:: The specified credential key name was invalid.
Action:: Ensure the credential key name is valid.

JPS-01002: The value {0} is invalid in this password credential.
Category:: Requests/Responses
Cause:: The specified password credential was invalid.
Action:: Use only a supported credential type. The supported types are {0}.

JPS-01003: The value of name {0}, url {1}, of port {2} is invalid in this datasource credential.
Category:: Requests/Responses
Cause:: The specified datasource credential was invalid.
Action:: Use only a supported credential type. The supported types are {0}.

JPS-01004: The value {0} is invalid in this generic credential.
Category:: Requests/Responses
Cause:: The specified generic credential was invalid.
Action:: Use only a supported credential type. The supported types are {0}.

JPS-01005: The credential type {0} is not supported.
Category:: Requests/Responses
Cause:: The specified credential type was invalid.
Action:: Use only a supported credential type. The supported types are {0}.

JPS-01006: The credential expired on {0}.
Category:: Requests/Responses
Cause:: This credential expired on {0}.
Action:: Create a new credential.

JPS-01007: The credential with map {0} and key {1} already exists.
Category:: Requests/Responses
Cause:: This credential already existed.
Action:: Use a credential with different map name or key.

JPS-01008: The credential map name {0} already exists.
Category:: Requests/Responses
Cause:: This credential map name already existed.
Action:: Use a different map name.

JPS-01009: The credential with map {0} and key {1} does not exist.
Category:: Requests/Responses
Cause:: This credential did not exist.
Action:: Check the credential map name and key.

JPS-01010: The credential map {0} does not exist.
Category:: Requests/Responses
Cause:: This credential map name did not exist.
Action:: Check the credential map name.

JPS-01011: The credential store location property {0} is not configured, or the configured value {1} is invalid.
Category:: Configuration
Cause:: The credential store location was not specified.
Action:: Check the value of the location attribute.

JPS-01012: The credential property {0} is invalid or not defined.
Category:: Requests/Responses
Cause:: The credential property {0} was invalid or not defined.
Action:: Check the configuration of this property.

JPS-01013: The credential store DN {0} is missing in the store; the target DN must be pre-configured.
Category:: Requests/Responses
Cause:: The expected credential store DN {0} was missing.
Action:: Configure this DN during the bootstrap process.

JPS-01014: The credential {0} is invalid.
Category:: Requests/Responses
Cause:: This credential was invalid.
Action:: Use only a supported credential type. The supported types are password or generic.

JPS-01015: Cannot retrieve credential {0}.
Category:: Requests/Responses
Cause:: This credential was invalid.
Action:: Use only a supported credential type. The supported types are password or generic.

JPS-01016: A password credential is expected; instead found {0} for alias {1} and key {2} at location {3}.
Category:: Other
Cause:: Wrong credential type was found.
Action:: Use the password credential type. Expecting password credential but found {0} for alias {1} and key {2} at location {3}.

JPS-01017: A generic credential is expected; instead found {0}.
Category:: Other
Cause:: Wrong credential type was found.
Action:: Use the generic credential type. Expecting generic credential but found {0}.

JPS-01018: A password credential is missing in the credential store.
Category:: Session
Cause:: The password credential was not found in the credential store.
Action:: Ensure that the credential is present in the credential store.

JPS-01019: The credential store {0} has been moved or deleted.
Category:: Configuration
Cause:: The specified credential store did not exist.
Action:: Ensure that the credential store location is valid.

JPS-01020: Cannot create store {0}.
Category:: Configuration
Cause:: Could not create the credential store.
Action:: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.

JPS-01021: The generic credential {0} is not serializable.
Category:: Requests/Responses
Cause:: This generic credential was not serializable.
Action:: Make this credential serializable.

JPS-01022: The expiration time {0} is invalid: the expiration time must be later than the creation time.
Category:: Requests/Responses
Cause:: Invalid credential expiration time.
Action:: Set the expiration time to a time later than the credential creation time.

JPS-01023: Store does not contain all expected maps. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01024: Store contains all expected maps. Result {0}.
Category:: Compliance
Cause:
Action:

JPS-01025: Store does not contain all expected credentials. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01026: Store contains all expected credentials. Result {0}.
Category:: Compliance
Cause:
Action:

JPS-01027: Cannot get credential map. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01028: successful getting of credential map
Category:: Compliance
Cause:
Action:

JPS-01029: successful getting of credential
Category:: Compliance
Cause:
Action:

JPS-01030: Cannot get credential. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01031: Cannot retrieve map names. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01032: successful setting of credential
Category:: Compliance
Cause:
Action:

JPS-01033: Cannot set credential. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01034: successful resetting of credential
Category:: Compliance
Cause:
Action:

JPS-01035: Cannot reset credential. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01036: successful setting of credential map
Category:: Compliance
Cause:
Action:

JPS-01037: Cannot set credential map. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01038: successful resetting of credential map
Category:: Compliance
Cause:
Action:

JPS-01039: Cannot reset credential map. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01040: successful deletion of credential
Category:: Compliance
Cause:
Action:

JPS-01041: Cannot delete credential. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01042: successful deletion of credential map
Category:: Compliance
Cause:
Action:

JPS-01043: Cannot delete credential map. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01044: successful deletion of all credentials from the store
Category:: Compliance
Cause:
Action:

JPS-01045: Cannot delete all credentials from the store. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01046: successful retrieving of map names; mapNameSet {0}.
Category:: Compliance
Cause:
Action:

JPS-01047: Cannot persist the wallet. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01048: Modifying of credential failed. Reason {0}
Category:: Compliance
Cause:: Modification of credential failed
Action:: Contact system administrator

JPS-01049: Reading all credentials from the store failed. Reason {0}
Category:: Compliance
Cause:: Read of all credentials failed
Action:: Contact system administrator

JPS-01050: Opening of wallet based credential store failed. Reason {0}
Category:: Compliance
Cause:: Credential wallet could not be opened
Action:: Contact system administrator

JPS-01051: Credential audit events cannot be logged. Reason {0}
Category:: Compliance
Cause:: Credential store audit events logging not enabled
Action:: Check the audit configuration to ensure auditing enabled

JPS-01052: Credential audit event logging failed. Reason {0}
Category:: Compliance
Cause:: Credential audit event logging failed
Action:: Contact system administrator

JPS-01053: Creation of new credential map failed. Reason {0}
Category:: Compliance
Cause:: Creation of new credential map failed
Action:: Ensure all jps libraries are in setup properly in the runtime

JPS-01054: Refresh of credential wallet failed. Reason {0}
Category:: Compliance
Cause:: Refresh of credstore wallet failed
Action:: Contact system administrator

JPS-01055: Could not create credential store instance. Reason {0}
Category:: Compliance
Cause:: Could not create credential store instance
Action:: Contact system administrator

JPS-01056: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.
Category:: Configuration
Cause:: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.
Action:: Check the value of the location property

JPS-01057: The credential map was invalid. Reason {0}
Category:: Requests/Responses
Cause:: The credential map was null.
Action:: Check the value of the credential map

JPS-01058: The credential dn {0} was invalid.
Category:: Requests/Responses
Cause:: The credential dn was invalid.
Action:: Ensure the credential dn is valid.

JPS-01059: The credential store instance {0} was not fully initialized.
Category:: Configuration
Cause:: The credential store was not fully initialized until data source is available.
Action:: Wait and retry later

JPS-01060: The credential store instance does not have the property ldap url/JDBC url/datasource JNDI name defined.
Category:: Configuration
Cause:: The credential store property ldap.url or jdbc.url or datasource.jndi.name was not defined.
Action:: Check the configuration for this property.

JPS-01061: Access to boostrap credential store denied to application code.
Category:: Security
Cause:: Application code was trying to access a bootstrap credential store. Bootstrap credential store is intended only for the OPSS usage.
Action:: bootstrap_credstore_context need not be used for credential store operations.

JPS-01062: A backup of the bootstrap credential store could not be created.
Category:: Security
Cause:: A backup of the bootstrap cwallet.sso could not be created.
Action:: Investigate the logs to find out the root cause of the exception in file operations

JPS-01063: Credential compatibility check failed. Cannot migrate credential: {0}
Category:: Security
Cause:: There exists one or more generic credential in the store that cannot be migrated.
Action:: Ensure that the store does not contain any generic credential with binary attribute before migration.

JPS-01064: Invalid password: Passwords must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.
Category:: Security
Cause:
Action:

JPS-01065: Could not decrypt a random credential
Category:: Security
Cause:: Decryption of credential failed
Action:: Ensure that the bootstrap wallet contains the correct encryption key that was used to encrypt the credentials in the store.

JPS-01066: Cannot get credential due to database disconnected. Reason {0}.
Category:: Compliance
Cause:
Action:

JPS-01067: Failed to retrieve customer encryption key password.
Category:: Security
Cause:: No password was specified in the custom callback.
Action:: Ensure that the password for decrypting customer encryption key is provided.

JPS-01068: Missing callback handler to provide context information
Category:: Security
Cause:: No custom callback to provide context information specified.
Action:: Ensure that a callback handler is specified.

JPS-01500: The anonymous service configuration is missing.
Category:: Configuration
Cause:: The anonymous service configuration was missing in jps-config.xml.
Action:: Configure the anonymous service in jps-config.xml.

JPS-01501: The anonymous identity store provider instance {0} is not found.
Category:: Configuration
Cause:: The anonymous identity store provider configuration was invalid.
Action:: Check the anonymous identity store provider configuration in jps-config.xml.

JPS-01502: The LDAP identity store provider instance {0} is not found.
Category:: Configuration
Cause:: Invalid or missing LDAP identity store provider configuration.
Action:: Check LDAP identity store provider configuration in jps-config.xml.

JPS-01503: The XML identity store provider instance {0} is not found.
Category:: Requests/Responses
Cause:: Invalid or missing XML identity store provider configuration.
Action:: Check the XML identity store provider configuration in jps-config.xml.

JPS-01504: The secret store provider for provider {0} and instance {1} does not exist.
Category:: Requests/Responses
Cause:: The credential provider was missing.
Action:: Check the configuration of the credential store provider in jps-config.xml.

JPS-01505: The key store provider {0} is missing or not configured.
Category:: Configuration
Cause:: The keystore provider configuration was missing in jps-config.xml.
Action:: Configure a keystore provider in jps-config.xml.

JPS-01506: Invalid context name.
Category:: Configuration
Cause:: Invalid context name found.
Action:: Check the configurations of contexts in jps-config.xml.

JPS-01507: Invalid login module name.
Category:: Configuration
Cause:: Invalid login module name found.
Action:: Check the login module configurations in jps-config.xml.

JPS-01508: Invalid login module descriptor.
Category:: Configuration
Cause:: Invalid login module descriptor found.
Action:: Check the login module instance configurations in jps-config.xml.

JPS-01509: Invalid login module class name.
Category:: Configuration
Cause:: Invalid login module class name found.
Action:: Check the loginModuleClassName property in the login module instance configuration in jps-config.xml.

JPS-01510: Invalid login module entries.
Category:: Configuration
Cause:: Invalid login module entries found.
Action:: The expected login module to be invoked is not present or misconfigured. Check the login module instance configurations in jps-config.xml.

JPS-01511: Invalid login module entry.
Category:: Configuration
Cause:: The login module entries were not valid in the jps-config.xml file.
Action:: Correct the login module entries in service instances and service providers.

JPS-01512: Missing login module entry.
Category:: Configuration
Cause:: The login module entries were missing in the jps-config.xml file.
Action:: Add the appropriate login module entries in service instances and service providers.

JPS-01513: The configuration of the JAAS login provider {0} and the service instance {1} are missing.
Category:: Configuration
Cause:: The login module provider was missing.
Action:: Ensure that a login module provider is configured in the jps-config.xml.

JPS-01514: The default context is missing in jps-config.xml.
Category:: Configuration
Cause:: Default context was missing in jps-config.xml.
Action:: Add a default context to jps-config.xml.

JPS-01515: A context named anonymous is missing in jps-config.xml.
Category:: Configuration
Cause:: Context named anonymous was missing in jps-config.xml.
Action:: Add a context named anonymous in jps-config.xml file with an anonymous service instance reference.

JPS-01516: The default credential store service is missing in default jps-config.xml.
Category:: Other
Cause:: The default credential store service was missing in the default context in jps-config.xml.
Action:: There must be at least one credential store service configured in the default context.

JPS-01517: The generic identity store provider is missing.
Category:: Configuration
Cause:: Invalid or missing generic identity store provider configuration.
Action:: Check the generic identity store provider configuration in jps-config.xml.

JPS-01518: The anonymous service is not available in the application context.
Category:: Session
Cause:: The anonymous service was not available in context.
Action:: Check the context in jps-config.xml.

JPS-01519: The default context configuration is missing in jps-config.xml.
Category:: Session
Cause:: The default context configuration was not available in jps-config.xml.
Action:: Ensure that the default context is present in jps-config.xml.

JPS-01520: Cannot initialize identity store, cause: {0}.
Category:: Configuration
Cause:: Could not initialize identity store.
Action:: Correct the identity store configuration.

JPS-01521: Identity store file path is invalid.
Category:: Configuration
Cause:: Identity store file path was invalid or null.
Action:: Ensure that the path configured with the property ADF_IM_FILE_PATH is valid.

JPS-01522: The Jps configuration is invalid.
Category:: Configuration
Cause:: JPS configuration was null or invalid.
Action:: Verify configuration in jps-config.xml.

JPS-01523: The service instance {0} is invalid or not configured in jps-config.xml.
Category:: Configuration
Cause:: A service instance configuration was not valid.
Action:: Verify that the instance is correctly configured in jps-config.xml.

JPS-01524: The service instance {0} is invalid or not configured in jps-config.xml.
Category:: Configuration
Cause:: A service provider configuration was invalid.
Action:: Veirfy that the provider is correctly configured in jps-config.xml.

JPS-01525: The identity store service is not properly configured.
Category:: Configuration
Cause:: Found invalid identity store service configuration in jps-config.xml.
Action:: Ensure a valid identity store configuration in jps-config.xml.

JPS-01526: Configured identity store, user manager, or role manager is invalid. The error is {0}.
Category:: Configuration
Cause:: Found null value for configured identity store, user manager, or role manager.
Action:: Correct the identity store configuration.

JPS-01527: The identity store factory name is not configured.
Category:: Configuration
Cause:: Could not find identity store factory name.
Action:: Use the property ADF_IM_FACTORY_CLASS to specify the factory class.

JPS-01528: Idm identity store is invalid.
Category:: Configuration
Cause:: The identity store was not configured correctly.
Action:: Correct the configuration of the identity store in jps-config.xml.

JPS-01529: The context {0} contains multiple services of type {1}.
Category:: Configuration
Cause:: The context {0} contains multiple services of type {0}.
Action:: Check jps-config.xml for correctness.

JPS-01530: The anonymous service is already configured in the context {0}.
Category:: Configuration
Cause:: The anonymous service is already configured in the context {0}.
Action:: Check jps-config.xml for correctness.

JPS-01531: Configuration location {0} is a directory. File name expected.
Category:: Configuration
Cause:: Configuration location {0} is a directory. File name expected.
Action:: Provide a valid configuration file location, including a file name.

JPS-01532: The service instance location {0} is invalid or not configured in jps-config.xml.
Category:: Configuration
Cause:: A service instance configuration was invalid.
Action:: Verify that the location of the instance is correctly configured in jps-config.xml.

JPS-01533: Failed to create service instance {0} for application {1}.
Category:: Configuration
Cause:: Failed to create service instance {0} for application {1}.
Action:: Check the log files to resolve the error.

JPS-01534: Failed to get identity store configuration.
Category:: Security
Cause:: Failed to get identity store configuration.
Action:: Ensure the configuration is available.

JPS-01535: Failed to get configuration name {0}.
Category:: Configuration
Cause:: Failed to get configuration name {0}.
Action:: Check the log files to resolve the error.

JPS-01536: Failed to evaluate XML expression on Object {0}.
Category:: Configuration
Cause:: Failed to evaluate XML expression on Object {0}.
Action:: Check the log files to resolve the error.

JPS-01537: Failed to handle config location {0}. Reason {1}.
Category:: Security
Cause:
Action:

JPS-01538: The default policy provider was not found.
Category:: Security
Cause:: The default policy provider was not found.
Action:: Ensure policy provider configuration is correct.

JPS-01539: The Ovd IGF service provider instance {0} is not found.
Category:: Configuration
Cause:: Invalid or missing Ovd IGF service provider configuration.
Action:: Check Ovd IGF service provider configuration in jps-config.xml.

JPS-01543: The value of {0} is invalid. It must be an integer.
Category:: Configuration
Cause:: attribute.expire.time.seconds is not an integer.
Action:: Ensure attribute.expire.time.seconds is a valid integer.

JPS-01544: The provided configuration file path {0} is invalid or null.
Category:: Configuration
Cause:: The provided configuration file path {0} is invalid or null.
Action:: Provide a valid configuration file path.

JPS-01545: Back up of JPS Config file {0} done.
Category:: Configuration
Cause:: Back up of JPS Config file {0} done.
Action:: No action required

JPS-02000: The authentication of user {0} succeeded.
Category:: Requests/Responses
Cause:
Action:

JPS-02001: The authentication of user {0} failed. Reason: {1}
Category:: Requests/Responses
Cause:: User authentication failed.
Action:: Ensure the user exists in the identity store. Check the user credentials that are being sent for authentication.

JPS-02003: Authentication failed.
Category:: Requests/Responses
Cause:: Could not authenticate user.
Action:: Ensure that authentication uses valid user name and password.

JPS-02004: Cannot authenticate user {0}.
Category:: Security
Cause:: Could not authenticate user.
Action:: Ensure that the credentials provided for authentication are correct.

JPS-02005: Cannot login user {0} because {1}. Check the log files for more details.
Category:: Requests/Responses
Cause:: Encountered an error while authenticating user.
Action:: Contact the domain administrator.

JPS-02008: Authenticated role name is invalid: property {0} is invalid or not configured.
Category:: Configuration
Cause:: Found invalid or undefined authentication role name property.
Action:: Ensure that authentication role name properties are valid in jps-config.xml.

JPS-02009: SAML trusted assertion issuer is not configured: property set {0} is not configured.
Category:: Configuration
Cause:: Could not find configuration for SAML trusted assertion issuer.
Action:: Set the property saml.trusted.issuers in jps-config.xml.

JPS-02010: Cannot verify SAML assertion.
Category:: Requests/Responses
Cause:: Found invalid assertion; SAML trusted assertion issuer was not configured.
Action:: Check assertion and set the property saml.trusted.issuers in jps-config.xml.

JPS-02011: SAML assertion is missing name identifier.
Category:: Requests/Responses
Cause:: Found invalid assertion: name identifier was missing.
Action:: Ensure the use of a valid assertion.

JPS-02012: SAML assertion subject name is invalid.
Category:: Requests/Responses
Cause:: Found invalid assertion: subject name was null.
Action:: Ensure the use of a valid assertion.

JPS-02013: SAML assertion issuer name is invalid.
Category:: Requests/Responses
Cause:: Found invalid assertion: issuer name was invalid.
Action:: Ensure the use of a valid assertion.

JPS-02014: SAML assertion is invalid.
Category:: Requests/Responses
Cause:: Found invalid assertion.
Action:: Ensure the use of a valid assertion.

JPS-02015: SAML assertion has missing subject.
Category:: Requests/Responses
Cause:: Found invalid assertion: subject statement was missing.
Action:: Ensure the use of a valid assertion.

JPS-02016: SAML assertion is missing conditions.
Category:: Requests/Responses
Cause:: Found invalid assertion: condition statement was missing.
Action:: Ensure the use of a valid assertion.

JPS-02017: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.
Category:: Requests/Responses
Cause:: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.
Action:: Verify that the condition "not before" in the SAML assertion is set to a date earlier than or equal to today's date.

JPS-02018: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.
Category:: Requests/Responses
Cause:: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.
Action:: Verify that the condition "on or after" in the SAML assertion is set to a valid date.

JPS-02019: SAML assertion is missing assertion issuers signature.
Category:: Requests/Responses
Cause:: Found invalid assertion: assertion issuers signature was missing.
Action:: Ensure the use of a valid assertion.

JPS-02020: Signature for SAML assertion issuer is invalid.
Category:: Configuration
Cause:: Found invalid signature in SAML assertion issuer.
Action:: Ensure the use of a valid assertion.

JPS-02021: Signature certificate (X509 Data) for SAML assertion issuer is invalid.
Category:: Configuration
Cause:: Found invalid signature certificate (X509 Data) in SAML assertion.
Action:: Ensure the use of a valid assertion.

JPS-02022: Cannot verify signature for SAML assertion.
Category:: Configuration
Cause:: Failed to verify issuers signature in assertion.
Action:: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.

JPS-02023: Cannot verify SAML assertion signature certificate path.
Category:: Configuration
Cause:: Found invalid assertion signature.
Action:: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.

JPS-02024: Cannot retrieve trusted CA policy for issuer {0}.
Category:: Configuration
Cause:: Found invalid assertion.
Action:: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.

JPS-02025: Cannot modify read-only Subject.
Category:: Requests/Responses
Cause:: Could not modify a read-only subject.
Action:: Ensure the program logic is correct and that the program does not attempt to modify a read-only subject.

JPS-02026: X509 certificate is invalid.
Category:: Other
Cause:: The X509 certificate passed to the callback handler was null or invalid.
Action:: Ensure that the callback handler uses a valid X509 certificate.

JPS-02027: The property set {0} is missing in jps-config.xml.
Category:: Configuration
Cause:: Could not find property set in jps-config.xml.
Action:: Configure the property set in jps-config.xml.

JPS-02028: The extended property set {0} is missing in jps-config.xml.
Category:: Configuration
Cause:: Could not find extended property set in jps-config.xml.
Action:: Configure the extended property set in jps-config.xml.

JPS-02029: The default realm is not configured in identity store service {0}.
Category:: Configuration
Cause:: Could not find the default realm in the identity store service.
Action:: Configure the default realm property in the identity store service.

JPS-02030: The default realm configured in identity store service {0} is empty or null.
Category:: Configuration
Cause:: Found null default realm configured in identity store service.
Action:: Configure the default realm property in the identity store service.

JPS-02031: The invalid realm name property {0} is configured in identity store service {1}.
Category:: Configuration
Cause:: Found invalid realm name property in identity store service.
Action:: Configure the correct realm name property in the identity store service.

JPS-02032: The duplicate realm name {0} is configured in identity store service {1}.
Category:: Configuration
Cause:: Found duplicate realm in identity store service.
Action:: Remove duplicate realm configuration from the identity store service.

JPS-02033: The realm name {0} passed for authentication is invalid. Was expecting {1}, but found {0}.
Category:: Configuration
Cause:: Found invalid realm name {0}. Was expecting {1}, but found {0}.
Action:: Check the realm name passed to the authentication of user name.

JPS-02034: Realm name is missing in user name for authentication in multi-realm configuration.
Category:: Configuration
Cause:: The realm name was not supplied for authentication of multi-realm configuration.
Action:: Ensure that the realm name value is passed in the user name when authenticating a multi-realm configuration.

JPS-02035: Cannot properly initialize the Kerberos authenticator.
Category:: Requests/Responses
Cause:: Could not initialize the Kerberos authenticator.
Action:: Check the log files for errors and contact the domain administrator.

JPS-02036: Browser does not support Kerberos authentication.
Category:: Requests/Responses
Cause:: Could not find support for Kerberos authentication, or it was not configured correctly.
Action:: Verify that the browser is set to allow Kerberos authentication.

JPS-02037: The SAML assertion issuer {0} certificate is missing from the keystore.
Category:: Configuration
Cause:: Could not find SAML assertion certificate in keystore.
Action:: Store the SAML assertion issuer's certificate in the keystore, and configure the trustpoint alias in JpsSAMLLoginModuule.

JPS-02038: The SAML assertion {0} is missing a signature.
Category:: Requests/Responses
Cause:: Could not find expected signature in assertion.
Action:: Check that the assertion sent has a valid signature.

JPS-02039: Cannot assert certificate. Reason {0}.
Category:: Requests/Responses
Cause:: Found invalid certificate, or could not find corresponding user in identity store.
Action:: Make sure that the assertion is valid.

JPS-02040: Both user identity and token were provided for assertion. Either user identity or token should be provided, not both.
Category:: Other
Cause:: Both user identity and token were provided for assertion.
Action:: Provide either user identity or a token for assertion, not both.

JPS-02041: Asserter class was configured as {0}, but does not implement {1}.
Category:: Other
Cause:: Assertor class was configured as {0}, but does not implement {1}.
Action:: Provide an Assertor that implements {1}.

JPS-02042: Token assertion failed.
Category:: Other
Cause:: Token assertion failed.
Action:: Check detailed logs for more information.

JPS-02043: User name cannot be null or empty.
Category:: Requests/Responses
Cause:: User name cannot be null or empty.
Action:: Check that the user name is not null or empty.

JPS-02044: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.
Category:: Requests/Responses
Cause:: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.
Action:: Check that the attesting entity for the SAML assertion is valid.

JPS-02045: Audience URI for SAML assertion is invalid.
Category:: Requests/Responses
Cause:: SAML assertion audience URI is invalid.
Action:: Check that the audience URI for the SAML assertion is valid.

JPS-02046: Cannot get the user name from SAML assertion name identifier: {0}.
Category:: Requests/Responses
Cause:: Cannot get the user name from SAML assertion name identifier: {0}.
Action:: Check that the name identifier for the SAML assertion is valid.

JPS-02047: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.
Category:: Other
Cause:: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.
Action:: Provide an SAMLNameIdentifierMapper that implements oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

JPS-02048: Incorrect password was provided.
Category:: Requests/Responses
Cause:: Incorrect password was provided.
Action:: Ensure that authentication uses correct password.

JPS-02049: Null or empty password was provided.
Category:: Requests/Responses
Cause:: Null or empty password was provided.
Action:: Ensure that authentication uses correct password.

JPS-02050: Signature verification failed. Principal: {0}
Category:: Security
Cause:: Signature verification failed.
Action:: This error is unlikely to occur. Contact technical support when necessary.

JPS-02051: No auth module to validate request: auth context ID "{0}" of application context "{1}".
Category:: Security
Cause:: Server auth context did not have auth module to validate request.
Action:: Ensure that the server auth module is properly configured and bound for use by applications.

JPS-02052: No auth module to secure response: auth context ID "{0}" of application context "{1}".
Category:: Security
Cause:: Server auth context did not have auth module to secure response.
Action:: Ensure that the server auth module is properly configured and bound for use by applications.

JPS-02053: No auth module to validate response: auth context ID "{0}" of application context "{1}".
Category:: Security
Cause:: Client auth context did not have auth module to validate response.
Action:: Ensure that the client auth module is properly configured and bound for use by applications.

JPS-02054: No auth module to secure request: auth context ID "{0}" of application context "{1}".
Category:: Security
Cause:: Client auth context did not have auth module to secure request.
Action:: Ensure that the client auth module is properly configured and bound for use by applications.

JPS-02055: Cannot instantiate auth module class "{0}" for application context "{1}", cause: {2}.
Category:: Security
Cause:: Could not load the auth module.
Action:: Ensure that the module class name is correctly supplied and the class is in the class path.

JPS-02056: The auth module must support message type: {0}.
Category:: Security
Cause:: Auth module did not support the required message type.
Action:: Ensure that the class correctly implements the required auth module interfaces.

JPS-02057: The message layer "{0}" is not supported.
Category:: Requests/Responses
Cause:: The specified message layer was not supported.
Action:: Provide a valid message layer.

JPS-02058: Null callback handler is not supported.
Category:: Requests/Responses
Cause:: The specified callback handler was null.
Action:: Supply a non-null callback handler.

JPS-02059: The default auth provider "{0}" for layer "{1}" is not configured.
Category:: Configuration
Cause:: The default auth provider was not configured.
Action:: Ensure that the provider is configured in jps-config.xml.

JPS-02060: The auth module "{0}" is missing.
Category:: Configuration
Cause:: The specified auth module did not exist.
Action:: Configure the auth module in jps-config.xml.

JPS-02061: No auth module configured for provider "{0}".
Category:: Configuration
Cause:: No auth module configured for the specified provider.
Action:: Configure an auth module for the provider in jps-config.xml.

JPS-02062: Cannot determine the JDK vendor. Defaults to Oracle JDK Kerberos Login Module.
Category:: Configuration
Cause:: Cannot determine the JDK vendor. Defaults to Oracle JDK Kerberos Login Module.
Action:: See error message.

JPS-02063: Failed to create Kerberos Login Module instance "{0}". Reason: {1}.
Category:: Requests/Responses
Cause:: Failed to create Kerberos Login Module instance "{0}". Reason: {1}.
Action:: Ensure that the Login Module class name is correctly supplied and the class is in the class path.

JPS-02064: Cannot retrieve value for key {0}. Expecting key type {1}, found {2}.
Category:: Configuration
Cause:: Found invalid object type in role mapping map for key {0}. Expecting {1}, Found {2}.
Action:: Check the role mapping values passed in the callback.

JPS-02066: Cannot map default service role
Category:: Configuration
Cause:: default service roles are missing in the role mapping provided.
Action:: Check the role mapping values passed in the callback. Default service role should be provided if mapping of roles is enabled but mapping is not provided

JPS-02500: The principal name is invalid.
Category:: Requests/Responses
Cause:: Found null principal name.
Action:: Check the principal name.

JPS-02501: The principal type {0} is invalid.
Category:: Requests/Responses
Cause:: Found invalid principal type.
Action:: Check the principal type.

JPS-02502: The password {0} is invalid.
Category:: Data
Cause:: Found invalid password.
Action:: Check the password passed to create user account.

JPS-02503: The user name {0} is invalid.
Category:: Data
Cause:: Found invalid user name.
Action:: Ensure that the user name used to create, fetch, or remove the account is valid.

JPS-02504: The user range starting at {0} and ending at {1} is not a valid range.
Category:: Data
Cause:: The user range was invalid.
Action:: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.

JPS-02505: The group {0} is invalid.
Category:: Data
Cause:: Group name was invalid.
Action:: Check the group name that is being sent for creating/fetching/removing group.

JPS-02506: The group range starting at {0} and ending at {1} is not valid range.
Category:: Data
Cause:: The JPSUserManager.getGroups() method was invoked with invalid start or end range.
Action:: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.

JPS-02507: The anonymous user is not found.
Category:: Session
Cause:: The anonymous user was not found.
Action:: Ensure that a valid anonymous user is configured.

JPS-02508: The anonymous user name is invalid; property {0} is invalid or not defined.
Category:: Configuration
Cause:: The anonymous.user.name property was not configured in the anonymous service configuration.
Action:: Configure the anonymous.user.name property to a valid user name in the identity store while configuring the Anonymous Service.

JPS-02509: The user {0} already exists in the store; choose a different user name.
Category:: Requests/Responses
Cause:: The specified user name already existed in the store.
Action:: Provide a different user name.

JPS-02510: The group {0} already exists in the store; choose a different group name.
Category:: Requests/Responses
Cause:: The specified group name already existed in the store.
Action:: Provide a different group name.

JPS-02511: The role for group {0} is invalid.
Category:: Requests/Responses
Cause:: Found null role in group.
Action:: Check the group's name.

JPS-02512: Cannot create a new user {0}.
Category:: Configuration
Cause:: Could not create user.
Action:: Ensure that the user name is valid and distinct from any other existing user name.

JPS-02513: Cannot drop user {0}.
Category:: Configuration
Cause:: Could not drop the user.
Action:: Ensure this user already exists.

JPS-02514: Cannot retrieve user profile.
Category:: Configuration
Cause:: Could not get profile for user.
Action:: Ensure that the user exists.

JPS-02515: Cannot update user profile.
Category:: Configuration
Cause:: Could not set profile for user.
Action:: Ensure that the user exists.

JPS-02516: Cannot retrieve role profile.
Category:: Configuration
Cause:: Could not get role profile.
Action:: Ensure that the role exists.

JPS-02517: Cannot update role profile.
Category:: Configuration
Cause:: Could not set role profile.
Action:: Ensure that the role exists.

JPS-02518: Cannot create role {0}.
Category:: Security
Cause:: Could not create role.
Action:: Ensure that the role exists.

JPS-02519: Cannot drop role {0}.
Category:: Configuration
Cause:: Could not drop role.
Action:: Ensure that the role exists.

JPS-02520: Cannot grant role to the principal.
Category:: Configuration
Cause:: Could not grant permission to role.
Action:: Ensure that the permission is set for the role.

JPS-02521: Cannot revoke role from principal.
Category:: Configuration
Cause:: Could not revoke role.
Action:: Check that the correct permission to revoke the role is set.

JPS-02522: Cannot add user to role owners.
Category:: Configuration
Cause:: Could not add owner to role.
Action:: Check log files and correct the appropriate configuration.

JPS-02523: Cannot remove user from role owners.
Category:: Configuration
Cause:: Could not remove owner from role.
Action:: Check log files and correct the appropriate configuration.

JPS-02524: Cannot retrieve role owners.
Category:: Configuration
Cause:: Could not get role owners.
Action:: Check log files and correct the appropriate configuration.

JPS-02525: Cannot retrieve role grantees.
Category:: Configuration
Cause:: Could not get role grantees.
Action:: Check log files and correct the appropriate configuration.

JPS-02526: Cannot retrieve the roles granted to principal.
Category:: Configuration
Cause:: Could not get granted roles.
Action:: Check log files and correct the appropriate configuration.

JPS-02527: Cannot close identity store.
Category:: Configuration
Cause:: Could not close identity store.
Action:: Check log files and correct the appropriate configuration.

JPS-02528: Cannot obtain a handle for role manager MBean.
Category:: Configuration
Cause:: Could not get role manager object name.
Action:: Check log files and correct the appropriate configuration.

JPS-02529: Cannot obtain a handle for user manager MBean.
Category:: Configuration
Cause:: Could not get user manager object name.
Action:: Check log files and correct the appropriate configuration.

JPS-02530: Cannot get a list of searchable attributes.
Category:: Configuration
Cause:: Could not get searchable attributes.
Action:: Check log files and correct the appropriate configuration.

JPS-02531: Cannot get list of user property names.
Category:: Configuration
Cause:: Could not get user property names.
Action:: Check log files and correct the appropriate configuration.

JPS-02532: Cannot parse principals of role.
Category:: Configuration
Cause:: Could not parse role principals.
Action:: Check log files and correct the appropriate configuration.

JPS-02533: Cannot parse principals of user.
Category:: Configuration
Cause:: Could not parse user principals.
Action:: Check log files and correct the appropriate configuration.

JPS-02534: Cannot find role {0}.
Category:: Configuration
Cause:: Could not completer search role operation.
Action:: Correct the role name and, if necessary, contact the domain administrator.

JPS-02535: Cannot complete search for roles.
Category:: Configuration
Cause:: Could not complete search for multiple roles.
Action:: Correct role names and, if necessary, contact the domain administrator.

JPS-02536: Cannot complete search for user {0}.
Category:: Configuration
Cause:: Could not completer user search.
Action:: Correct user name and, if necessary, contact the domain administrator.

JPS-02537: Cannot complete search for users.
Category:: Configuration
Cause:: Could not complete search for multiple users.
Action:: Correct user names and, if necessary, contact the domain administrator.

JPS-02538: Cannot complete search operation.
Category:: Configuration
Cause:: Failed to complete search.
Action:: Correct the search query.

JPS-02539: Cannot change password of user {0}.
Category:: Configuration
Cause:: Could not change password.
Action:: Contact the domain administrator.

JPS-02540: User {0} not found in the identity store.
Category:: Configuration
Cause:: User {0} not found in the identity store.
Action:: Ensure user is valid.

JPS-02541: Identity store has an invalid configured subscriber name.
Category:: Configuration
Cause:: Found invalid subscriber name.
Action:: Correct the configuration of property subscriber.name.

JPS-02542: unknown identity store service type {0}.
Category:: Configuration
Cause:: Found unknown identity store service type {0}.
Action:: Correct the identity store configuration.

JPS-02543: Search type {0} is invalid.
Category:: Other
Cause:: Found invalid search type {0}.
Action:: Correct the type passed for the search.

JPS-02544: Operation type {0} is invalid.
Category:: Other
Cause:: Found invalid operation type {0}.
Action:: Correct the type passed for the operation.

JPS-02545: Search filter type {0} is invalid.
Category:: Other
Cause:: Found invalid search filter type {0}.
Action:: Correct the type passed for the search filter.

JPS-02546: Scope type is invalid {0}.
Category:: Other
Cause:: Found invalid scope type {0}.
Action:: Correct the type passed for the scope.

JPS-02547: Cannot create realm {0}.
Category:: Requests/Responses
Cause:: Could not created realm.
Action:: Check log files for error details.

JPS-02548: Cannot delete realm {0}.
Category:: Requests/Responses
Cause:: Could not delete realm.
Action:: Check log files for error details.

JPS-02549: A realm with the specified name already exists.
Category:: Requests/Responses
Cause:: A realm with the specified name already exists.
Action:: Choose a different realm name.

JPS-02550: The realm {0} does not exist.
Category:: Requests/Responses
Cause:: Could not find realm with the name {0}.
Action:: Correct the supplied realm name.

JPS-02551: Cannot perform an unsupported operation on a serialized object.
Category:: Requests/Responses
Cause:: Could not perform operation on serialized object.
Action:: Check log files for error details.

JPS-02552: Cannot add a duplicate owner.
Category:: Data
Cause:: Attempted to add already present owner.
Action:: Correct the owner's name.

JPS-02553: Cannot remove an owner that is not present.
Category:: Data
Cause:: Attempted to remove a non existing owner.
Action:: Correct the owner's name.

JPS-02554: Cannot add a duplicate member.
Category:: Requests/Responses
Cause:: Attempted to add already present member.
Action:: Correct the member's name.

JPS-02555: Cannot complete identity store operation. The error is {0}.
Category:: Requests/Responses
Cause:: Could not perform identity store operation.
Action:: Check error log files for details.

JPS-02556: Run into error {0} while using identity store.
Category:: Requests/Responses
Cause:: Run into an internal identity store error.
Action:: Check error log files for details.

JPS-02557: The group {0} is invalid.
Category:: Requests/Responses
Cause:: Found null or invalid group.
Action:: Correct the group's name.

JPS-02558: Operation isOwnedBy failed.
Category:: Configuration
Cause:: Could not perform operation isOwnedBy.
Action:: Correct the owner's name.

JPS-02559: Operation isManagedBy failed.
Category:: Configuration
Cause:: Could not perform operation isManagedBy.
Action:: Correct the name.

JPS-02560: Cannot update role.
Category:: Configuration
Cause:: Could not update role.
Action:: Verify that the role name is correct and, if necessary, contact the domain administrator.

JPS-02561: The realm entry {0} is missing in the identity store XML file.
Category:: Configuration
Cause:: Could not find realm entry {0} in XML-based identity store.
Action:: Ensure that the realm name is present in the XML-based identity store.

JPS-02562: Identity store entry is missing in the identity store XML file.
Category:: Configuration
Cause:: Could not find identity store entry in XML-based identity store.
Action:: Ensure that entry is present in the XML-based identity store.

JPS-02563: Length of the name attribute should be more than {0}.
Category:: Configuration
Cause:: Found attribute name with less than {0} characters.
Action:: Ensure that the length of the attribute name is at least the minimum length.

JPS-02564: Length of the name attribute should be less than {0}.
Category:: Configuration
Cause:: Found attribute name with more than {0} characters.
Action:: Ensure that the length of the attribute name is at most the maximum length.

JPS-02565: Name attribute contains invalid characters.
Category:: Configuration
Cause:: Found invalid characters in attribute name.
Action:: Ensure that attribute names have characters in the following sets only: [a-z], [A-Z], [0-9], ['.', '-', '_'].

JPS-02566: The identity store config property {0} with value {1} is invalid.
Category:: Configuration
Cause:: Found invalid identity store configuration property.
Action:: Correct the configuration of the identity store property.

JPS-02567: The credential with map {0} and key {1} does not exist.
Category:: Configuration
Cause:: Could not find credential with map and key names provided.
Action:: Ensure that a credential with given map and key is present in the credential store.

JPS-02568: The password credential with map {0} and key {1} is invalid.
Category:: Configuration
Cause:: Found invalid user name or password.
Action:: Ensure that the user name and password in the credential store are correct.

JPS-02569: Cannot find the XML file {0}.
Category:: Configuration
Cause:: Could not find XML file for XML-based identity store {0}.
Action:: Check the path of the XML file specified for the identity store.

JPS-02570: XML file is unspecified.
Category:: Configuration
Cause:: Could not determine XML file.
Action:: Specify the XML file for the XML-based repository.

JPS-02571: The algorithm {0} to encode passwords is not supported.
Category:: Configuration
Cause:: Found invalid password encoding algorithm.
Action:: Specify a valid algorithm for password encoding.

JPS-02572: Caller does not have IdentityAssertion permission to execute this operation. Reason {0}.
Category:: Requests/Responses
Cause:: Caller did not have IdentityAssertion permission.
Action:: Make sure the caller has IdentityAssertion permission to execute this operation.

JPS-02573: Cannot grant a role to itself.
Category:: Configuration
Cause:: Attempted to grant a role to itself.
Action:: Verify that no role is being granted to itself.

JPS-02574: Cannot delete default realm.
Category:: Requests/Responses
Cause:: Could not delete default realm.
Action:: The default realm cannot be deleted: assign another realm as the default realm before deleting this one.

JPS-02575: A user with the specified name does not exist.
Category:: Requests/Responses
Cause:: Could not find user with the specified name.
Action:: Check the user name.

JPS-02576: A role with the specified name already exists.
Category:: Requests/Responses
Cause:: Role with the specified name already existed.
Action:: Use a different role name.

JPS-02577: A role with the specified name does not exist.
Category:: Requests/Responses
Cause:: Could not find role with the specified name.
Action:: Check the role name.

JPS-02578: The principal type {0} is invalid for the identity store type {1}.
Category:: Requests/Responses
Cause:: Found unsupported principal type {0} for identity store type {1}.
Action:: Verify that principals have supported types.

JPS-02579: Identity store type for application {0} is null or empty.
Category:: Requests/Responses
Cause:: Found null identity store type configured in identity store.
Action:: Pass one of the following identity store types: XML, OID, ACTIVE_DIRECTORY, IPLANET, EDIRECTORY, OPEN_LDAP, COREID, OVD, OUD, or CUSTOM.

JPS-02580: Cannot grant role {0} to {1} because it would lead to a cyclic dependency.
Category:: Requests/Responses
Cause:: Could not grant role {0} to {1}, because it would lead to a cyclic dependency.
Action:: Revoke the grant which would create the cyclic dependency, and try again.

JPS-02582: LDAP user or group search base is invalid.
Category:: Requests/Responses
Cause:: Found invalid LDAP user or group search base.
Action:: Check that the user and group search base properties are valid.

JPS-02583: JPS principal "{0}" with identity store type "{1}" cannot be created.
Category:: Security
Cause:: JPS principal "{0}" with identity store type "{1}" cannot be created.
Action:: Ensure the principal value is valid.

JPS-02584: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.
Category:: Security
Cause:: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.
Action:: Ensure the user value is valid.

JPS-02585: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.
Category:: Security
Cause:: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.
Action:: Ensure the enterprise role value is valid.

JPS-02586: JPS application role name "{0}", principal type "{1}" cannot be created.
Category:: Security
Cause:: JPS application role name "{0}", principal type "{1}" cannot be created.
Action:: Ensure the application role value is valid.

JPS-02587: Principal class "{0}", name "{1}" cannot be created.
Category:: Security
Cause:: Principal class "{0}", name "{1}" cannot be created.
Action:: Ensure the principal value is valid.

JPS-02588: Enterprise user principal "{0}" cannot be created. Reason: {1}.
Category:: Security
Cause:: Enterprise user principal "{0}" cannot be created.
Action:: Ensure the user principal value is valid.

JPS-02589: Enterprise role principal "{0}" cannot be created. Reason: {1}.
Category:: Security
Cause:: Enterprise role principal "{0}" cannot be created.
Action:: Ensure the role principal value is valid.

JPS-02590: Token type {0} cannot be supported. Supported types are: {1}.
Category:: Configuration
Cause:: Token type {0} cannot be supported. Supported types are: {1}.
Action:: Use the Supported types.

JPS-02591: Guid {0} is assigned to principal {1}.
Category:: Security
Cause:: Guid {0} is assigned to principal {1}.
Action:: Check log for more details.

JPS-02592: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}
Category:: Security
Cause:: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}
Action:: Check libOvd log for more details.

JPS-02593: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}
Category:: Security
Cause:: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}
Action:: Check IGF API or libOvd log for more details.

JPS-02594: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured
Category:: Security
Cause:: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured
Action:: Check jps-config.xml to make sure the IGF service has either the IDStore instance defined, or use the WlsLdapIdStoreConfigProvider to get LDAP config from WLS Authentication providers.

JPS-02595: The IGFService specified ldap "{0}" is not defined in the JPS service instances
Category:: Security
Cause:: The IGFService specified ldap "{0}" is not defined in the JPS service instances
Action:: Check jps-config.xml to make sure the specified ldap is defined as a JPS service instance.

JPS-02596: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"
Category:: Security
Cause:: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"
Action:: Check jps-config.xml to make sure the provider type class for ldap instance is "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider".

JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.
Category:: Security
Cause:: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which is a custom type and not supported by libOvd
Action:: The "idstore.type" property must be specified in jps-config.xml file as specific type such as OID, OVD etc. Alternatively, select a specific WLS LDAP Authentication provider that matches your LDAP server.

JPS-02598: Pushed ldap name and types info to libOvd. Ldaps : {0}.
Category:: Security
Cause:: libOvd is enabled so Ldap configuration info is passed to libOvd
Action:: No action required

JPS-02599: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory
Category:: Security
Cause:: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory
Action:: Use supported Identity Store provider for the IdentiyStoreService

JPS-02600: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line
Category:: Security
Cause:: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line
Action:: Supply the system flag of "-Dcommon.components.home" and point it to the oracle_common folder

JPS-02601: Failed to get Ovd virtualization service for service instance "{0}" in JPS context "{1}", cause: {2}
Category:: Security
Cause:: Failed to get Ovd virtualization service for service instance "{0}" in JPS context "{1}", cause: {2}
Action:: Check Ovd log for more details.

JPS-03000: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the application policy context "{3}". Cause {4}
Category:: Security
Cause:: Could not load a permission class.
Action:: Ensure that the class name is correct and available in the current class loader.

JPS-03001: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the system policy context. Cause {3}
Category:: Security
Cause:: Could not load a class.
Action:: Ensure that the class name is correct and is available in the current class loader.

JPS-03004: Cannot log check authorization event to the audit service.
Category:: Security
Cause:: Could not log check authorization events to the audit service.
Action:: Ensure that auditing is configured correctly in your environment and application.

JPS-03005: LDAP policy store contains invalid configuration parameters.
Category:: Security
Cause:: Found invalid parameters in LDAP policy store configuration.
Action:: Check the configuration of the LDAP policy store.

JPS-03006: The name "{0}" of application role "{1}" is missing or invalid.
Category:: Security
Cause:: Found missing or invalid name in application role.
Action:: The internal identifier generated by the policy store seems malformed, due to an internal policy store error; contact Oracle Support Services.

JPS-03007: Authorization check permission succeeded.
Category:: Security
Cause:
Action:

JPS-03008: Authorization check permission failed.
Category:: Security
Cause:: Current Subject or source code did not have required permissions
Action:: Provide the required permissions.

JPS-03009: Executing privileged action in {0} mode as subject {1}.
Category:: Security
Cause:
Action:

JPS-03010: Policy store cleanup thread started.
Category:: Security
Cause:
Action:

JPS-03011: Policy store cleanup thread stopped.
Category:: Security
Cause:
Action:

JPS-03012: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}
Category:: Security
Cause:: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}
Action:: Refer to the base exception in logs to resolve the issue.

JPS-03013: Unsupported API method call.
Category:: Security
Cause:: Unsupported API method call.
Action:: Check the policy provider.

JPS-03014: Failed to distribute policy by timer.
Category:: Configuration
Cause:: Failed to distribute policy by timer.
Action:: Check the log for more details or contact the administator.

JPS-03015: Resource-Actions "{0}" will be skipped in bulk authorization evaluation for Application: "{1}".
Category:: Configuration
Cause:: Application name not set in the resource-actions.
Action:: Set the Application name in the resource-actions

JPS-03016: Resource-Actions "{0}" will be skipped in bulk authorization. Reason: "{1}"
Category:: Configuration
Cause:: Failed to convert the Resource-Actions into a Permission instance.
Action:: Check the logs for more information to resolve the error.

JPS-03017: Failed to compute Application roles for Subject "{0}". Reason "{1}"
Category:: Configuration
Cause:: Unable to get the ApplicationRoles granted to a principal.
Action:: Check the logs for more information to resolve the error.

JPS-03018: The authorization result is ignoring policies from application {0} as the application is not available
Category:: Configuration
Cause:: The application is not available at runtime, or the application is not defined in the policystore.
Action:: Check if the application is provisioned in the policystore.

JPS-03019: Policy evaluation in the application {0} failed. Reason: {1}
Category:: Configuration
Cause:: Error occurred while evaluating policies.
Action:: Refer to the logs to rectify the problem.

JPS-03020: Policy evaluation in the system policy failed. Reason: {0}
Category:: Configuration
Cause:: Error occurred while evaluating system policies.
Action:: Refer to the logs to rectify the problem.

JPS-03021: Admin Policy evaluation in the application {0} failed. Reason: {1}
Category:: Configuration
Cause:: Error occurred while evaluating administrative policies.
Action:: Refer to the logs to rectify the problem.

JPS-03022: Failed to initialize PolicyStore for Discovery mode. Reason: {0}
Category:: Configuration
Cause:: Failed to initialize PolicyStore for Discovery mode. Reason: {0}
Action:: Refer to the logs to rectify the problem.

JPS-03023: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}
Category:: Configuration
Cause:: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}
Action:: Make sure directory for writing discovered policy exist, is directory and can write.

JPS-03024: Failed to write policy information during discovery. Reason: {0}
Category:: Configuration
Cause:: Failed to dump policy objects in discovery mode. Reason: {0}
Action:: Refer to the logs to rectify the problem.

JPS-03025: Input permission is null when getPermissions is called for application name= {0}
Category:: Configuration
Cause:: Input permission is null when getPermissions is called. application name= {0}
Action:: Refer to the logs to rectify the problem.

JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: {0}
Category:: Configuration
Cause:: PolicyStore service instance and PDPService service instance not found in the default JpsContext in an uncontrolled mode.
Action:: Configure a PDPService service instance in the default JpsContext, or if running in an uncontroled mode, a PolicyStore Service.

JPS-03027: PDPService service instance failed during initialization due to lack of grant. If you are seeing this error after a new installation, make sure you have updated weblogic.policy as installation step suggested
Category:: Configuration
Cause:: PDPService service instance failed during initialization because of lack of grant.
Action:: check codebase grant like weblogic.policy to see if proper grant set for all codebase of PDP service.

JPS-03028: Unable to convert to a permission entry to resource-actions entry. Reason: {0}
Category:: Configuration
Cause:: Unable to convert to a permission entry to resource-actions entry.
Action:: Check the logs for more information to resolve the error.

JPS-03029: Unable to Notify to external Application:{0} Refresh Event. Reason {1}
Category:: Configuration
Cause:: Unable to Notify to external Appliacation Refresh Event.
Action:: Check the logs for more information to resolve the error.

JPS-03030: Catch exception in PDP registration, will retry later.
Category:: Configuration
Cause:: Catch exception in PDP registration, retry later.
Action:: check the exception details and retry

JPS-03031: Catch InterruptedException in PDP registration. Registration failed.
Category:: Configuration
Cause:: Catch InterruptedException in PDP registration. Registration failed
Action:: check the exception details and retry

JPS-03032: Can not access PD server web service during PDP registration, will retry later.
Category:: Configuration
Cause:: PD Server web service not available, retry later.
Action:: wait retry to access to PD Server web service

JPS-03033: Can not access PD client web service during PDP registration, will retry later.
Category:: Configuration
Cause:: PD client web service not available, retry later.
Action:: wait retry to access to PD client web service

JPS-03034: Policystore is not ready on admin server during PDP registration, will retry later.
Category:: Configuration
Cause:: Policystore isn't available from admin server, retry later.
Action:: wait retry accessing policystore

JPS-03035: PDP registration succeeded.
Category:: Configuration
Cause:
Action:

JPS-03036: No PDP Service is found in JPS Context {1}
Category:: Configuration
Cause:: PDPService service instance is not found in JPS Context.
Action:: Configure a PDPService service instance in JPS Context

JPS-03037: Exception happened during PDP initialization.
Category:: Configuration
Cause:: Exception happened during PDP Initialization
Action:: check the exception details and retry

JPS-03038: Unable to find PolicyStore or Schema Version. Check farm name and root name of policystore service instance in OPSS configuration file.
Category:: Configuration
Cause:: Unable to find PolicyStore or Schema Version.
Action:: Check farm name and root name of policystore service instance in OPSS configuration file

JPS-03039: Exception {0} happened during Policystore agent processing message {1}, the message will be ignored.
Category:: Configuration
Cause:: Exception happened during PolicyStore agent processing
Action:: check the exception details and retry

JPS-03040: Subject resolver cache initiation failed.
Category:: Security
Cause:: Subject resolver cache initiation failed.
Action:: Make sure all jars are included in the classpath.

JPS-03041: Subject resolver cache property, key: {0}, value: {1} is not valid.
Category:: Security
Cause:: Subject resolver cache property, key: {0}, value: {1} is not valid.
Action:: Check pdp service configuration.

JPS-03042: PDP Service property, key: {0}, value: {1} is not valid, use default value: {2}.
Category:: Security
Cause:: PDP Service property, key: {0}, value: {1} is not valid, use default value: {2}.
Action:: Check pdp service configuration.

JPS-03043: Configuration property, key: {0}, value: {1} is not valid, use default value: {2}.
Category:: Security
Cause:: Configuration property, key: {0}, value: {1} is not valid, use default value: {2}.
Action:: Check pdp service configuration.

JPS-03044: Mandatory property {0} of PDP service is missing.
Category:: Configuration
Cause:: Mandatory property of PDP service is missing.
Action:: provide the required property

JPS-03045: Can not clean application : {0} from runtime cache. Reason:mode : {1} it is not non-controlled mode or not non-bound application in mixed mode.
Category:: Security
Cause:: Can not clean application : {0} from runtime cache. Reason: mode : {1} it is not non-controlled mode or not non-bound application in mixed mode.
Action:: Check pdp service configuration.

JPS-03046: Application {0} is not found when being preloaded.
Category:: Programmatic
Cause:: Application {0} is not found when being preloaded.
Action:: Please check policy store, application might have been deleted.

JPS-03047: Upsupported preload key type {0} with condition oracle.security.jps.policystore.policy.lazy.load.enable being {1} .
Category:: Programmatic
Cause:: Upsupported preload key type {0} with condition 'oracle.security.jps.policystore.policy.lazy.load.enable' being {1}
Action:: Please check the preload key and the configuration parameters for PDP service.

JPS-03048: Unable to remove application {0} from runtime cache, due to {1}
Category:: Security
Cause:: Unable to remove application {0} from runtime cache, due to {1}
Action:: Check full stacktrace

JPS-03049: Cannot {0} {1} {2} {3} because the policy lockdown has been enabled.
Category:: Security
Cause:: Cannot {0} {1} {2} {3} because the policy lockdown has been enabled
Action:: The exception is because of violation of policy customization rule. Seeded policy definition can not be modified.

JPS-03150: Error during setting the field of a provider MBean. {0}
Category:: Security
Cause:: Error during setting the field of a provider MBean. {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03151: getSecurityService returning null for requested service type of {0} for realm {1}
Category:: Security
Cause:: getSecurityService returning null for requested service type of {0} for realm {1}.
Action:: Refer to the log files for details and correct the error.

JPS-03152: Query Atz Cache specified but no response collector supplied
Category:: Security
Cause:: Query Atz Cache specified but no response collector supplied.
Action:: Supply the response collector in the request.

JPS-03153: Error parsing atz. cache flush time.
Category:: Security
Cause:: Error parsing atz. cache flush time.
Action:: Verify that the value is an integer.

JPS-03154: Authorization cache has been flushed. Time={0}
Category:: Security
Cause:: Authorization cache has been flushed. Time={0}.
Action:: No actions are required.

JPS-03155: Cannot locate class: {0}
Category:: Security
Cause:: Cannot locate class: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03156: The exception has been thrown by ARME. The authorization result is set to deny.
Category:: Security
Cause:: The exception has been thrown by ARME. The authorization result is set to deny.
Action:: Refer to the log files for details and correct the error.

JPS-03157: Error during initialization of the security framework.
Category:: Security
Cause:: Error during initialization of the security framework.
Action:: Refer to the log files for details and correct the error.

JPS-03158: Failed to parse resource cache size: {0}
Category:: Security
Cause:: Failed to parse resource cache size: {0}
Action:: Refer to the log files for details and correct the error.

JPS-03159: Invalid built in type in Value object: {0}
Category:: Security
Cause:: Invalid built in type in Value object: {0}
Action:: Refer to the log files for details and correct the error.

JPS-03160: Attempt to {0} a {1} value for type: {2}
Category:: Security
Cause:: Attempt to {0} a {1} value for type: {2}
Action:: Refer to the log files for details and correct the error.

JPS-03161: identifier not found in symbol table: {0}
Category:: Security
Cause:: Identifier not found in symbol table: {0}
Action:: Refer to the log files for details and correct the error.

JPS-03162: ERROR: PARSE: reason:==> {0}
Category:: Security
Cause:: ERROR: PARSE: reason:==>
Action:: Refer to the log files for details and correct the error.

JPS-03163: Invalid Declaration type received by setDeclType
Category:: Security
Cause:: Invalid Declaration type received by setDeclType.
Action:: Refer to the log files for details and correct the error.

JPS-03164: Got exception
Category:: Security
Cause:: Got exception.
Action:: Refer to the log files for details and correct the error.

JPS-03165: Invalid declaration type found: {0}
Category:: Security
Cause:: Invalid declaration type found: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03166: Unexpected PolicyParserTokenType: {0}
Category:: Security
Cause:: Unexpected PolicyParserTokenType: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03167: Invalid attribute type: {0}
Category:: Security
Cause:: Invalid attribute type: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03168: Invalid attribute value type: {0}
Category:: Security
Cause:: Invalid attribute value type: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03169: Invalid configuration
Category:: Security
Cause:: Invalid configuration.
Action:: Refer to the log files for details and correct the error.

JPS-03170: Try to get {0}, but JPS Policy tree is not available.
Category:: Security
Cause:: Try to get {0}, but JPS Policy tree is not available.
Action:: Refer to the log files for details and correct the error.

JPS-03171: Unable to update policy: unable to get {0} instance
Category:: Security
Cause:: Unable to update policy: unable to get {0} instance.
Action:: Refer to the log files for details and correct the error.

JPS-03172: Unspecified error in {0}
Category:: Security
Cause:: Unspecified error in {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03173: Commit error: {0}
Category:: Security
Cause:: Commit error: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03174: ARME can not find state.chk file.
Category:: Security
Cause:: ARME can not find state.chk file.
Action:: Refer to the log files for details and correct the error.

JPS-03175: Invalid mac found in write check, rewrite policies and mac
Category:: Security
Cause:: !!!>>>Invalid mac found in write check, rewrite policies and mac
Action:: Refer to the log files for details and correct the error.

JPS-03176: Failed to write check file.
Category:: Security
Cause:: Failed to write check file.
Action:: Refer to the log files for details and correct the error.

JPS-03177: Failed to close check file writer
Category:: Security
Cause:: Failed to close check file writer.
Action:: Refer to the log files for details and correct the error.

JPS-03178: Failed to write mac, which will cause Mac verification error in the future.
Category:: Security
Cause:: Failed to write mac, which will cause Mac verification error in the future.
Action:: Refer to the log files for details and correct the error.

JPS-03179: Prepare request in invalid state for update
Category:: Security
Cause:: Prepare request in invalid state for update.
Action:: Refer to the log files for details and correct the error.

JPS-03180: Error happens: {0}
Category:: Security
Cause:: Error happened: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03181: ArmeRuntimeException happens
Category:: Security
Cause:: ArmeRuntimeException happened.
Action:: Refer to the log files for details and correct the error.

JPS-03182: Cannot get AppGuardInstance, so cannot get information to request policy update from PD.
Category:: Security
Cause:: Cannot get AppGuardInstanceii, so cannot get information to request policy update from PD.
Action:: Refer to the log files for details and correct the error.

JPS-03183: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.
Category:: Security
Cause:: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.
Action:: Refer to the log files for details and correct the error.

JPS-03184: No host specified in the ARME configuration, attempting to determine host address...
Category:: Security
Cause:: No host specified in the ARME configuration, attempting to determine host address...
Action:: No actions are required.

JPS-03185: No {0} found in the ARME configuration. Cannot contact PD
Category:: Security
Cause:: No {0} found in the ARME configuration. Cannot contact PD.
Action:: Verify configuration.

JPS-03186: InstanceName not found in ARME configuration, using LocalName and host
Category:: Security
Cause:: InstanceName not found in arme configuration, using LocalName and host.
Action:: Refer to the log files for details and correct the error.

JPS-03187: No {0} from ARME, unable to contact PD
Category:: Security
Cause:: No {0} from ARME, unable to contact PD.
Action:: Refer to the log files for details and correct the error.

JPS-03188: Exception initializing SSL. Unable to contact PD
Category:: Security
Cause:: Exception initializing SSL. Unable to contact PD.
Action:: Refer to the log files for details and correct the error.

JPS-03189: Error getting attribute: {0}
Category:: Security
Cause:: Error getting attribute: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03190: Failed to close File reader while reading salt.
Category:: Security
Cause:: Failed to close File reader while reading salt.
Action:: Refer to the log files for details and correct the error.

JPS-03191: Could not obtain digest algorithm {0}
Category:: Security
Cause:: Could not obtain digest algorithm '{0}'.
Action:: Refer to the log files for details and correct the error.

JPS-03192: Index of ListValue is wrong
Category:: Security
Cause:: Index of ListValue is wrong.
Action:: Refer to the log files for details and correct the error.

JPS-03193: PBEService is not initialized
Category:: Security
Cause:: PBEService is not initialized.
Action:: Refer to the log files for details and correct the error.

JPS-03194: Port is not number type
Category:: Security
Cause:: Port is not number type.
Action:: Verify that the port value is an integer.

JPS-03195: Can not get host IP information, using default IP address: {0}
Category:: Security
Cause:: Cannot get host IP information, use default IP address: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03196: Can not get host IP information.
Category:: Security
Cause:: Cannot get host IP information.
Action:: Refer to the log files for details and correct the error.

JPS-03197: ARME shutdown failed: {0}
Category:: Security
Cause:: ARME shutdown failed: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03198: Can not get enablePerfStats from ARME config file
Category:: Security
Cause:: Cannot get enablePerfStats from arme config file.
Action:: Refer to the log files for details and correct the error.

JPS-03199: Configuration file is [{0}]
Category:: Security
Cause:: Configuration file is [{0}].
Action:: No actions are required.

JPS-03200: getDebugStore: IOException caught.
Category:: Security
Cause:: getDebugStore: IOException happens.
Action:: Refer to the log files for details and correct the error.

JPS-03201: Privilege name error: {0}
Category:: Security
Cause:: privilege name error: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03202: Resource name or application name invalid.
Category:: Security
Cause:: Resource name or application name invalid.
Action:: Refer to the log files for details and correct the error.

JPS-03203: Resource name is wrong according to ALES naming logic
Category:: Security
Cause:: Pesource name is wrong according to ALES naming logic.
Action:: Refer to the log files for details and correct the error.

JPS-03204: Invalid object name
Category:: Security
Cause:: Invalid object name.
Action:: Refer to the log files for details and correct the error.

JPS-03205: Logical name {0} is invalid
Category:: Security
Cause:: Logical name {0} is invalid.
Action:: Refer to the log files for details and correct the error.

JPS-03206: Logical name {0} is undefined
Category:: Security
Cause:: Logical name {0} is undefined.
Action:: Refer to the log files for details and correct the error.

JPS-03207: IOException occurred when storing logical names {0}
Category:: Security
Cause:: ioexception occured when storing logical names {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03208: Logical names record is not correct
Category:: Security
Cause:: Logical names record is not correct.
Action:: Refer to the log files for details and correct the error.

JPS-03209: objectTree is initialized properly
Category:: Security
Cause:: ObjectTree is initialized properly.
Action:: No actions are required.

JPS-03210: Can not close data files: {0}
Category:: Security
Cause:: Cannot close data files: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03211: Blocking queue is broken
Category:: Security
Cause:: Blocking queue is broken.
Action:: Refer to the log files for details and correct the error.

JPS-03212: Session data could not be loaded. Session abandoned
Category:: Security
Cause:: Session data could not be loaded. Session abandoned.
Action:: Refer to the log files for details and correct the error.

JPS-03213: args value is null or wrong type
Category:: Security
Cause:: Args value is null or wrong type.
Action:: Refer to the log files for details and correct the error.

JPS-03214: Could not add attribute(s) to cache
Category:: Security
Cause:: Could not add attribute(s) to cache.
Action:: Refer to the log files for details and correct the error.

JPS-03215: Caught BadParameterException during get attribute: {0}
Category:: Security
Cause:: Caught BadParameterException while getting attribute: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03216: Installing custom retriever: {0}
Category:: Security
Cause:: Installing custom retriever: {0}.
Action:: No actions are required.

JPS-03217: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.
Category:: Security
Cause:: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.
Action:: Refer to the log files for details and correct the error.

JPS-03218: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}
Category:: Security
Cause:: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}.
Action:: Refer to the log files for details and correct the error.

JPS-03219: AttributeValue type error, not single and list, return null
Category:: Security
Cause:: AttributeValue type error, not single and list, return null.
Action:: Refer to the log files for details and correct the error.

JPS-03220: Exception from the LDAP/DB server, code: {0}, trying alternate connection
Category:: Security
Cause:: Exception from the LDAP/DB server, code: {0}, trying alternate connection.
Action:: Refer to the log files for details and correct the error.

JPS-03221: Alternate LDAP/DB connection failed, code: {0}
Category:: Security
Cause:: Alternate LDAP/DB connection failed, code: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03222: Null extendedContext is passed to attribute retriever, cannot look for value.
Category:: Security
Cause:: Null extendedContext is passed to attribute retriever, cannot look for value.
Action:: Refer to the log files for details and correct the error.

JPS-03223: Caught exception while retrieving attribute: {0}
Category:: Security
Cause:: Caught exception while retrieving attribute: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03224: Parameter value is null or wrong type.
Category:: Security
Cause:: Parameter value is null or wrong type.
Action:: Refer to the log files for details and correct the error.

JPS-03225: Calling RBACEvals:{0}
Category:: Security
Cause:: Calling RBACEvals:{0}.
Action:: No actions are required.

JPS-03226: Empty Application name or Obligation name is passed to report_obligation function.
Category:: Security
Cause:: Empty Application name or Obligation name is passed to report_obligation function.
Action:: Refer to the log files for details and correct the error.

JPS-03227: Unexpected error: invalid parameter instances.
Category:: Security
Cause:: Unexpected error: invalid parameter instances.
Action:: Refer to the log files for details and correct the error.

JPS-03228: The value of args is null
Category:: Security
Cause:: args is null.
Action:: Refer to the log files for details and correct the error.

JPS-03229: Error during initialization of RetrieverConfiguration.
Category:: Security
Cause:: Error during initialization of RetrieverConfiguration.
Action:: Refer to the log files for details and correct the error.

JPS-03230: args value type is null or wrong type value
Category:: Security
Cause:: args value type is null or wrong type value.
Action:: Refer to the log files for details and correct the error.

JPS-03231: {0} supplied to subject_in_group is not a qualified group, will qualify
Category:: Security
Cause:: {0} supplied to subject_in_group is not a qualified group, will qualify.
Action:: Refer to the log files for details and correct the error.

JPS-03232: Qualified group is {0}
Category:: Security
Cause:: qualified group is {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03233: Type of args should be String[]
Category:: Security
Cause:: args should be String[].
Action:: Refer to the log files for details and correct the error.

JPS-03234: No value is passed to {0}
Category:: Security
Cause:: No value is passed to {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03235: No attribute name is passed to sys_obj_exists
Category:: Security
Cause:: No attribute name is passed to sys_obj_exists.
Action:: Refer to the log files for details and correct the error.

JPS-03236: Failed to get attribute {0} for eval function {0}
Category:: Security
Cause:: Failed to get attribute {0} for eval function {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03237: Value passed to {0} is not valid, {1}
Category:: Security
Cause:: Value passed to {0} is not valid, {1}.
Action:: Refer to the log files for details and correct the error.

JPS-03238: {0} is not a valid value for {1}
Category:: Security
Cause:: {0} is not a valid value for {1}.
Action:: Refer to the log files for details and correct the error.

JPS-03239: valid_timeval called for unexpected eval function {0}
Category:: Security
Cause:: valid_timeval called for unexpected eval function {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03240: Unknown eval function {0} used in valid_until_timeofday
Category:: Security
Cause:: Unknown eval function {0} used in valid_until_timeofday.
Action:: Refer to the log files for details and correct the error.

JPS-03241: Disabling extended performance data...
Category:: Security
Cause:: Disabling extended performance data...
Action:: No actions are required.

JPS-03242: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.
Category:: Security
Cause:: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.
Action:: No actions are required.

JPS-03243: Unexpected MBean attribute get method: {0}
Category:: Security
Cause:: Unexpected mbean attribute get method: {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03244: {0} specified but no response collector supplied
Category:: Security
Cause:: {0} specified but no response collector supplied.
Action:: Refer to the log files for details and correct the error.

JPS-03245: Received {0} in isProtectedResource
Category:: Security
Cause:: Received {0} in isProtectedResource.
Action:: Refer to the log files for details and correct the error.

JPS-03246: Role object passed into wles atz provider is null, ignoring
Category:: Security
Cause:: Null role object passed into wles atz provider, ignoring.
Action:: Refer to the log files for details and correct the error.

JPS-03247: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.
Category:: Security
Cause:: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03248: Error {0}
Category:: Security
Cause:: Error {0}.
Action:: Refer to the log files for details and correct the error.

JPS-03249: ASI shutdown failed
Category:: Security
Cause:: ASI shutdown failed.
Action:: Refer to the log files for details and correct the error.

JPS-03250: getInstance: Warning: The parent classloaders are different.
Category:: Security
Cause:: getInstance: Warning: The parent classloaders are different.
Action:: Refer to the log files for details and correct the error.

JPS-03251: addClassJars: {0}
Category:: Security
Cause:: addClassJars: {0}.
Action:: Refer to the log files for details.

JPS-03252: Missing JAR file: {0}
Category:: Security
Cause:: Missing JAR file: {0}.
Action:: Refer to the log files for details.

JPS-03253: Error initializing URLs in classloader. Vector: {0}
Category:: Security
Cause:: Error initializing URLs in classloader. Vector: {0}.
Action:: Refer to the log files for details.

JPS-03254: lazy getRoles failed with error {0}
Category:: Security
Cause:: lazy getRoles failed with error {0}.
Action:: Refer to the log files for details.

JPS-03255: null value returned in roles list, ignoring
Category:: Security
Cause:: null value returned in roles list, ignoring.
Action:: Refer to the log files for details.

JPS-03256: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.
Category:: Security
Cause:: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.
Action:: Refer to the log files for details.

JPS-03257: Passed an non URLResource, in getAttributeValue
Category:: Security
Cause:: Passed a non URLResource, in getAttributeValue.
Action:: Refer to the log files for details.

JPS-03258: Initializing UserUtils; {0}
Category:: Security
Cause:: Initializing UserUtils; {0}.
Action:: No actions are required.

JPS-03259: Invalid built in type received
Category:: Security
Cause:: Invalid built in type received.
Action:: Refer to the log files for details.

JPS-03260: Attempt to {0} when CRED is wrong type
Category:: Security
Cause:: Attempt to {0} when CRED is wrong type.
Action:: Refer to the log files for details.

JPS-03261: No locally defined evaluator found for function {0}.
Category:: Security
Cause:: No locally defined evaluator found for function {0}.
Action:: Refer to the log files for details.

JPS-03262: DiscoveryModeRoleMap does not support this operation
Category:: Configuration
Cause:: DiscoveryModeRoleMap does not support this operation
Action:: Do not call method not supported

JPS-03263: DiscoveryModeRoleMap never contains data
Category:: Configuration
Cause:: DiscoveryModeRoleMap never contains data
Action:: Do not try to get data from DiscoveryModeRoleMap.

JPS-03264: The attribute dependency leads to a dead loop, {1} depends on {0} already.
Category:: Security
Cause:: The attribute dependency leads to a dead loop, {1} depends on {0} already.
Action:: Please check the configuration.

JPS-03265: Data source based DB query failed, try again.
Category:: Security
Cause:: Data source based DB query failed, try again.
Action:: Refer to the log files for details.

JPS-03266: Failed to retrieve connection for url {0} due to following exception {1}.
Category:: Security
Cause:: Failed to retrieve connection for {0}.
Action:: Refer to the log files for details.

JPS-03267: Ignoring credential variable exception in computeObligation for {0}.
Category:: Security
Cause:
Action:

JPS-03268: In Policy {0}, an invalid Resource Name Expression {1} was encountered. The Policy will not participate in the runtime authorization evaluation. Reason: {2}
Category:: Security
Cause:: Resource name expression in policy is invalid
Action:: Correct the reource name expression.

JPS-03269: Size of bag provided for type-one-and-only function is not one.
Category:: Programmatic
Cause:: Size of bag provided to type one and only function is not one.
Action:: Provide correct function.

JPS-03270: Invalid value of year {0} or month {1} in yearMonthDuration .Must be between max and min values for integer.
Category:: Programmatic
Cause:: Value provided for year or month is outside the supported integer range on this JVM.
Action:: Provide a valid integer value.

JPS-03271: Function name passed to evaluator is null.
Category:: Programmatic
Cause:: Function name is null.
Action:: Provide a valid function name.

JPS-03272: No arguments passed to function {0}.
Category:: Programmatic
Cause:: No arguments passed to function.
Action:: Provide a valid function arguments.

JPS-03273: Application {0} attribute {1} is not available.
Category:: Programmatic
Cause:: Application {0} attribute {1} is not available.
Action:: None.

JPS-04000: Cannot get the default policy store.
Category:: Security
Cause:: Could not find to the default policy store.
Action:: Refer to the log files for details and correct the error.

JPS-04001: Cannot read the default policy store.
Category:: Security
Cause:: Could not read the default policy store.
Action:: Refer to the log files for details and correct the error.

JPS-04002: Cannot get application policy for application "{0}".
Category:: Security
Cause:: Encountered a policy store internal error.
Action:: Refer to the log files for details and correct the error.

JPS-04003: Duplicate principal present "{0}"in a grant request.
Category:: Security
Cause:: Found that list of principals in the grantee for the grant contains duplicate
Action:: Correct the list of principals in the grantee.

JPS-04004: Duplicate permission present "{0}" in a grant request.
Category:: Security
Cause:: Found that list of permissions in the grant contains duplicate.
Action:: Correct the list of permissions in the grant.

JPS-04005: More than one result found for given Application Name:{0}, Query:{1}, Actual results:{2}.
Category:: Security
Cause:: More than one results found for application name.
Action:: Refer to the log files for details and correct the error.

JPS-04006: No results found for given Application Name:{0}, DN: {1}, Query: {2}.
Category:: Security
Cause:: No results found for application name.
Action:: Refer to the log files for details and correct the error.

JPS-04021: Application Policy "{0}" already exists.
Category:: Security
Cause:: Encountered two application policy contexts with identical names.
Action:: Modify an application policy context to have a distinct name.

JPS-04022: Cannot create application policy context "{0}".
Category:: Security
Cause:: Failed to complete persist operation while creating an application policy.
Action:: Refer to the base exception in log files and correct the error.

JPS-04026: Application policy "{0}" does not exist.
Category:: Security
Cause:: Could not find a policy context with the provided name.
Action:: Verify that a context with the provided name exists.

JPS-04027: Role with name "{0}" does not exist.
Category:: Configuration
Cause:: Could not find a role with name {0}.
Action:: Verify that a role with the provided name exists.

JPS-04028: Application with name "{0}" does not exist.
Category:: Configuration
Cause:: Could not find application with name {0}.
Action:: Verify that an application with the provided name exists.

JPS-04029: Cannot create principal with class name "{0}".
Category:: Configuration
Cause:: Could not create principal with class name {0}.
Action:: Verify that the provided class name is valid.

JPS-04030: Cannot delete application policy context "{0}".
Category:: Security
Cause:: Failed to complete persist operation while deleting an application policy.
Action:: Refer to the base exception in log files and correct the error.

JPS-04031: Parameter "{0}" is null or empty.
Category:: Security
Cause:: Supplied parameter {0} was null or empty.
Action:: Verify that the supplied parameter is non-null. If it is of type String, ensure that its length is positive.

JPS-04032: Parameter "{0}" supplied is not the instance of "{1}".
Category:: Security
Cause:: Parameter {0} supplied is not the instance of {1}.
Action:: Ensure parameter is of correct datatype.

JPS-04033: Parameter "{0}" supplied is not of the type "{1}" (as expected).
Category:: Security
Cause:: Parameter {0} supplied is not of the type {1} (as expected).
Action:: Ensure parameter is of correct datatype.

JPS-04034: Failed to modify properties for Application "{0}".
Category:: Security
Cause:: Cannot modify application policy.
Action:: Check the logs for errors.

JPS-04035: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.
Category:: Security
Cause:: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.
Action:: Ensure attribute name is of correct datatype.

JPS-04036: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.
Category:: Security
Cause:: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.
Action:: Ensure function name is of correct datatype.

JPS-04037: Name "{0}" starts or ends with whitespace.
Category:: Security
Cause:: Object name should not start with or end with whitespace.
Action:: Ensure object name has no whitespace in the beginning and end.

JPS-04038: Object name only contains whitespace.
Category:: Security
Cause:: Object name should not only contain whitespace.
Action:: Ensure object name doesn't only contain whitespace.

JPS-04039: Application "{0}", Deleting {1} entries under "{2}", Maximum remaining re-tries {3}.
Category:: Security
Cause:
Action:

JPS-04080: Scanning of system policy failed. Reason {0}
Category:: Security
Cause:: Scan of system policy failed.
Action:: Check the system policy setup and the provider setup.

JPS-04081: Policy store purge thread interrupted. Reason {0}.
Category:: Security
Cause:: Purge thread interrupted in policy caching.
Action:: Check the policy setup and the provider setup

JPS-04082: Deletion of system policy failed. Reason {0}
Category:: Security
Cause:: Deletion of system policy failed.
Action:: Provide legal non empty values for policy name

JPS-04083: Creation of system policy failed. Reason {0}
Category:: Security
Cause:: Creation of system policy failed.
Action:: Provide legal non empty values for policy name

JPS-04084: Migration of application policy failed. Further migration of application policies halted. Reason: {0}.
Category:: Security
Cause:: Exception in migration of application policy
Action:: Check application policy setup or contact system administrator

JPS-04085: Migration of codebase policy failed. Reason: {0}.
Category:: Security
Cause:: Exception in migration of codebase policy
Action:: Check codebase policy setup or contact system administrator

JPS-04086: Could not perform isPolicyModified. Reason {0}
Category:: Security
Cause:: Is policy modification check failed.
Action:: Contact system administrator

JPS-04089: Could not get policy cache count. Reason {0}
Category:: Security
Cause:: Could not retrieve policy cache count.
Action:: Contact system administrator

JPS-04090: The policy store property {0} is invalid or not defined.
Category:: Requests/Responses
Cause:: The policy store property {0} was invalid or not defined.
Action:: Check the configuration of this property.

JPS-04091: Application {0} is being deployed with policy migration option set to {1}, start policy migration.
Category:: Security
Cause:: Start application policy migration
Action:: No action required

JPS-04092: Application {0} is being deployed with policy migration option set to neither OVERWRITE nor MERGE, skip policy migration.
Category:: Security
Cause:: Skip application policy migration
Action:: No action required

JPS-04093: Application policy migration for application {0} is completed successfully.
Category:: Security
Cause:: Complete application policy migration
Action:: No action required

JPS-04094: Start removing application policies for Application {0}.
Category:: Security
Cause:: Start application policy removal
Action:: No action required

JPS-04095: Application policy removal for application {0} is completed successfully.
Category:: Security
Cause:: Complete application policy removal
Action:: No action required

JPS-04096: Application policies for application {0} was NOT removed in application undeployment with jps.policystore.removal set to OFF.
Category:: Security
Cause:: Skip application policy removal
Action:: No action required

JPS-04097: Application {0} is being deployed without existing application policies found in static deployment, start policy migration.
Category:: Security
Cause:: Start application policy migration in static deployment
Action:: No action required

JPS-04098: Start codebase policy migration for application {0}.
Category:: Security
Cause:: Start codebase policy migration
Action:: No action required

JPS-04099: Codebase policy migration for {0} is completed successfully.
Category:: Security
Cause:: Complete codebase policy migration
Action:: No action required

JPS-04100: Application Role "{0}" already exists.
Category:: Security
Cause:: Encountered two roles with identical names.
Action:: Modify a role to have a distinct name.

JPS-04101: Cannot create application role "{0}".
Category:: Security
Cause:: Failed to complete persist operation while creating an application role.
Action:: Refer to the base exception in logs to resolve the issue.

JPS-04102: Cannot create application role. Cause: Invalid Argument -- Multiple role categories supplied for single application role
Category:: Security
Cause:: Persist operation failed because more than one role category supplied for create role
Action:: Ensure supplied parameters are correct.

JPS-04110: Cannot delete application role "{0}". Cause: Application role not found.
Category:: Security
Cause:: Could not find an application role in the application policy.
Action:: Check the name of the application role.

JPS-04111: Cannot delete application role "{0}".
Category:: Security
Cause:: Could not remove application role from policy store.
Action:: Refer to the base exception in log files and correct the error.

JPS-04112: Cannot delete application role "{0}".
Category:: Security
Cause:: Could not remove application role "{0}" because it may be in use; this role is a member of one or more other application roles (nested role hierarchy).
Action:: Flatten the nested role hierarchy, and then remove the desired role. Alternatively, remove the application role using the option force set to true.

JPS-04113: Cannot delete application role "{0}".
Category:: Security
Cause:: Could not remove application role "{0}" because it may be in use, or contains enterprise groups or enterprise users.
Action:: Remove the enterprise groups and enterprise users from the application role, or remove the application role using the option force set to true.

JPS-04114: Cannot delete application role "{0}".
Category:: Security
Cause:: Could not remove application role "{0}" because it may be in use; this role has one or more permissions granted to it.
Action:: Revoke the permission(s) from the application role, and then remove the role. Alternatively, remove the application role using the option force set to true.

JPS-04120: Cannot add principal to application role.
Category:: Security
Cause:: Encountered an internal policy store error.
Action:: Refer to the base exception in log files and correct the error.

JPS-04121: Cannot add principal to application role "{0}".
Category:: Security
Cause:: Could not find application role in the application policy context.
Action:: Ensure the application role is present in the application policy.

JPS-04122: Cannot add principal to application role; principal(s) "{0}" is already a member of application role "{1}".
Category:: Security
Cause:: Found that principal {0} is already a member of the application role {1}.
Action:: Correct the principal name.

JPS-04123: Cannot add principal to the application role.
Category:: Security
Cause:: Attempted to insert an application role as a member of itself.
Action:: Correct the application role principal name. The containment in the role hierarchy must be cycle-free.

JPS-04124: The application role {0} added to {1} has no GUID defined.
Category:: Requests/Responses
Cause:: The application role {0} added to {1} has no GUID defined.
Action:: Ensure the application role has GUID before adding it as a member of an application role.

JPS-04125: Application Role {0} granted to role category {1} cannot be found in application {2}
Category:: Security
Cause:: Application Role {0} granted to role category {1} cannot be found in application {2}
Action:: Ensure application role exists before assigning it to a role category

JPS-04130: Cannot remove principal from application role.
Category:: Security
Cause:: Encountered an internal policy store error.
Action:: Refer to the base exception in log files and correct the error.

JPS-04131: Cannot remove principal from application role; cannot find application role "{0}" in application policy context.
Category:: Security
Cause:: Could not find the specified application role in the application policy context.
Action:: Correct the application role name.

JPS-04132: Cannot remove principal from application role; principal "{0}" is not member of application role "{1}".
Category:: Security
Cause:: See error message.
Action:: Correct the principal role name.

JPS-04135: Resource name not specified in application {0}.
Category:: Security
Cause:: Resource name not specified in application {0}.
Action:: Ensure the resource name is not null.

JPS-04136: Resource type name not specified in application {0}.
Category:: Security
Cause:: Resource type name not specified in application {0}.
Action:: Ensure the resource type name is not null.

JPS-04137: Permission set name not specified in application {0}.
Category:: Security
Cause:: Permission set name not specified in application {0}.
Action:: Ensure the permission set name is not null.

JPS-04138: Application role name not specified in application {0}.
Category:: Security
Cause:: Application role name not specified in application {0}.
Action:: Ensure the application role name is not null.

JPS-04140: Cannot complete application role search because search expression "{0}" is incorrect.
Category:: Security
Cause:: Found an invalid search pattern.
Action:: Refer to the base exception in log files and correct the error.

JPS-04141: Cannot complete application role search because of internal error {0}.
Category:: Security
Cause:: Encountered an internal policy store error while searching the policy store.
Action:: Refer to the base exception in log files and correct the error.

JPS-04142: Cannot complete application role search because search role attribute "{0}" is incorrect.
Category:: Security
Cause:: Could not complete the search because the application role attribute {0} was invalid.
Action:: Supply a valid role attribute name.

JPS-04143: Cannot find application role "{0}".
Category:: Security
Cause:: Could not find application role in the application policy context.
Action:: Supply the name of an existing application role name.

JPS-04144: Cannot get granted application role for principal "{0}".
Category:: Security
Cause:: Encountered an internal policy store error.
Action:: Refer to the base exception in log files and correct the error.

JPS-04145: Cannot get all application roles for application "{0}".
Category:: Security
Cause:: Encountered an internal policy store error.
Action:: Refer to the base exception in log files and correct the error.

JPS-04146: Cannot complete application role search because search role attribute name is null.
Category:: Security
Cause:: Could not complete the search because the role attribute name was NULL.
Action:: Provide a non-null role attribute name.

JPS-04147: Cannot get members of application role "{0}".
Category:: Security
Cause:: Could not find application role in the application policy context.
Action:: Supply the name of an existing application role name.

JPS-04148: Exception when converting "{0}" to number, msg is "{1}".
Category:: Security
Cause:: Exception when converting {0} to number, msg is {1}
Action:: Only number is allowed

JPS-04150: Cannot alter application role {0} since multiple entries found for the application name:{1} query: {2} and actual result is {3}.
Category:: Security
Cause:: Encountered the policy store error {0}.
Action:: Check the error details to resolve the issue.

JPS-04151: Cannot alter application role.
Category:: Security
Cause:: Could not find application role {0} in the application policy context.
Action:: Provide an existing application role name.

JPS-04153: In Domain {0}, Application {1} is not present.
Category:: Security
Cause:: Application not found in the policystore
Action:: Check the name of the application in the policystore.

JPS-04154: Refresh of application policy failed. Reason {0}
Category:: Security
Cause:: Refresh of application policy failed.
Action:: Check the application policy setup and the provider setup

JPS-04155: Scanning of application policy failed. Reason {0}
Category:: Security
Cause:: Scan of application policy failed.
Action:: Check the application policy setup and the provider setup

JPS-04156: RoleCategory modification attribute "{0}" is invalid.
Category:: Security
Cause:: Invalid RoleCategory modify attribute
Action:: Check whether the attribute you are trying to modify is valid or not.

JPS-04157: RoleCategory "{0}" already exists.
Category:: Security
Cause:: The role category already exists.
Action:: Supply a different role category name.

JPS-04158: RoleCategory {0} does not exist
Category:: Security
Cause:: The role category does not exist.
Action:: Supply a different role category name.

JPS-04159: Role category search value: {0}, is invalid for matcher type: {1}
Category:: Security
Cause:: The role category search query has invalid parameter value
Action:: Modify the search query and supply correct parameter value.

JPS-04160: Cannot find PermissionSet {0} in policy store.
Category:: Security
Cause:: Could not find PermissionSet in policy store.
Action:: Provide the name of a valid PermissionSet.

JPS-04161: Search for PermissionSet {0} by name yielded more than one result.
Category:: Security
Cause:: Found a duplicate PermissionSet name in search context.
Action:: Ensure that all PermissionSet names in the current search context are distinct.

JPS-04162: PermissionSet "{0}" already exists in policy store.
Category:: Security
Cause:: Permission Set already exists.
Action:: Create a PermissionSet with a different name.

JPS-04163: PermissionSet {0} cannot have empty ResourceActions.
Category:: Security
Cause:: PermissionSet {0} has empty ResourceActions.
Action:: Ensure PermissionSet has ResourceActions.

JPS-04164: MemberResource {0} of type {1} not found in application {1}.
Category:: Security
Cause:: MemberResource {0} of type {1} not found in application {1}.
Action:: Ensure the Resource exists in the PolicyStore.

JPS-04165: ResourceType {0} referenced by MemberResource {1} not found in application {2}.
Category:: Security
Cause:: ResourceType {0} referenced by MemberResource {1} not found in application {2}.
Action:: Ensure the ResourceType exists in the PolicyStore.

JPS-04166: MemberResource {0} of type {1} does not have actions defined.
Category:: Security
Cause:: MemberResource {0} of type {1} does not have actions defined.
Action:: Ensure the MemberResource has valid actions.

JPS-04167: MemberResource {0} of type {1} has actions defined.
Category:: Security
Cause:: MemberResource {0} of type {1} has actions defined.
Action:: Ensure the MemberResource does not have actions.

JPS-04168: PermissionSet {0} cannot be created without ResourceActions.
Category:: Security
Cause:: PermissionSet {0} cannot be created without ResourceActions.
Action:: Create a PermissionSet with ResourceActions.

JPS-04169: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.
Category:: Security
Cause:: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.
Action:: Modify PermissionSet using a ResourceAction that has valid actions.

JPS-04173: The resource type {0} is not found in store
Category:: Configuration
Cause:: Unsupported Resource Type {0}.
Action:: Check Resource Type.

JPS-04179: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence
Category:: Security
Cause:: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence.
Action:: Ensure the ResourceType reference exists for every resource.

JPS-04190: Cannot find resource.
Category:: Security
Cause:: Could not find resource in the resource store.
Action:: Modify your search query.

JPS-04191: Cannot find unregistered resource finder for resource type "{0}".
Category:: Security
Cause:: Could not find a registered resource finder for the resource type.
Action:: Provide a resource finder implementation for the resource type, and register it with JPS.

JPS-04192: Cannot load resource finder with provider name "{0}".
Category:: Security
Cause:: Found an incorrect implementation: argumentless public constructor is missing.
Action:: Revisit the implementation to provide an argumentless public constructor.

JPS-04193: Cannot load resource finder with provider name "{0}" and class "{1}".
Category:: Security
Cause:: Could not load resource finder class: error encountered while reading a registered class file for resource finder.
Action:: Check the configuration of the class property in jps-config.xml.

JPS-04194: Cannot initialize resource finder with provider name "{0}" and class name "{1}".
Category:: Security
Cause:: Found an error while initializing a registered class for resource finder.
Action:: Check the configuration of the class property in jps-config.xml.

JPS-04195: Cannot load the resource finder with provider "{0}".
Category:: Security
Cause:: Found an error in external resource finder configuration: a required property was missing.
Action:: Check the configuration of the class property in jps-config.xml.

JPS-04198: Resource {0} in application {1} has a non existent resource type {2}. Ignoring this resource.
Category:: Security
Cause:: Resource {0} in application {1} has a non existent resource type {2}. Ignoring this resource.
Action:: Ensure the ResourceType exists for every resource.

JPS-04200: Cannot grant policy due to a policy store internal error.
Category:: Security
Cause:: Encountered a policy store error.
Action:: Check the error details to resolve the issue.

JPS-04201: Cannot grant permission(s). Grant already exists for grantee {0}.
Category:: Security
Cause:: Permissions already granted to grantee.
Action:: Grant a different set of permissions.

JPS-04202: Cannot revoke policy.
Category:: Security
Cause:: Encountered an internal policy store error while revoking a policy.
Action:: Refer to the base exception in log files and correct the error.

JPS-04203: Cannot revoke permission.
Category:: Security
Cause:: Found that a permission has not been granted.
Action:: Provide the appropriate permission to the grantee.

JPS-04204: Cannot revoke permissions.
Category:: Security
Cause:: Found that permissions have not been granted.
Action:: Provide the appropriate permissions to the grantee.

JPS-04205: Cannot revoke permissions.
Category:: Security
Cause:: Found that permissions have not been granted to principals.
Action:: Provide the appropriate permissions to principals.

JPS-04206: Cannot revoke permissions.
Category:: Security
Cause:: Found that permissions have not been granted to code source.
Action:: Correct the code source grantee.

JPS-04207: Matching Grantee not found: {0}.
Category:: Security
Cause:: Found that permissions have not been granted to principals or code source.
Action:: Correct the list of principals and code source in the grantee, or revoke permissions granted to this grantee.

JPS-04208: Cannot modify policy due to a policy store internal error.
Category:: Security
Cause:: Encountered an internal policy store error while modifying the policy store.
Action:: Refer to the base exception in log files and correct the error.

JPS-04209: Cannot modify property {0}.
Category:: Security
Cause:: Could not modify a property.
Action:: Supply the name of a property that can be modified.

JPS-04210: Modification code {0} is invalid.
Category:: Security
Cause:: Found an unsupported modification code.
Action:: Ensure that the modification code is ADD, REMOVE, or REPLACE.

JPS-04211: Cannot query, update, or delete Object with type "{0}" and name "{1}".
Category:: Security
Cause:: Attempted to query, update, or delete an invalid policy store object.
Action:: Ensure that the object to be queried, updated, or deleted belongs to the appropriate policy domain

JPS-04212: PermissionSet "{0}" is in use, cannot delete.
Category:: Security
Cause:: Permission set already existed.
Action:: Permission set with the same name cannot be created. Use different name.

JPS-04213: Cannot modify a grant with an empty permission entry.
Category:: Security
Cause:: Encountered empty permission entry list while modifying a grant
Action:: Pass a non empty permission entry list while modifying a grant

JPS-04216: Cannot grant/revoke permissions because type "{0} " is not known.
Category:: Security
Cause:: Resource type validation for Permission set failed
Action:: Check whether the grant's permission's resourcetype is provisioned in the policystore.

JPS-04217: Grant/revoke failed for grantee "{0}", permission class "{1}", resource name "{2}", permission actions "{3}", resource type "{4}". Reason: permission actions is not a subset of resource type actions " {5}".
Category:: Security
Cause:: Resource type validation for Permission set failed
Action:: Check whether the actions in the Permission are valid actions for the resource type provisioned in the policy store.

JPS-04218: Grant/revoke failed for grantee "{0}", permission class "{1}", resource Name "{2}", permission actions "{3}", resource type "{4}". Reason: permission class is not equal to resource type matcher class " {5}".
Category:: Security
Cause:: Resource type validation for Permission set failed
Action:: Check whether the matcher class in the Permission is valid for the resource type provisioned in the policy store.

JPS-04219: The action {0} is invalid for resource type {1}.
Category:: Requests/Responses
Cause:: The action {0} is invalid for resource type {1}.
Action:: Check the ResourceActionsEntry parameter.

JPS-04220: Cannot search because the search query "{0}" was empty (has no child query).
Category:: Requests/Responses
Cause:: The search query {0} was empty (has no child query).
Action:: Provide a non-empty search query in.

JPS-04221: Cannot search because the grant search query "{0}" has illegal object type for search property "{1}".
Category:: Security
Cause:: The grant search query {0} has wrong object type in search value for search property {1}.
Action:: Provide an object type corresponding to the search property.

JPS-04222: Cannot search because the search query was null for "{0}" .
Category:: Requests/Responses
Cause:: The search query was null for {0} .
Action:: Provide a non-null search query .

JPS-04223: Access to tenant system policy is not allowed.
Category:: Security
Cause:: Access to tenant system policy is not allowed.
Action:: Access global system policy instead.

JPS-04227: The object name "{0}" is invalid.
Category:: Requests/Responses
Cause:: The object name {0} is invalid.
Action:: Pass a correct object name in.

JPS-04300: Cannot save policy.
Category:: Security
Cause:: Could not save policy. Cause {0}.
Action:: Check the log files and resolve the error.

JPS-04301: Cannot read from policy store. Reason is {0}, {1}
Category:: Security
Cause:: Could not read from the policy store.
Action:: Check the log files and resolve the error.

JPS-04302: Cannot read from policy store.
Category:: Configuration
Cause:: Could not find the location property {1} in instance {0}.
Action:: Ensure the location is set to a valid policy store file.

JPS-04303: Cannot read from policy store.
Category:: Configuration
Cause:: Could not find value for system property '{0}' or for location property '{2}' in instance '{1}'.
Action:: Ensure the location is set to a valid policy store file.

JPS-04304: Policy store instance descriptor {0}, location value {1} is ignored.
Category:: Configuration
Cause:: Could not find value for the system property '{0}', which overrides the descriptor property {1} in the policy store service instance.
Action:: Unset the system property so that the location is picked up from configuration in jps-config.xml.

JPS-04305: Could not determine the work folder for controlled and mixed mode PD.
Category:: Configuration
Cause:: Could not determine the work folder for controlled and mixed mode PD.
Action:: Ensure system property "oracle.security.jps.config" or "domain.home" is set and jps-config.xml is present under ${domain.home}/config/fmwconfig.

JPS-04410: Cannot create JACC module policy context "{0}" for application {1}.
Category:: Security
Cause:: Could not create application policy because found two application module contexts with identical names.
Action:: Ensure that all application module context names are distinct.

JPS-04411: Cannot create application "{0}" JACC module policy context "{1}".
Category:: Security
Cause:: Could not create application module policy; persist operation failed.
Action:: Refer to the base exception in log files and correct the error.

JPS-04412: Cannot delete JACC module "{0}".
Category:: Security
Cause:: Could not find JACC policy context to delete.
Action:: Check the JACC policy context name.

JPS-04413: Cannot delete JACC module policy context "{0}".
Category:: Security
Cause:: Could not delete JACC policy; persist operation failed.
Action:: Refer to the base exception in log files and correct the error.

JPS-04420: Application policy context name is missing from application role {0}.
Category:: Security
Cause:: Could not find application policy context in the application role principal.
Action:: Ensure that the application role principal has an application context.

JPS-04421: Administrator role name is invalid.
Category:: Security
Cause:: Found an invalid administrator role name.
Action:: Correct the name of the administrator role.

JPS-04422: Policy is malformed.
Category:: Security
Cause:: Found system policy that granted permissions to application role(s).
Action:: Grants to application roles are not allowed in a system policy. Remove such grants.

JPS-04423: Application role name "{0}" is invalid.
Category:: Security
Cause:: Found invalid application role name {0}.
Action:: Verify that the application role name conforms with the role name syntax.

JPS-04502: Java SSO Login
Category:: Requests/Responses
Cause:: This was JSSO page title.
Action:: No action needed.

JPS-04503: Enter your single sign-on username and password.
Category:: Requests/Responses
Cause:: User name and password were required for logging into JSSO.
Action:: Enter a valid user name and password.

JPS-04504: Username
Category:: Requests/Responses
Cause:: This was JSSO login user name.
Action:: No action needed.

JPS-04505: Password
Category:: Requests/Responses
Cause:: This was JSSO login user password.
Action:: No action needed.

JPS-04506: Login
Category:: Requests/Responses
Cause:: Submit button.
Action:: Press submit.

JPS-04507: Cancel
Category:: Requests/Responses
Cause:: Cancel button.
Action:: Press cancel to abort login.

JPS-04508: Failed.
Category:: Requests/Responses
Cause:: JSSO login failed.
Action:: Check user name and password used for login.

JPS-04509: The maximum number of login attempts is exceeded. Contact the application administrator, or retry after {0} minutes.
Category:: Requests/Responses
Cause:: Maximum login attempts was exceeded.
Action:: Contact the system administrator.

JPS-04510: Incorrect username or password.
Category:: Requests/Responses
Cause:: User name or password was invalid.
Action:: Check the user name and password used for login.

JPS-04511: Java SSO Application Error.
Category:: Requests/Responses
Cause:: Encountered and internal error.
Action:: Contact the system administrator.

JPS-04512: application error
Category:: Requests/Responses
Cause:: Encountered and internal error.
Action:: Contact the system administrator.

JPS-04513: The Java SSO application is not properly configured.
Category:: Configuration
Cause:: The Java SSO application was not correctly configured.
Action:: Reconfigure the application.

JPS-04514: Configuration error: {0}.
Category:: Configuration
Cause:: The Java SSO application was not correctly configured.
Action:: Reconfigure the application.

JPS-04515: Usage arguments:
Category:: Requests/Responses
Cause:: Defines the keytool usage.
Action:: See error message.

JPS-04516: No key type for algorithm.
Category:: Configuration
Cause:: The algorithm key type was not specified.
Action:: Configure the algorithm key type.

JPS-04517: Key does not match any known algorithm.
Category:: Configuration
Cause:: The given key did not match the corresponding algorithm.
Action:: Reconfigure the algorithm key type.

JPS-04518: The number of JSSO cookies is zero or invalid.
Category:: Requests/Responses
Cause:: Could not find JSSO cookie in header.
Action:: Login again or contact the system administrator.

JPS-04519: The number of Oracle Access Manager cookies is zero or invalid.
Category:: Requests/Responses
Cause:: Could not find Oracle Access Manager cookie in header.
Action:: Login again or contact the system administrator.

JPS-04520: Token type is invalid: expected type is COOKIE_TOKEN, but found {0}.
Category:: Configuration
Cause:: The token type configured was invalid: it should be COOKIE_TOKEN.
Action:: Reconfigure the token type to a valid value.

JPS-04521: The JSSO property {0} is not set.
Category:: Configuration
Cause:: JSSO property was not correctly configured.
Action:: Reconfigure the property to a correct value.

JPS-04522: The authentication type {0} is invalid.
Category:: Configuration
Cause:: JSSO did not support this authentication type.
Action:: Reconfigure the type to a supported type.

JPS-04523: Token is no longer valid.
Category:: Requests/Responses
Cause:: The incoming token was no longer valid.
Action:: Login again.

JPS-04524: Cannot create token from JSSO cookie.
Category:: Requests/Responses
Cause:: Could not create token from the JSSO cookie; cookie may have expired.
Action:: Login again.

JPS-04525: The number of cookies is zero or the invalid number {0}.
Category:: Requests/Responses
Cause:: Could not find at least one cookie in the request.
Action:: Login again.

JPS-04526: Token has invalid version number.
Category:: Requests/Responses
Cause:: Token had invalid version number.
Action:: Login again.

JPS-04527: Token has an invalid format.
Category:: Requests/Responses
Cause:: Token was corrupted or had invalid format.
Action:: Login again.

JPS-04528: An error occurred while encoding JSSO token.
Category:: Configuration
Cause:: Could not encode JSSO token.
Action:: Specify a valid, supported encoding.

JPS-04529: Cannot verify signature in the JSSO token.
Category:: Requests/Responses
Cause:: Could not verify signature: the token was tampered with, or the signature algorithm was invalid.
Action:: Specify a supported signature algorithm.

JPS-04530: Algorithm is unsupported.
Category:: Configuration
Cause:: Specified algorithm was unsupported.
Action:: Check documentation for the list of supported algorithms.

JPS-04531: Error creating cipher.
Category:: Configuration
Cause:: Could not create cipher.
Action:: Check documentation for the list of supported cipher algorithms.

JPS-04532: JSSO logout URL is not configured.
Category:: Configuration
Cause:: The logout URL was not configured or invalid.
Action:: Check the logout URL configuration properties, and reconfigure it to a valid URL.

JPS-04533: JSSO has encountered an unexpected error.
Category:: Requests/Responses
Cause:: An internal error occurred.
Action:: Contact the system administrator.

JPS-04534: JSSO symmetric key is missing.
Category:: Configuration
Cause:: The symmetric key configuration was missing.
Action:: Ensure that the properties "custom.sso.cred.key" and "custom.sso.cred.alias" are configured in the service instance, and that the symmetric key is present in the credential store.

JPS-04535: Identity name is invalid.
Category:: Configuration
Cause:: User identity was invalid or missing.
Action:: Provide a valid user identity.

JPS-04536: The token name {0} is missing in request object.
Category:: Configuration
Cause:: Token name was missing in the request object.
Action:: Ensure that the token name is present in the request object.

JPS-04537: No token name is specified for token collector {0}.
Category:: Configuration
Cause:: Token collector was invalid or missing.
Action:: Configure a valid token collector with the property "idm.token.collector.class".

JPS-04538: The request object class is invalid.
Category:: Configuration
Cause:: The request object class was invalid.
Action:: Ensure that the request object is valid.

JPS-04539: Token collector is not properly initialized.
Category:: Configuration
Cause:: Could not initialize the token collector.
Action:: Ensure that the token collector is correctly configured and initialized.

JPS-04540: The token asserter is not properly initialized.
Category:: Configuration
Cause:: Could not initialize the token asserter.
Action:: Ensure that the token asserter is correctly configured and initialized.

JPS-04541: Cannot find authenticated identity.
Category:: Configuration
Cause:: Authentication failed.
Action:: Provide a valid identity.

JPS-04542: The token collector class {0} is not properly configured in the configuration file.
Category:: Configuration
Cause:: Token collector class was missing.
Action:: Configure a valid token collector class with the property "idm.token.collector.class".

JPS-04543: No login module is configured for application.
Category:: Configuration
Cause:: Could not find configured login module.
Action:: Configure a login module in jps-config.xml.

JPS-04544: The subject of the identity is invalid.
Category:: Configuration
Cause:: Subject was missing.
Action:: Ensure that the valid Subject is present.

JPS-04545: Cannot verify the Subject {0}.
Category:: Configuration
Cause:: Could not verify Subject.
Action:: Check the user credentials.

JPS-04546: The configuration (idm.subject.loginmodule.disabled=true) specifies that the Subject is populated by the token asserter.
Category:: Configuration
Cause:: Could not find Subject asserter.
Action:: Configure an asserter to use a login module that returns a valid Subject.

JPS-04547: The token type {0} is not properly configured in the configuration file.
Category:: Configuration
Cause:: Could not find token type configuration.
Action:: Configure a token type in the service instance with the property "idm.token.type property".

JPS-04548: The token asserter class {0} is not properly configured in the configuration file.
Category:: Configuration
Cause:: Could not find token asserter class configuration.
Action:: Configure a token asseter class in the service instance with the property "idm.token.asserter.class".

JPS-04549: Token is no longer valid.
Category:: Configuration
Cause:: Found invalid or expired token.
Action:: Check that the token is valid and has not expired.

JPS-04550: Token type is invalid: expected type is HEADER_TOKEN, but found {0}.
Category:: Configuration
Cause:: Token type was invalid: it should be HEADER_TOKEN.
Action:: Reconfigure the token type to a valid type.

JPS-04551: The number of OSSO headers is zero or an invalid number.
Category:: Requests/Responses
Cause:: Could not find OSSO header in HTTP request.
Action:: Login again, or contact the system administrator.

JPS-04552: The required Oracle Access Manager property {0} is missing or invalid.
Category:: Configuration
Cause:: A required Oracle Access Manager property was missing or invalid.
Action:: Configure the property "access.sdk.install.path" in the service instance in jps-config.xml.

JPS-04553: The user identity {0} for Oracle Access Manager is invalid.
Category:: Requests/Responses
Cause:: The user identity for Oracle Access Manager was invalid.
Action:: Login again.

JPS-04554: The user password for Oracle Access Manager is invalid.
Category:: Requests/Responses
Cause:: The user password for Oracle Access Manager was invalid.
Action:: Login again.

JPS-04555: The user {0} is not logged in to Oracle Access Manager. The error is {1}.
Category:: Requests/Responses
Cause:: The user was not logged in Oracle Access Manager.
Action:: Login again.

JPS-04556: The user {0} is not authorized to access a resource type authentication in Oracle Access Manager.
Category:: Requests/Responses
Cause:: The user was not logged in Oracle Access Manager.
Action:: Login again.

JPS-04557: Invalid parameter {0} supplied. Cannot be null or empty.
Category:: Requests/Responses
Cause:: Invalid parameter {0} supplied. Cannot be null or empty.
Action:: Ensure the parameter is not null or empty.

JPS-04558: The SSO service is not properly configured: {0}.
Category:: Configuration
Cause:: The SSO service is not properly configured: {0}.
Action:: Check the SSO Service configuration.

JPS-04559: Failed to create the {0} token. Cause: {1}.
Category:: Requests/Responses
Cause:: Failed to create the {0} token. Cause: {1}.
Action:: Re-login.

JPS-04560: SSO provider cannot initiate SSO process: {0}.
Category:: Requests/Responses
Cause:: SSO provider cannot initiate SSO process: {0}.
Action:: Check the SSO Service configuration.

JPS-04561: Invalid parameter {0} supplied. Cannot be null.
Category:: Requests/Responses
Cause:: Invalid parameter {0} supplied. Cannot be null.
Action:: Ensure the parameter is not null.

JPS-04601: Cannot obtain audit service for policy store.
Category:: Security
Cause:: Could not query audit service about audit logging level for policy store messages.
Action:: Ensure that auditing is configured correctly.

JPS-04602: Cannot log policy management event to the audit service.
Category:: Security
Cause:: Could not log policy management audit messages to the audit service.
Action:: Ensure that auditing is configured correctly in your environment and application.

JPS-05500: Cannot create the user manager MBean.
Category:: Configuration
Cause:: Could not create the user manager MBean.
Action:: Check errors in log files and contact the domain administrator.

JPS-05501: Cannot create the role manager MBean.
Category:: Configuration
Cause:: Could not create the role manager MBean.
Action:: Check the log files for errors and contact domain administrator.

JPS-05502: Cannot create the identity store MBean.
Category:: Configuration
Cause:: Could not create the identity store MBean.
Action:: Check log files and contact the domain administrator.

JPS-05513: Failed to determine realms to migrate file {0}. Reason {1}.
Category:: Programmatic
Cause:: Failed determine realms to migrate file {0}. Reason {1}.
Action:: Check log files and try again.

JPS-05521: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.
Category:: Requests/Responses
Cause:: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.
Action:: Use a valid value.

JPS-05542: Bootstrap credential store context missing
Category:: Compliance
Cause:: Could not find bootstrap credstore context
Action:: Contact aystem administrator

JPS-05546: Bootstrap credential store service missing
Category:: Compliance
Cause:: Could not find bootstrap credstore service
Action:: Contact system administrator

JPS-05626: Bootstrap credential already present in store
Category:: Compliance
Cause:: Credential already present in the store
Action:: use different map name or key name for the credential

JPS-05657: Bootstrap credential store context {0} missing
Category:: Compliance
Cause:: Could not find bootstrap credential store context
Action:: Contact aystem administrator

JPS-05658: Bootstrap credential store service {0} missing from bootstrap credential store context {1}
Category:: Compliance
Cause:: Could not find bootstrap credential store service
Action:: Contact system administrator

JPS-05659: location attribute missing from bootstrap credential store service {0}
Category:: Compliance
Cause:: Could not find location attribute of bootstrap credential store service
Action:: Contact system administrator

JPS-06000: The source context {0} is missing in jps configuration file.
Category:: Configuration
Cause:: While migrating a security store, found that the context, specified as source {0}, did not exist in jps-config.xml.
Action:: Provide a context for source that is present in jps-config.xml.

JPS-06001: The destination context {0} is missing in jps configuration file.
Category:: Configuration
Cause:: While migration of a security store, found that the context, specified as destination {0}, did not exist in jps-config.xml.
Action:: Provide a context for destination that is present in jps-config.xml.

JPS-06002: Cannot clean the destination credential store. Reason {0}.
Category:: Upgrade
Cause:: A codebase grant was found without the required permissions.
Action:: Set the right permissions to the codebase grant.

JPS-06003: Cannot migrate credential folder/key {0}/{1}.Reason {2}.
Category:: Upgrade
Cause:: Cannot migrate this credential.
Action:: Verify that the credential is correctly specified.

JPS-06004: Cannot migrate an unknown user. Reason {0}.
Category:: Upgrade
Cause:: Cannot migrate this user.
Action:: Verify that the user is correctly specified.

JPS-06005: Cannot get password of user {0}. Reason {1}.
Category:: Upgrade
Cause:: Cannot get this user password.
Action:: Verify that the password is correctly specified.

JPS-06006: Cannot migrate user {0}. Reason {1}.
Category:: Upgrade
Cause:: Cannot migrate this user name.
Action:: Verify that the user name is correctly specified.

JPS-06007: Cannot migrate an unknown role. Reason {0}.
Category:: Upgrade
Cause:: Cannot migrate this role.
Action:: Verify that the role is correctly specified.

JPS-06008: Cannot migrate role {0}. Reason {1}.
Category:: Upgrade
Cause:: Cannot migrate this role name.
Action:: Verify that the role name is correctly specified.

JPS-06009: Cannot migrate any member of role {0}. Reason {1}.
Category:: Upgrade
Cause:: Cannot migrate members.
Action:: Verify that the members are correctly specified.

JPS-06010: Cannot migrate an unknown member of role {0}. Reason {1}.
Category:: Upgrade
Cause:: Cannot migrate this member.
Action:: Verify that the member is correctly specified.

JPS-06011: Cannot migrate member {0} of role: {1}. Reason {2}.
Category:: Upgrade
Cause:: Cannot migrate this member name.
Action:: Verify that the member name is correctly specified.

JPS-06012: Cannot migrate a global grant. Reason {0}.
Category:: Upgrade
Cause:: Could not migrate a global grant. Reason {0}.
Action:: Verify that the grant is correctly specified.

JPS-06013: Cannot migrate an application grant. Reason {0}.
Category:: Upgrade
Cause:: Could not migrate an application grant. Reason {0}.
Action:: Verify that the application grant is correctly specified.

JPS-06014: Cannot migrate an indirect password for {0}. Reason {1}.
Category:: Upgrade
Cause:: Could not migrate an indirect password due to an exception.
Action:: Verify that the indirect password is correctly specified.

JPS-06015: Cannot migrate an indirect password for {0} because the specified realm is null.
Category:: Upgrade
Cause:: Could not migrate an indirect password because the given realm was null.
Action:: Provide a non-null realm.

JPS-06016: Cannot migrate an indirect password for {0} because the specified user name is null.
Category:: Upgrade
Cause:: Could not migrate an indirect password because the given user name was null.
Action:: Provide a non-null user name.

JPS-06017: Cannot migrate an indirect password for {0} because the specified realm does not exist.
Category:: Upgrade
Cause:: Could not migrate an indirect password because the input realm does not exist.
Action:: Provide an existing realm.

JPS-06018: Cannot migrate an indirect password for {0} because the specified user does not exist.
Category:: Upgrade
Cause:: Could not migrate an indirect password because the input user does not exist.
Action:: Provide an existing user.

JPS-06019: The identity store associated with context {0} is missing in jps-config.xml.
Category:: Configuration
Cause:: While migration of a policy store, found that the context, specified as containing the associated identity store {0}, did not exist in jps-config.xml.
Action:: Provide a context to associate identity store that is present in jps-config.xml.

JPS-06020: The principal class {0} specified in the source policy store cannot be loaded. Reason {1}.
Category:: Upgrade
Cause:: Could not load a class. Reason {0}.
Action:: Ensure the class is in the class path.

JPS-06021: Cannot migrate the credentials in the folder {0}. Reason: {1}.
Category:: Upgrade
Cause:: Cannot migrate the credentials in this folder.
Action:: Check the folder in the source credential store.

JPS-06022: Cannot determine the folder to be migrated.
Category:: Upgrade
Cause:: The credential store has more than one folder and the folder to be migrated was not defined.
Action:: Specify the folder to be migrated.

JPS-06023: The input file {0} specified for migration or upgrade is not valid.
Category:: Upgrade
Cause:: The file {0} was non-readable, empty, or did not exist.
Action:: Provide a valid file.

JPS-06024: Cannot initialize the destination identity store.
Category:: Upgrade
Cause:: One or more required configuration properties were not be properly defined.
Action:: Check the configuration of the destination identity store.

JPS-06025: There are undefined credential properties for the destination identity store.
Category:: Upgrade
Cause:: One or more required configuration properties for credentials were not defined.
Action:: Check the configuration of the destination identity store.

JPS-06026: Cannot get credentials for the destination identity store from the domain credential store.
Category:: Upgrade
Cause:: Credentials were not found in the domain credential store.
Action:: Ensure that the domain credential store has the appropriate credentials.

JPS-06027: Cannot migrate the specified realm.
Category:: Upgrade
Cause:: The specified realm was not found in the source store.
Action:: Specify a valid realm name.

JPS-06028: The required identity store property {0} required for migration is undefined.
Category:: Other
Cause:: A property required for migration was not configured in the identity store.
Action:: Specify the missing configuration property.

JPS-06029: JAZN properties cannot be read from config file {0}.
Category:: Upgrade
Cause:: JAZN properties could not be read from config file {0}.
Action:: Check the configuration file and try again.

JPS-06030: The required JAZN property {0} could not be read.
Category:: Upgrade
Cause:: A required JAZN property {0} could not be read.
Action:: Check the configuration file and try again.

JPS-06031: No application is configured in the source policy store.
Category:: Upgrade
Cause:: No application was configured in the source policy store.
Action:: Check the source policy store.

JPS-06032: Unable to determine the application policy to migrate.
Category:: Upgrade
Cause:: More than one application was configured in the source policy store.
Action:: Check the source policy store.

JPS-06033: The source credential store contains no credentials.
Category:: Requests/Responses
Cause:: The requested credential was not found in the credential store.
Action:: Ensure that the credential store has the requested credential.

JPS-06034: The folder {0} is missing in the credential store.
Category:: Requests/Responses
Cause:: The requested map name was not found in the credential store.
Action:: Ensure that the credential store contains the requested map name.

JPS-06035: The destination file {0} already exists; the existing LDIF file will not be appended or overwritten.
Category:: Requests/Responses
Cause:: The destination file is already present.
Action:: Delete the destination file, or provide the name of a non-existing file.

JPS-06036: Cannot determine the default realm to migrate file {0}. Reason {1}.
Category:: Programmatic
Cause:: An internal error occurred while determining the default realm.
Action:: Check log files and try again.

JPS-06037: Cannot initialize the source credential store.
Category:: Upgrade
Cause:: The configuration for the credential store was invalid.
Action:: Verify that the credential store configuration is correct and try again.

JPS-06038: Cannot initialize the destination credential store.
Category:: Upgrade
Cause:: The configuration for the credential store was invalid.
Action:: Verify that the credential store configuration is correct and try again.

JPS-06039: Cannot migrate property {0} of user {1}. Reason {2}.
Category:: Upgrade
Cause:: Cannot migrate property {0} for user {1}. Reason {2}.
Action:: Check the log files and retry migrating.

JPS-06040: Cannot migrate property {0} of role {1}. Reason {2}.
Category:: Upgrade
Cause:: Cannot migrate property {0} for role {1}. Reason {2}.
Action:: Check the log files and retry migrating.

JPS-06041: The switch or keyword " {0} " is not applicable to " {1} = {2} ".
Category:: Requests/Responses
Cause:: One or more optional switches or keywords were invalid.
Action:: Refer to the command documentation for the correct usage.

JPS-06042: Invalid scope for migration.
Category:: Requests/Responses
Cause:: Value of scope keyword was invalid.
Action:: Enter only one of the defined values/alias of scope as a value for the keyword scope.

JPS-06043: The source application is undefined but required to migrate application-specific policies.
Category:: Requests/Responses
Cause:: Optional keyword srcApp was not defined.
Action:: Specify, in the parameter srcApp, the value of the application whose policies are to be migrated.

JPS-06044: Cannot create the temporary file {0}.
Category:: Programmatic
Cause:: Could not write the XML file.
Action:: Check permissions or disk space in the java.io.tmpdir directory.

JPS-06045: Cannot parse the file {0}.
Category:: Programmatic
Cause:: Could not parse the XML file.
Action:: Check that the file is present in the java.io.tmpdir directory, and that it contains well-formed XML.

JPS-06046: Cannot delete the file {0}.
Category:: Programmatic
Cause:: The temp file could not be deleted.
Action:: Check that the file is not being accessed by other applications.

JPS-06047: Cannot migrate user credentials of user {0}.
Category:: Configuration
Cause:: The source identity store was configured not to give cleartext password.
Action:: Configure the source identity store to obfuscate password.

JPS-06048: Null values passed in for username or application stripes.
Category:: Programmatic
Cause:: The user name or the application stripe was null.
Action:: The user name must not be null. The list of application names must be null if only global policies are to be extracted.

JPS-06049: Application list is empty. Only global policies will be extracted.
Category:: Programmatic
Cause:: The list of applications was empty.
Action:: Only global policies are collected.

JPS-06050: file {0} was not found
Category:: Programmatic
Cause:: The xml file was not found.
Action:: Check if the file is present in the java.io.tmpdir directory.

JPS-06051: Processing of privilege roles is supported only when migrating an XML Policy store to an LDAP Policy Store.
Category:: Upgrade
Cause:: Processing of privilege roles was supported only when migrating an XML policy store to an LDAP policy store.
Action:: Make sure that the source store is XML-based and the destination store is LDAP-based.

JPS-06052: Error while processing a PermissionSet grant.
Category:: Upgrade
Cause:: Error encountered while processing permissionSet grant.
Action:: Check log files for details.

JPS-06053: Processing privilege roles failed. Cause {0}
Category:: Upgrade
Cause:: The processing of privilege roles failed.
Action:: Check log files for detials.

JPS-06054: Error in creating resourceTypes in destination store. Cause {0}
Category:: Upgrade
Cause:: Error encountered while creating resourceTypes in destination store.
Action:: Check log files for detials.

JPS-06055: Location of the ldif file containing resourceType definitions cannot be null.
Category:: Upgrade
Cause:: Location of the LDIF file containing resourceType definitions was null or not found.
Action:: Provide the absolute path for the resource file.

JPS-06056: Error while reading resource type file {0}.
Category:: Upgrade
Cause:: Error encountered while reading the resource type file {0}.
Action:: Ensure that the file exists and that it has the expected format.

JPS-06057: Resource type name or matcher class cannot be null.
Category:: Upgrade
Cause:: Resource type name or matcher class was null.
Action:: Provide a valid name and matcher class for the resource type.

JPS-06058: Permission class {0} with more than one matching resource type found.
Category:: Upgrade
Cause:: Permission class had more than one matching resource type.
Action:: Ensure that the a permission class has just one matching resource type.

JPS-06059: A grant entry containing {0} as one of principals has multiple principal entries. This entry cannot be processed.
Category:: Upgrade
Cause:: A grant for a privilege role had multiple principals.
Action:: Ensure that the privilege role grant has a single principal.

JPS-06060: The resource type definition file is missing.
Category:: Upgrade
Cause:: The resource type definition file was not found.
Action:: Provide the absolute path location for the resource definition file in LDIF format when using the option procPrivOption.

JPS-06061: The switch or keyword " {0} " is not defined for " {1} = {2} ".
Category:: Requests/Responses
Cause:: One or more optional switches or keywords were invalid.
Action:: Refer to the command documentation for the correct usage.

JPS-06062: Application role {0} corresponding to a member application role not defined.
Category:: Upgrade
Cause:: Application role not defined.
Action:: Check logs for detials.

JPS-06063: No Matching resource type definition found for permission class {0}.
Category:: Upgrade
Cause:: Permission class representing resource granted to a privilleged role does not have corresponding resource type definition.
Action:: Make sure a permission class has one matching resource type.

JPS-06064: Error getting the application role {0} from the source policy store
Category:: Upgrade
Cause:: The application role was either not present or defined multiple times.
Action:: Check the source policy store and make sure that the application role is uniquely defined.

JPS-06065: Report generation failed
Category:: Configuration
Cause:: .
Action:: .

JPS-06066: Invalid value for mode: {0}.
Category:: Security
Cause:: Invalid value for mode: {0}.
Action:: Make sure the value for mode is valid

JPS-06067: {0} config file either not found or not a valid file.
Category:: Upgrade
Cause:: {0} config file either not found or not a valid file
Action:: Make sure to provide a valid config file

JPS-06068: Unable to read configurations from jazn config file : {0}.
Category:: Upgrade
Cause:: Unable to read configurations from jazn data file : {0}.
Action:: Check the jazn data file.

JPS-06069: Provider referred from jazn config file {0} is of type XML and not LDAP.
Category:: Upgrade
Cause:: Provider referred from jps-config file {0} is of type XML and not LDAP.
Action:: Refer to a provider of type LDAP.

JPS-06070: Unable to read policies from policy store.
Category:: Upgrade
Cause:: Unable to read policies from policy store.
Action:: Check the policy store.

JPS-06071: Unable to read global policies from policy store.
Category:: Upgrade
Cause:: Unable to read global policies from policy store.
Action:: Check the policy store.

JPS-06072: Unable to read permissions for grantee {0} from policy store.
Category:: Upgrade
Cause:: Unable to read permissions for grantee {0} from policy store.
Action:: Check the policy store.

JPS-06073: Unable to read realm policies from policy store.
Category:: Upgrade
Cause:: Unable to read realm policies from policy store.
Action:: Check the policy store.

JPS-06074: Unable to read realm policies from realm {0} from policy store.
Category:: Upgrade
Cause:: Unable to read realm policies from realm {0} from policy store.
Action:: Check the policy store.

JPS-06075: Unsupported resource type file format. Use either an ldif file or a jazn-data with only resource type definitions.
Category:: Upgrade
Cause:: Unsupported resource type file format.
Action:: Use either an ldif file or a jazn-data with only resource type definitions.

JPS-06076: A Resource Type referred by {0} is expected to have a matching class {1} but has {2}.
Category:: Upgrade
Cause:: A Resource Type referred by a Permission is expected to have the same matching class as defined in the Permission
Action:: Make sure a permission class has one matching resource type with the same class name.

JPS-06077: A Resource Type referred by {0} is not defined.
Category:: Upgrade
Cause:: A Resource Type referred by a Permission is not defined.
Action:: Make sure a permission class has one matching resource type.

JPS-06078: Cannot migrate keystore/stripe {0}/{1}.Reason {2}.
Category:: Upgrade
Cause:: Cannot migrate the keystore in this stripe.
Action:: Check the keystore and stripe in the source keystore service.

JPS-06079: Cannot determine the stripe to be migrated.
Category:: Upgrade
Cause:: The keystore service has more than one stripes and the stripe to be migrated was not defined.
Action:: Specify the stripe to be migrated.

JPS-06080: The source keystore service contains no keystore within the given application stripe.
Category:: Requests/Responses
Cause:: The requested keystore was not found in the keystore service.
Action:: Ensure that the keystore service has the requested keystore.

JPS-06082: Cannot initialize the source keystore service.
Category:: Upgrade
Cause:: The configuration for the keystore service was invalid.
Action:: Verify that the keystore service configuration is correct and try again.

JPS-06083: Cannot initialize the destination keystore service.
Category:: Upgrade
Cause:: The configuration for the keystore service was invalid.
Action:: Verify that the keystore service configuration is correct and try again.

JPS-06084: Cannot clean the destination keystore service. Reason {0}.
Category:: Upgrade
Cause:: A codebase grant was found without the required permissions.
Action:: Set the right permissions to the codebase grant.

JPS-06085: Resource types not defined for the application {0}.
Category:: Upgrade
Cause:: Resource Types not found for the application {0}.
Action:: Define the resource types for the application {0}.

JPS-06086: Cannot upgrade policies for application {0}.
Category:: Upgrade
Cause:: Exception during policy upgradation.
Action:: Check the Causing exception and fix the error.

JPS-06087: Duplicate permissions: {0} present in grant in source.
Category:: Upgrade
Cause:: Duplicate permissions are present in a grant in source.
Action:: See error message.

JPS-06088: Duplicates principals:{0} present in grant in source.
Category:: Upgrade
Cause:: Duplicates principals are present in a grant in source.
Action:: See error message.

JPS-06089: Duplicate grant {0} present in source.
Category:: Upgrade
Cause:: Duplicate grants are present in source.
Action:: See error message.

JPS-06090: Duplicate app-role {0} present in source.
Category:: Upgrade
Cause:: Duplicate app-roles are present in source.
Action:: See error message.

JPS-06091: Duplicate member {0} present in an app-role in source.
Category:: Upgrade
Cause:: Duplicate members are present in an app-role in source.
Action:: See error message.

JPS-06092: Can not overwrite global policy.
Category:: Upgrade
Cause:: Can not overwrite global policy.
Action:: Do not set overwrite to true

JPS-06100: Policy Store version {0} and Oracle Platform Security Services Version {1} are not compatible.
Category:: Security
Cause:: The policy store version and the version of Oracle Platform Security Services does not match
Action:: Upgrade your binaries or your policy store.

JPS-06101: Cannot initialize the source auditstore service.
Category:: Upgrade
Cause:: The configuration for the audit store was invalid.
Action:: Verify that the audit store configuration is correct and try again.

JPS-06102: Cannot initialize the destination auditstore service.
Category:: Upgrade
Cause:: The configuration for the audit store was invalid.
Action:: Verify that the audit store configuration is correct and try again.

JPS-06103: Default Admin Role {0} not found in the policy domain {1} in the destination policy store
Category:: Security
Cause:: The destination policy store may not conform to leates version and need to be upgraded
Action:: See error message.

JPS-06104: Default Admin Role {0} not found in the application {1} in the destination policy store
Category:: Security
Cause:: The destination policy store may not conform to leates version and need to be upgraded
Action:: See error message.

JPS-06105: Default system Admin Role {0} not found in the destination policy store
Category:: Security
Cause:: The destination policy store may not conform to leates version and need to be upgraded
Action:: See error message.

JPS-06106: Instantiation of bootstrap credential store specified in file {0} failed. Reason {1}
Category:: Requests/Responses
Cause:: The configuration provided is not valid.
Action:: Provide a valid configuration file which has configuration for bootstrap credential.

JPS-06107: Instantiation of credential store at path {0} failed. Reason: {1}
Category:: Requests/Responses
Cause:: An underlying exception prevented initialization of credentials file.
Action:: Check the cause of the exception and fix it.

JPS-06108: Import/Export of keys failed. Reason: {0}
Category:: Requests/Responses
Cause:: An underlying exception prevented exporting/importing of key.
Action:: Check the cause of the exception and fix it.

JPS-06109: Cannot read key from key file in Directory {0}. Reason {1}.
Category:: Requests/Responses
Cause:: An underlying exception prevented reading of key.
Action:: Check the cause of the exception and fix it.

JPS-06110: Key file Directory {0} does not have write permissions.
Category:: Requests/Responses
Cause:: Key file directory not writable.
Action:: Change the permissions of the directory.

JPS-06111: Key file Directory {0} does not have read permissions.
Category:: Requests/Responses
Cause:: Key file directory is not readable.
Action:: Change the permissions of the directory.

JPS-06112: Key file Directory {0} does not exist.
Category:: Requests/Responses
Cause:: The path specified either donnot exist or is not a directory.
Action:: Provide a valid directory.

JPS-06113: Configuration file {0} is not valid. It is either not present or does not have read permissions.}
Category:: Requests/Responses
Cause:: The file is either not present or is not readable.
Action:: Provide a valid file.

JPS-06114: Key is not present in the key file in Directory {0}.
Category:: Requests/Responses
Cause:: Export might have not completed successfully.
Action:: Provide key file that has key in it.

JPS-06115: Empty DB username information. Please make sure to provide the correct jdbcUser info.
Category:: Requests/Responses
Cause:: Empty DB username information.
Action:: Please make sure to provide the correct jdbcUser info.

JPS-06116: Empty DB password information. Please make sure to provide the correct jdbcPassword info.
Category:: Requests/Responses
Cause:: Empty DB password information.
Action:: Please make sure to provide the correct jdbcPassword info.

JPS-06117: Empty JDBC host and port information. Please make sure to provide the correct jdbcUrl info.
Category:: Requests/Responses
Cause:: Empty DB host and port information.
Action:: Please make sure to provide the correct jdbcUrl info.

JPS-06118: Empty JDBC Driver information. Please make sure to provide the correct jdbcDriver info.
Category:: Requests/Responses
Cause:: Empty JDBC Driver information.
Action:: Please make sure to provide the correct jdbcDriver info.

JPS-06119: Recovery failed. Key backup not Found.
Category:: Requests/Responses
Cause:: No import was performed or import was not sucessfull.
Action:: import the key(s) again.

JPS-06120: Policystore is already upgraded, so it will not be upgraded again.
Category:: Upgrade
Cause:: Policystore is already upgraded.
Action:: Policystore will not be upgraded again.

JPS-06121: Keystore is already upgraded, so it will not be upgraded again.
Category:: Upgrade
Cause:: Keystore is already upgraded.
Action:: Keystore will not be upgraded again.

JPS-06122: Auditstore is already upgraded, so it will not be upgraded again.
Category:: Upgrade
Cause:: Auditstore is already upgraded.
Action:: Auditstore will not be upgraded again.

JPS-06123: XACML Policy/PolicySet Defaults not supported in OES.
Category:: Programmatic
Cause:: XACML Policy/PolicySet Defaults not supported in OES.
Action:: XACML Policy/PolicySet Defaults not supported in OES.

JPS-06124: XACML Policy/PolicySet Max Delegation Depth not supported in OES.
Category:: Programmatic
Cause:: XACML Policy/PolicySet Max Delegation Depth not supported in OES.
Action:: XACML Policy/PolicySet Max Delegation Depth not supported in OES.

JPS-06125: XACML attribute Issuer not supported in OES for the element {0}.
Category:: Programmatic
Cause:: XACML attribute Issuer not supported in OES.
Action:: XACML attribute Issuer not supported in OES.

JPS-06126: XACML PolicySet/Policy/Rule Combiner Parameters not supported in OES.
Category:: Programmatic
Cause:: XACML Policy/Rule Combiner Parameters not supported in OES.
Action:: XACML Policy/Rule Combiner Parameters not supported in OES.

JPS-06127: XACML Attribute Selector not supported in OES.
Category:: Programmatic
Cause:: XACML Attribute Selector not supported in OES.
Action:: XACML Attribute Selector not supported in OES.

JPS-06128: Unknown Policy/PolicySet Id reference {0}.
Category:: Programmatic
Cause:: Unknown Variable reference.
Action:: Provide an Id Reference of a Policy/PolicySet that exists in the application

JPS-06129: Unknown Variable reference {0}.
Category:: Programmatic
Cause:: Unknown Policy/PolicySet Id reference.
Action:: Provide a variable Reference for which a vadiable definition exists in the policy

JPS-06131: Migration of Audit Store data in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06132: Migration of Audit Store data completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of Audit Store data completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06133: Migration of Credential Store data in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06134: Migration of Credential Store data completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of Credential Store data completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06135: Migration of Credential folder data in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06136: Migration of Credential folder data completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of Credential folder data completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06137: Migration of Application Policies {0} in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06138: Migration of Application Policies {0} completed, Time taken for migration is {1}
Category:: Upgrade
Cause:: Migration of Application Policies {0} completed, Time taken for migration is {1}.
Action:: No actions are required.

JPS-06139: Migration of Global Policies in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06140: Migration of Global Policies completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of System Policies completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06141: Migration of All[Application + Global] policies in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06142: Migration of All[Application + Global] policies completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of All[Application + Global] policies completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06143: Migration of Java Policies in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06144: Migration of Java Policies completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of Java Policies completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06145: Migration of Identity Store data in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06146: Migration of Identity Store data completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of Identity Store data completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06147: Migration of Admin Role Members started
Category:: Upgrade
Cause:
Action:

JPS-06148: Migration of {0} Admin Role Members completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Admin Role Members completed in {1}.
Action:: No actions are required.

JPS-06149: Migration of Grants started
Category:: Upgrade
Cause:
Action:

JPS-06150: Migration of {0} Grants completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Grants completed in {1}.
Action:: No actions are required.

JPS-06151: Migration of Policy Domains started
Category:: Upgrade
Cause:
Action:

JPS-06152: Migration of {0} Policy Domains completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Policy Domains completed in {1}.
Action:: No actions are required.

JPS-06153: Migration of Application Roles started
Category:: Upgrade
Cause:
Action:

JPS-06154: Migration of {0} Application Roles completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Application Roles completed in {1}.
Action:: No actions are required.

JPS-06155: Migration of Resources started
Category:: Upgrade
Cause:
Action:

JPS-06156: Migration of {0} Resources completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Resources completed in {1}.
Action:: No actions are required.

JPS-06157: Migration of Admin Roles started
Category:: Upgrade
Cause:
Action:

JPS-06158: Migration of {0} Admin Roles completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Admin Roles completed in {1}.
Action:: No actions are required.

JPS-06159: Migration of Policies started
Category:: Upgrade
Cause:
Action:

JPS-06160: Migration of {0} Policies completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Policies completed in {1}.
Action:: No actions are required.

JPS-06161: Migration of Resource Types started
Category:: Upgrade
Cause:
Action:

JPS-06162: Migration of {0} Resource Types completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Resource Types completed in {1}.
Action:: No actions are required.

JPS-06163: Migration of Permission Sets started
Category:: Upgrade
Cause:
Action:

JPS-06164: Migration of {0} Permission Sets completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Permission Sets completed in {1}.
Action:: No actions are required.

JPS-06165: Migration of Functions started
Category:: Upgrade
Cause:
Action:

JPS-06166: Migration of {0} Functions completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Functions completed in {1}.
Action:: No actions are required.

JPS-06167: Migration of Attributes started
Category:: Upgrade
Cause:
Action:

JPS-06168: Migration of {0} Attributes completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Attributes completed in {1}.
Action:: No actions are required.

JPS-06169: Migration of Role Policies started
Category:: Upgrade
Cause:
Action:

JPS-06170: Migration of {0} Role Policies completed in {1}
Category:: Upgrade
Cause:: Migration of {0} Role Policies completed in {1}.
Action:: No actions are required.

JPS-06171: Failed to create policy store object, please check the logs.
Category:: Upgrade
Cause:: Failed to create policy store object, please check the logs.
Action:: Please check the logs.

JPS-06172: {0} service not found in default context, skipping upgrade for this service.
Category:: Upgrade
Cause:: {0} service not found in default context of OPSS configuration
Action:: Configure {0} service in default context of OPSS configuration files and run the upgrade again

JPS-06173: Policystore upgrade from {0} to {1} not supported
Category:: Upgrade
Cause:: Policystore upgrade from {0} to {1} not supported
Action:: Policystore must be upgraded to a higher patchset first.

JPS-06174: OPSS data is not backed up as part of upgrade process in LDAP/DB based OPSS Store
Category:: Upgrade
Cause:: OPSS data is not backed up as part of upgrade process in LDAP/DB based OPSS Store
Action:: Back up data manually before running upgrade in LDAP/DB based OPSS Store.

JPS-06175: Migration of CombiningAlgorithms started
Category:: Upgrade
Cause:
Action:

JPS-06176: Migration of {0} CombiningAlgorithms completed in {1}
Category:: Upgrade
Cause:
Action:

JPS-06177: Migration of Policy Rule started
Category:: Upgrade
Cause:
Action:

JPS-06178: Migration of {0} Policy Rule completed in {1}
Category:: Upgrade
Cause:
Action:

JPS-06179: Migration of Policy Set started
Category:: Upgrade
Cause:
Action:

JPS-06180: Migration of {0} Policy Set completed in {1}
Category:: Upgrade
Cause:
Action:

JPS-06181: Migration of Key Store data in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06182: Migration of Key Store data completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of Key Store data completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06183: Migration of Key Store stripe data in progress.....
Category:: Upgrade
Cause:
Action:

JPS-06184: Migration of Key Store stripe data completed, Time taken for migration is {0}
Category:: Upgrade
Cause:: Migration of KeyStore stripe data completed, Time taken for migration is {0}.
Action:: No actions are required.

JPS-06185: More than one properties set references present for policy store service instance in jps-config file {0}
Category:: Requests/Responses
Cause:: More than one property set references present in policy store service instance in jps-config.xml file
Action:: Make sure only one property set references under policy store service instance in jps-config.xml file

JPS-06186: Either bootstrap credstore or key store service instance is not found in bootstrap context
Category:: Requests/Responses
Cause:: Either bootstrap credstore or key store service instance is not found in bootstrap context
Action:: Ensure both bootstrap credstore and keystore service instance reference in bootstrap context is present

JPS-06187: Not able to find file based keystore service instance, while adding keystore service instance to bootstrap context
Category:: Requests/Responses
Cause:: Not able to find file based keystore service instance, while adding keystore service instance to bootstrap context
Action:: Ensure file based keystore service instance reference in jps-config.xml is present

JPS-06188: New Application Policy {0} created during migration
Category:: Upgrade
Cause:: Migration of Application Roles completed in {0}.
Action:: No actions are required.

JPS-06189: Migrate Permission Name = {0}, Exception during modification of permission. Message = {1}.
Category:: Upgrade
Cause:: Migrate Permission Name = {0}, Exception during modification of permission. Message = {1}.
Action:: No actions are required.

JPS-06190: Miagrtion failed in Perm Member : {0}.
Category:: Upgrade
Cause:: Miagrtion failed in Perm Member : {0}
Action:: No actions are required.

JPS-06191: PermissionMigrator Thread {0} failed due to {1}.
Category:: Upgrade
Cause:: PermissionMigrator Thread {0} failed due to {1}.
Action:: No actions are required.

JPS-06192: Cannot get source policy store.
Category:: Configuration
Cause:: While migrating a security store, cannot get source policy store.
Action:: Check and make sure source policy store is configured correctly.

JPS-06193: Cannot get destination policy store.
Category:: Configuration
Cause:: While migrating a security store, cannot get destionation policy store.
Action:: Check and make sure destination policy store is configured correctly.

JPS-06194: There are multiple logic security stores in the db schema : {0}. Please split them before doing upgrade.
Category:: Upgrade
Cause:: Found multiple security stores in the db schema.
Action:: Reassociate each security store to separated db schema.

JPS-06195: Security store is already transformed, so it will not be transformed again.
Category:: Upgrade
Cause:: Security store is already transformed.
Action:: Security store will not be transfromed again.

JPS-06196: Transformation of security store started.
Category:: Upgrade
Cause:: Begin security store transformation.
Action:: No actions are required.

JPS-06197: Transformation of security store completed in {0}.
Category:: Upgrade
Cause:: Finish security store transformation.
Action:: No actions are required.

JPS-06198: OPSS Schema is not upgraded. Current schema version is {0}. Schema version for upgrade is {1}
Category:: Upgrade
Cause:: OPSS Schema is not upgraded.
Action:: Upgrade OPSS Schema first before upgrading Opss Data and Config.

JPS-06199: Source application type dose not match the type of destination application.
Category:: Upgrade
Cause:: Source application type dose not match the destination application type.
Action:: No actions are required.

JPS-06200: Property {0} with value "{1}" is invalid in the meta data property file.
Category:: Security
Cause:: Property {0} with value "{1}" is invalid in the meta data property file.
Action:: Check the meta data property file.

JPS-06201: Property {0} is missing in the meta data property file.
Category:: Security
Cause:: Property {0} is missing in the meta data property file.
Action:: Check the meta data property file.

JPS-06202: Cannot migrate {0} named "{1}", policy object already exists in application policy with different metadata.
Category:: Programmatic
Cause:: {0} named "{1}" already exists in application policy with differnt metadata.
Action:: Check policy store data in source application policy, remove conflict data.

JPS-06500: Alias already exists in the keystore
Category:: Configuration
Cause:: The specified alias name already existed in the keystore.
Action:: Specify a unique alias name.

JPS-06501: Keystore {0} in stripe {1} already exists
Category:: Configuration
Cause:: Keystore with the given name already existed.
Action:: Specify a unique keystore name.

JPS-06502: Failed to read keystore. Reason {0}
Category:: Configuration
Cause:: Could not read the keystore.
Action:: Verify the keystore location and that sufficient permissions are in place.

JPS-06503: Failed to write keystore. Reason {0}
Category:: Configuration
Cause:: Could not read the keystore.
Action:: Verify the keystore location, that sufficient permissions are in place and that sufficient disk space is available.

JPS-06504: Failed to perform cryptographic operation
Category:: Configuration
Cause:: The java provider did not support this cryptographic operation.
Action:: Verify that a provider that supports this algorithm/padding/key is configured.

JPS-06505: Failed to generate certificate request
Category:: Compliance
Cause:
Action:

JPS-06506: Key generation algorithm not supported
Category:: Configuration
Cause:: An unsupported key-pair generation algorithm was used.
Action:: Specify a supported key-pair generation algorithm.

JPS-06507: Root CA import failed.
Category:: Configuration
Cause:: The root CA certificate and/or key file was malformed.
Action:: Verify that the root CA certificate and/or key files is valid.

JPS-06508: Failed to generate CA signed certificate.
Category:: Compliance
Cause:
Action:

JPS-06509: The keystore has been moved or deleted.
Category:: Configuration
Cause:: The keystore did not exist at this location.
Action:: Verify that the location of keystore is correct.

JPS-06510: The keystore location property is not configured, or the configured value {0} is invalid.
Category:: Configuration
Cause:: The keystore location was not specified.
Action:: Check the value of the location attribute.

JPS-06511: Cannot create keystore at {0}.
Category:: Configuration
Cause:: Could not create the keystore.
Action:: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.

JPS-06513: Failed to save keystore. Reason :
Category:: Compliance
Cause:
Action:

JPS-06514: Opening of file based keystore failed. Reason :
Category:: Compliance
Cause:: Keystore could not be opened
Action:: Contact system administrator

JPS-06515: Refreshing of file based keystore failed. Reason {0}
Category:: Compliance
Cause:: Refresh of keystore failed
Action:: Contact system administrator

JPS-06516: Failed to get credential store. Reason {0}
Category:: Compliance
Cause:: Could not get credential store.
Action:: Verify credential store is correctly configured and initialized.

JPS-06517: Failed to create the keystore {0} in stripe {1}.
Category:: Compliance
Cause:
Action:

JPS-06518: Keystore {0} in stripe {1} does not exist.
Category:: Configuration
Cause:: Could not perform this operation since the keystore did not exist.
Action:: Specify an existing keystore name for this operation.

JPS-06519: Failed to get/set credential with map {0} and key {1} in bootstrap credstore. Reason {2}
Category:: Configuration
Cause:: Credential store was not available or permissions were not in place.
Action:: Verify credential store is correctly configured and permissions are granted.

JPS-06520: Failed to encode/decode certificate or public key.
Category:: Compliance
Cause:
Action:

JPS-06521: Invalid admin password, operation not permitted
Category:: Configuration
Cause:: Invalid admin password was specified.
Action:: Specify the correct admin password to perform this operation.

JPS-06522: Failed to roll over keystore master key.
Category:: Compliance
Cause:
Action:

JPS-06523: Failed to reset keystore administrator password.
Category:: Compliance
Cause:
Action:

JPS-06524: Failed to read certificates from keystore.
Category:: Compliance
Cause:
Action:

JPS-06525: Failed to list/renew expiring certificates.
Category:: Compliance
Cause:
Action:

JPS-06526: Failed to list policy violations in keystore.
Category:: Compliance
Cause:
Action:

JPS-06527: Invalid keystore name {0}.
Category:: Configuration
Cause:: Invalid keystore name was specified.
Action:: Specify a keystore name that is not null or empty and contains only alphanumeric characters.

JPS-06528: Invalid alias value {0}.
Category:: Configuration
Cause:: Invalid alias value was specified.
Action:: Specify an alias value that is not null or empty and contains only alphanumeric characters.

JPS-06529: Passwords must not be null or empty.
Category:: Configuration
Cause:: Password was specified as null or empty.
Action:: Specify a non null or non empty password for a keystore protected by password.

JPS-06530: Invalid stripe value {0}
Category:: Compliance
Cause:
Action:

JPS-06531: Operation failed, keystore password does not match
Category:: Compliance
Cause:
Action:

JPS-06532: Failed to delete the keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06533: Algorithm {0} not supported
Category:: Configuration
Cause:: The algorithm was not supported by keystore.
Action:: Check the list of supported algorithms and specify one of them.

JPS-06534: Keystore master key roll-over failed.
Category:: Compliance
Cause:
Action:

JPS-06535: Failed to generate secret key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06536: Failed to import secret key for keystore {0}
Category:: Compliance
Cause:
Action:

JPS-06537: Failed to change password for keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06538: Cannot set password for trusted certificate entry.
Category:: Compliance
Cause:
Action:

JPS-06539: Operation failed, key password does not match
Category:: Compliance
Cause:
Action:

JPS-06540: Failed to change password for key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06541: Invalid keystore entry type {0}
Category:: Configuration
Cause:: The keystore entry type was invalid for this operation.
Action:: Check the list of supported keystore entry types from documentation.

JPS-06542: Failed to list aliases for keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06543: Invalid Distinguished Name {0}
Category:: Compliance
Cause:
Action:

JPS-06544: Failed to generate key pair for alias {0} keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06545: The expected keystore entry with alias "{0}" either does not exist or is not of the specified keystore entry type for keystore "{1}" in stripe "{2}".
Category:: Configuration
Cause:: The alias value either did not exist or did not point to the specified keystore entry type.
Action:: Specify a valid alias value that points to the specified keystore entry type.

JPS-06546: Failed to get secret key with alias {0}
Category:: Compliance
Cause:
Action:

JPS-06547: Failed to get certificate(s) with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06548: Failed to export certificate request for key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06549: No corresponding key pair found for this certificate
Category:: Configuration
Cause:: The alias value did not point to the matching key pair for this certificate
Action:: Specify a valid alias value that points to a key pair whose public key matches that of the certificate.

JPS-06550: Failed to parse the certificate chain
Category:: Compliance
Cause:
Action:

JPS-06551: Failed to import the key store entry with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06552: Failed to delete the key store entry with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06553: Cannot perform this operation on domain trust store
Category:: Configuration
Cause:: The operation was not supported for domain trust store.
Action:: Check product documentation to see the operations permitted on domain trust store.

JPS-06554: Cannot perform this operation on demo CA keystore
Category:: Compliance
Cause:
Action:

JPS-06555: Mismatch between the values of key aliases and key passwords
Category:: Configuration
Cause:: There should be equal number of entries for key aliases and key passwords
Action:: Ensure that key aliases and key passwords are equal in number.

JPS-06556: Keystore to be imported is not valid
Category:: Configuration
Cause:: The keystore file being imported was either empty or of invalid format.
Action:: Ensure that the keystore being imported is of valid format.

JPS-06557: Mismatch between the values of CSF maps and keys
Category:: Configuration
Cause:: There should be equal number of entries for CSF maps and CSF keys
Action:: Ensure that CSF maps and keys are either both null, or are equal in number.

JPS-06558: Mismatch between the values of key alias/password and CSF map/key
Category:: Configuration
Cause:: There should be equal number of entries for key alias/password and CSF map/key
Action:: Ensure that key alias/password and CSF map/key are equal in number.

JPS-06559: Keystore type {0} not supported
Category:: Configuration
Cause:: The keystore type was not supported.
Action:: Check the list of supported keystore types and specify one of them.

JPS-06560: Failed to import the keystore {0} in stripe {1}. Reason {2}
Category:: Compliance
Cause:
Action:

JPS-06561: Failed to export the keystore {0} in stripe {1}. Reason {2}.
Category:: Compliance
Cause:
Action:

JPS-06562: Failed to load the keystore.
Category:: Compliance
Cause:
Action:

JPS-06563: Failed to save the keystore.
Category:: Compliance
Cause:
Action:

JPS-06564: Method not implemented
Category:: Compliance
Cause:
Action:

JPS-06565: Invalid keystore protection parameter
Category:: Configuration
Cause:: The specified keystore protection type was not supported.
Action:: Ensure that the keystore protection type is a password.

JPS-06566: No trusted certificate found with this alias
Category:: Configuration
Cause:: The specified alias did not refer to a trusted certificate.
Action:: Ensure that the alias refers to a trusted certificate in the keystore.

JPS-06567: Unsupported key type
Category:: Configuration
Cause:: The key type was not supported.
Action:: Ensure that key is either private key or secret key.

JPS-06568: Insufficient permissions for this operation. Reason {0}
Category:: Compliance
Cause:
Action:

JPS-06569: Keystore {0} in app stripe {1} does not exist
Category:: Compliance
Cause:
Action:

JPS-06570: Failed to set keystore policy
Category:: Compliance
Cause:
Action:

JPS-06571: Failed to delete keystore policy
Category:: Compliance
Cause:
Action:

JPS-06572: Null policy name/value not allowed
Category:: Compliance
Cause:
Action:

JPS-06573: Failed to list keystore policies
Category:: Compliance
Cause:
Action:

JPS-06574: Invalid key parameters
Category:: Compliance
Cause:
Action:

JPS-06575: Certificate import failed as the public key in the certificate did not match the one in the keystore.
Category:: Configuration
Cause:: The public key in the certificate does not match the one in the keystore.
Action:: Ensure that the certificate is imported into the alias used for generating certificate request.

JPS-06576: Failed to read {0} with alias {1}.
Category:: Configuration
Cause:: Failed to read {0} with alias {1}.
Action:: Contact the administrator.

JPS-06577: Failed to create private key {0}.
Category:: Configuration
Cause:: Failed to create private key {0}.
Action:: Contact the administrator.

JPS-06578: Cert with alias {0} was invalid.
Category:: Configuration
Cause:: Cert with alias {0} was invalid.
Action:: Contact the administrator.

JPS-06579: Failed to read keystore data.
Category:: Configuration
Cause:: Failed to read keystore data.
Action:: Contact the administrator.

JPS-06580: Failed to check keystore integrity.
Category:: Configuration
Cause:: Failed to check keystore integrity.
Action:: Contact the administrator.

JPS-06581: Failed to load certificates from the keystore.
Category:: Configuration
Cause:: Failed to load certificates from the keystore.
Action:: Contact the administrator.

JPS-06582: Failed to get trusted certs.
Category:: Configuration
Cause:: Failed to get trusted certs
Action:: Contact the administrator.

JPS-06583: Failed to check if audit is enabled.
Category:: Configuration
Cause:: Keystore audit events logging was not enabled.
Action:: Check the audit configuration to ensure auditing enabled.

JPS-06584: Failed to log audit record.
Category:: Configuration
Cause:: Keystore audit event logging failed.
Action:: Contact the administrator.

JPS-06585: Created keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06586: Deleted keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06587: Successfully listed keystores in stripe {0}
Category:: Compliance
Cause:
Action:

JPS-06588: Failed to list keystores in stripe {0}
Category:: Compliance
Cause:
Action:

JPS-06589: Successfully got the handle to keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06590: Failed to get the handle to keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06591: Successfully changed the password of keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06592: Successfully generated key pair with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06593: Successfully generated secret key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06594: Successfully changed password for key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06595: Successfully listed aliases for keystore {0} in stripe {1}
Category:: Compliance
Cause:
Action:

JPS-06596: Successfully listed properties for secret key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06597: Failed to list properties for secret key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06598: Successfully got certificate(s) with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06599: Successfully exported certificate request for key with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06600: Failed to export certificate(s) with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06601: Successfully exported certificate(s) with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06602: Successfully imported the key store entry with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06603: Successfully deleted the key store entry with alias {0} for keystore {1} in stripe {2}
Category:: Compliance
Cause:
Action:

JPS-06604: Successfully imported the keystore {0} in stripe {1}.
Category:: Compliance
Cause:
Action:

JPS-06605: Successfully exported the keystore {0} in stripe {1}.
Category:: Compliance
Cause:
Action:

JPS-06606: Could not create keystore service instance. Reason {0}
Category:: Compliance
Cause:: Could not create keystore service instance
Action:: Contact system administrator

JPS-06607: The keystore service DN {0} is missing in the store; the target DN must be pre-configured.
Category:: Requests/Responses
Cause:: The expected keystore DN {0} was missing.
Action:: Configure this DN during the bootstrap process.

JPS-06608: The farm DN property {0} is invalid or not defined.
Category:: Requests/Responses
Cause:: The farm name property {0} was invalid or not defined.
Action:: Check the configuration of this property.

JPS-06609: The keystore is not initialized.
Category:: Configuration
Cause:: The keystore was not loaded.
Action:: Load the keystore before trying this operation.

JPS-06610: Keystore {0} did not exist.
Category:: Compliance
Cause:
Action:

JPS-06611: The keystore service instance {0} was not initialized.
Category:: Configuration
Cause:: Keystore service was not completely initialized.
Action:: Wait until data source is available and try again later.

JPS-06612: The properties for keystore {0} in stripe {1} were read successfully
Category:: Compliance
Cause:
Action:

JPS-06613: Supported key sizes could not be determined for this algorithm.
Category:: Compliance
Cause:
Action:

JPS-06614: Operation not supported - unable to delete key store {0} in stripe {1}.
Category:: Configuration
Cause:: Deletion of domain trust store or the demo CA key store was not permitted.
Action:: Choose a different key store.

JPS-06615: Operation not supported - unable to delete alias {0} in key store {1} in stripe {2}.
Category:: Configuration
Cause:: Deletion of demo CA key was not permitted.
Action:: Choose a different key alias.

JPS-06616: Missing certificate chain.
Category:: Configuration
Cause:: Certificate chain was null.
Action:: Specify a valid certificate chain.

JPS-06617: Successfully retrieved the attribute {0} from the keystore {1} in stripe {2}.
Category:: Compliance
Cause:
Action:

JPS-06618: Failed to retrieve attribute {0} from the keystore {1} in stripe {2}.
Category:: Compliance
Cause:
Action:

JPS-06619: Key store file keystores.xml integrity check failed. Location: {0}
Category:: Configuration
Cause:: File keystore.xml has been manually edited.
Action:: Restore the keystore file to the last working backup and try again.

JPS-06620: Key store file integrity checker initialization failed. Reason {0}
Category:: Configuration
Cause:: Problem using the bootstrap credential store service.
Action:: Check the bootstrap credential store configuration.

JPS-06621: Cannot change password of a permission protected key store
Category:: Compliance
Cause:
Action:

JPS-06622: Cannot change key password of a permission protected key store
Category:: Compliance
Cause:
Action:

JPS-06623: Invalid KSS URI: {0}
Category:: Compliance
Cause:
Action:

JPS-06624: Cannot synchronize centralized key store(s) from stripe {0} to bootstrap key store(s). Reason {1}
Category:: Configuration
Cause:
Action:

JPS-06625: Invalid component type {0}
Category:: Configuration
Cause:
Action:

JPS-06626: Could not get bootstrap key store service. Reason {0}
Category:: Compliance
Cause:: Could not get bootstrap key store service.
Action:: Verify key store service is correctly configured and initialized.

JPS-06627: Invalid keystore provider type. Value {0}
Category:: Configuration
Cause:: Value of keystore.provider.type is invalid.
Action:: Assign a valid value to keystore.provider.type.

JPS-06628: Key alias {0} corresponds to neither a key nor a trusted certificate in the imported keystore.
Category:: Configuration
Cause:: Given key alias corresponds to neither a key nor a trusted certificate.
Action:: Given key alias should correspond to either a key or a trusted certificate.

JPS-06629: No alias specified so skipping import/export
Category:: Configuration
Cause:: Key aliases should not be null or empty string.
Action:: Ensure that key aliases are neither null nor empty string.

JPS-06630: Import of entry with alias: {0} into appStripe:{1} keystore:{2} skipped as it already exists in the keystore.
Category:: Configuration
Cause:: Alias already exists in the keystore. Alias overwriting while importing not supported.
Action:: Alias to be imported shouldn't pre-exist in the key store.

JPS-06631: Certificate import failed as the minimum number of certificates expected is {0}
Category:: Configuration
Cause:: K required were not given.
Action:: Ensure that minimum number of certificates are imported.

JPS-06632: Invalid key store attribute {0}
Category:: Compliance
Cause:
Action:

JPS-06633: Cannot synchronize component key store(s) under stripe {0} into corresponding wallets. Reason {1}
Category:: Configuration
Cause:
Action:

JPS-06634: One or more of keystores inside application stripe {0} are not permission protected.
Category:: Compliance
Cause:: One or more of keystores inside the application stripe are not permission protected.
Action:: Ensure that all keystores in the application stripe are permission protected.

JPS-06635: Either or both of stripe name {0} and keystore format {1} is null or empty string.
Category:: Compliance
Cause:: Either or both of stripe name and keystore format is null or empty string.
Action:: Ensure that stripe name and keystore format are both non-empty string.

JPS-06636: Application stripe {0} does not exist in keystore.
Category:: Compliance
Cause:: Given application stripe doesn't exist in keystore.
Action:: Provide name of an application stripe that is already existing in keystore.

JPS-06637: Trusted certificate with Subject DN {0} is missing from trust store of keystore.
Category:: Compliance
Cause:: A trusted certificate is missing from trust store of keystore.
Action:: Ensure that the trusted certificate is present in trust store of keystore.

JPS-06638: KeyStore Entry required were not given.
Category:: Configuration
Cause:: KeyStore Entry required were not given.
Action:: Provide KeyStore Entry as input.

JPS-06639: The following aliases were encountered in the keystore: {0}
Category:: Compliance
Cause:
Action:

JPS-06640: Empty alias specified for importing wallet keystore, so skipping import
Category:: Configuration
Cause:: Key aliases of wallet keystore to import should not be empty string.
Action:: Ensure that key aliases of wallet keystore to import are not empty string.

JPS-06641: Invalid keySize format : {0}
Category:: Compliance
Cause:: Cannot set key entry for non-existent stripe and keystore
Action:: This operation is not supported

JPS-06642: Can not determine the JAVA/JRE home,so could not find the cacerts file.
Category:: Compliance
Cause:: Neither environnment variable JAVA_HOME nor system property java.home is specified.
Action:: Ensure that either environnment variable JAVA_HOME or system property java.home is specified.

JPS-06643: JDK cacerts file {0} in use.
Category:: Compliance
Cause:
Action:

JPS-06644: Failed to import JDK cacerts to system/publiccacerts.
Category:: Compliance
Cause:: Importing JDK CA cert failed.
Action:: check log for more details.

JPS-06645: JDK cacerts {0} does not exist.
Category:: Compliance
Cause:: JDK cacerts file {0} does not exist.
Action:: Check the location of JDK cacerts files.

JPS-06646: Private or Secret key found in Trust Store
Category:: Compliance
Cause:
Action:

JPS-06647: Aggregation of two trust stores failed
Category:: Compliance
Cause:: There is a private or secret key entry in the truststore
Action:: Remove the private or secret key entries from the truststore

JPS-06655: The keysize for algorithm {0} can not be less than {1}, but {2} is being used .
Category:: Compliance
Cause:: Keysize is not allowed for specific algorithm
Action:: Use a higher key size for this algorithm.

JPS-06656: Using algorithm {0} is not permitted.
Category:: Compliance
Cause:: The algorithm is not allowed.
Action:: Use a stronger algorithm.

JPS-06657: The format of Subject Alternative Name certificate extension is invalid: {0}.
Category:: Requests/Responses
Cause:: The format of Subject Alternative Name certificate extension is invalid.
Action:: Correct the format of Subject Alternative Name certificate extension.

JPS-06658: Invalid secret key value.
Category:: Configuration
Cause:: Invalid secet key.
Action:: Check the value of secret key.

JPS-06659: Invalid private key value.
Category:: Configuration
Cause:: Invalid private key.
Action:: Check the value of private key.

JPS-06660: Invalid certificate value.
Category:: Configuration
Cause:: Invalid certificate.
Action:: Check the value of certificate.

JPS-06661: Invalid private key or certificate.
Category:: Configuration
Cause:: Invalid private key or certificate.
Action:: Check the value of private key and certificate.

JPS-06662: Import secret key success.
Category:: Compliance
Cause:
Action:

JPS-06663: Import private key and certificate success.
Category:: Compliance
Cause:
Action:

JPS-06664: Import secret key failure.
Category:: Compliance
Cause:
Action:

JPS-06665: Import private key and certificate failure.
Category:: Compliance
Cause:
Action:

JPS-06666: Invalid key password value.
Category:: Configuration
Cause:: Invalid key password.
Action:: Check the value of key password.

JPS-07000: Provide a valid jps configuration file.
Category:: Security
Cause:: The jps configuration file was invalid.
Action:: Refer to the log files for details and correct the error.

JPS-07001: Provide a valid application name.
Category:: Security
Cause:: Application ID was invalid.
Action:: Refer to the log files for details and correct the error.

JPS-07002: Provide a valid jazn-data file. .
Category:: Security
Cause:: The jazn-data file was invalid.
Action:: Refer to the log files for details and correct the error.

JPS-07003: Provide a valid folder name.
Category:: Security
Cause:: The patch delta folder was invalid.
Action:: Provide a valid folder for generating patch delta files.

JPS-07004: ApplicationPolicy object is null/empty.
Category:: Security
Cause:: ApplicationPolicy object was null
Action:: Make sure to create a not null ApplicationPolicy object

JPS-07005: The "{0} " jazn data file does not exists.
Category:: Security
Cause:: Jazn data file does not exists.
Action:: Make sure to provide an existing jazn-data file.

JPS-07006: "{0}" Not a folder. Please provide a valid folder.
Category:: Security
Cause:: Not a folder.
Action:: Make sure to provide a valid folder.

JPS-07007: "{0}" folder does not exists
Category:: Security
Cause:: The folder does not exists.
Action:: Make sure to provide an existing folder.

JPS-07008: The {0} jps configuration file does not exist.
Category:: Security
Cause:: The jps configuration file does not exists.
Action:: Make sure to provide an existing jps configuration file.

JPS-07009: The "{0}" folder for generating patch delta files does not exist.
Category:: Security
Cause:: The folder to generate the patch delta files does not exists.
Action:: Make sure to provide an existing folder.

JPS-07010: The AppRole "{0}" cannot be created. Cause {1} .
Category:: Security
Cause:: The approle could not be created.
Action:: Refer to the log files for details and correct the error.

JPS-07011: The AppRole object is null while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Ensure to provide a valid AppRole Object.

JPS-07012: The ResourceType object is null while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Enusre to provide a valid ResourceType Object.

JPS-07013: The AppRole list is null/empty while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Ensure to provide a valid AppRole List.

JPS-07014: The Resource object is null while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Ensure to pass a valid Resource object.

JPS-07015: The PermissionSet object is null while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Ensure to provide a valid PermissionSet object.

JPS-07016: The Association object is null while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Ensure to provide a valid Association object.

JPS-07017: Internal Error.
Category:: Security
Cause:: That was an internal error.
Action:: Refer to the log files for details and correct the error.

JPS-07018: Application Role: "{0}" cannot be added. Reason {1} .
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07019: Permission Set: "{0}" cannot be added. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07020: Resource: "{0}" cannot be added. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07021: Resource Type "{0}" cannot be added. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07022: Member: name "{0}" ,class "{1}" cannot be granted an application role: "{2}". Reason {3}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07023: Resource Actions: name "{0}", actions "{1}" cannot be added in permission set: "{2}". Reason {3}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07024: Permission: "{0}" cannot be granted to grantee "{1}". Reason {2}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07025: Permission set: "{0}" cannot be granted to grantee "{1}". Reason {2}
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07026: Application Role: "{0}" cannot be modified. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07027: Permission Set: "{0}" cannot be modified. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07028: Resource: "{0}" cannot be modified. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07029: Resource Type: "{0}" cannot be modified. Reason {1}
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07030: Application Role: "{0}" cannot be deleted. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07031: Permission Set: "{0}" cannot be deleted. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07032: Resource: "{0}" cannot be deleted. Reason {1}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07033: Resource Type: "{0}" cannot be deleted. Reason {1}
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07034: Member: name "{0}", class "{1}" cannot be revoked from application role: "{2}". reason {3}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07035: Resource Actions: name "{0}", actions "{1}" cannot be deleted from permission set: "{2}". Reason {3}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07036: Permission: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07037: Permission set: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07038: Additions cannot be read. Reason {0}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07039: Deletions cannot be read. Reason {0}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07040: Modifications cannot be read. Reason {0}.
Category:: Security
Cause:: Policy store reported an error.
Action:: Check the Reason and fix the problem.

JPS-07041: The argument "{0}" is not applicable for phase "{1}".
Category:: Security
Cause:: Extra argument provided
Action:: Please provide only relavent parameters

JPS-07042: Illegal value provided for argument "{0}".
Category:: Security
Cause:: Illegal value provided for an argument
Action:: Please provide a legal value for the argument.

JPS-07043: Cannot find application policy {0}.
Category:: Security
Cause:: Could not find application policy {0}.
Action:: Check the application name passed.

JPS-07044: Cannot retrieve newline application policy.
Category:: Security
Cause:: Could not retrieve newline application policy.
Action:: Check the application name passed.

JPS-07045: Cannot retrieve baseline application policy.
Category:: Security
Cause:: Could not retrieve baseline application policy.
Action:: Check the application name passed.

JPS-07046: Cannot retrieve customer application policy.
Category:: Security
Cause:: Could not retrieve customer application policy.
Action:: Check the application name passed.

JPS-07047: This artifact is newly added in patch version.
Category:: Security
Cause:: Policy store doesn't suport metadata
Action:: Update policy store

JPS-07055: Policy entry is null.
Category:: Security
Cause:: {0} Policy entry is null.
Action:: No actions are required.

JPS-07056: Addition conflicts initialization failed.
Category:: Security
Cause:: Internal Error occured when attempting to load Addition Conflicts from Patch Delta.
Action:: Check the logs.

JPS-07057: Modification conflicts initialization failed.
Category:: Security
Cause:: Internal Error occured when attempting to load Modification Conflicts from Patch Delta.
Action:: Check the logs.

JPS-07058: Deletion conflicts initialization failed.
Category:: Security
Cause:: Internal Error occured when attempting to load Deletion Conflicts from Patch Delta.
Action:: Check the logs.

JPS-07059: Conflicting addition changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.
Category:: Security
Cause:: Addition conflicts are not resolved.
Action:: Resolve addition conflicts.

JPS-07060: Conflicting modification changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.
Category:: Security
Cause:: Modification conflicts are not resolved.
Action:: Resolve modification conflicts.

JPS-07061: Conflicting deletion changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.
Category:: Security
Cause:: Deletion conflicts are not resolved.
Action:: Resolve deletion conflicts.

JPS-07062: Additions Writer initialization failed for resolve.
Category:: Security
Cause:: Additions Writer initialization failed for resolve.
Action:: Check the logs.

JPS-07063: Deletions Writer initialization failed for resolve.
Category:: Security
Cause:: Additions Writer initialization failed for resolve.
Action:: Check the logs.

JPS-07064: Modifications Writer initialization failed for resolve.
Category:: Security
Cause:: Modification Writer initialization failed for resolve.
Action:: Check the logs.

JPS-07065: Dependency artifact {0} is not resolved for artifact {1}.
Category:: Security
Cause:: Dependency artifact {0} is not resolved for artifact {1}.
Action:: Check the resolutions.

JPS-07066: Dependency artifact {0} resolution is not valid for artifact {1}.
Category:: Security
Cause:: Dependency artifact {0} resolution is not valid for artifact {1}.
Action:: Check the resolutions.

JPS-07067: Artifact not resolved {0}.
Category:: Security
Cause:: Artifact not resolved {0}.
Action:: Check the resolutions.

JPS-07069: Deletion of member {0} of permission set {1} renders the permission set empty.
Category:: Security
Cause:: Deletion of member will render Permission set empty
Action:: Check the resolutions.

JPS-07070: The argument {0} is not passed
Category:: Security
Cause:: The required argument is not passed.
Action:: Provide the required argument.

JPS-07071: Deletion Changes in the patch have been identified. Applying the changes will permanently delete policy store artifacts. Silent Apply process halted. Review the changes and Apply the patch.
Category:: Security
Cause:: Addition Safe changes and Modification Safe changes have been applied.However, Deletion conflicts are not resolved.
Action:: Resolve deletion conflicts.

JPS-07077: Cannot generate report. Reason {0}
Category:: Security
Cause:: Report generation failed.
Action:: Check the logs.

JPS-07078: Report file {0} path is invalid.
Category:: Security
Cause:: Report file specified is not a valid file path.
Action:: Specify a valid file path.

JPS-07079: Report file {0} cannot be created in the given directory.
Category:: Security
Cause:: The directory doesn't have write permission.
Action:: Specify a directory which has write permission.

JPS-07080: Report file {0} already exists.
Category:: Security
Cause:: Report file exists.
Action:: Specify a non existing file.

JPS-07081: Could not find policystore in "{0}" jps context in production config.
Category:: Security
Cause:: Could not find policystore in {0} jps context in production config.
Action:: Provide a service instance for policystore in the {0} jps context in production config.

JPS-07082: Loading base policy store complete in {0}.
Category:: Security
Cause:: Loading base policy store complete in {0}.
Action:: No actions are required.

JPS-07083: Initializing Application Policy Comparator complete in {0}.
Category:: Security
Cause:: Initializing Application Policy Comparator complete in {0}.
Action:: No actions are required.

JPS-07084: Loading new policy store complete in {0}.
Category:: Security
Cause:: Loading new policy store complete in {0}.
Action:: No actions are required.

JPS-07085: Oracle Delta calculation complete in {0}.
Category:: Security
Cause:: Oracle Delta calculation complete in {0}.
Action:: No actions are required.

JPS-07086: Production application policy store object created in {0}.
Category:: Security
Cause:: Production application policy store object created in {0}.
Action:: No actions are required.

JPS-07087: Customer delta created in {0}.
Category:: Security
Cause:: Customer delta created in {0}.
Action:: No actions are required.

JPS-07088: Patch delta created in {0}.
Category:: Security
Cause:: Patch delta created in {0}.
Action:: No actions are required.

JPS-07089: Report File created in {0}.
Category:: Security
Cause:: Report file created in {0}.
Action:: No actions are required.

JPS-07090: Customer delta files created in {0}.
Category:: Security
Cause:: Customer delta files created in {0}.
Action:: No actions are required.

JPS-07093: The Role category object is null while persisting to Addition Safe Changes.
Category:: Security
Cause:: The required parameter was null.
Action:: Enusre to provide a valid RoleCategory Object.

JPS-07101: Beginning to apply additions...
Category:: Security
Cause:: Beginning to apply additions...
Action:: No actions are required.

JPS-07102: Additions applied in {0}
Category:: Security
Cause:: Additions applied in {0}.
Action:: No actions are required.

JPS-07103: Beginning to apply modifications...
Category:: Security
Cause:: Beginning to apply modifications...
Action:: No actions are required.

JPS-07104: Modifications applied in {0}
Category:: Security
Cause:: Modifications applied in {0}.
Action:: No actions are required.

JPS-07105: Beginning to apply deletions...
Category:: Security
Cause:: Beginning to apply deletions...
Action:: No actions are required.

JPS-07106: Deletions applied in {0}
Category:: Security
Cause:: Deletions applied in {0}.
Action:: No actions are required.

JPS-07107: {0} Application roles added.
Category:: Security
Cause:: {0} Application roles added.
Action:: No actions are required.

JPS-07108: {0} Role categories added.
Category:: Security
Cause:: {0} Role categories added.
Action:: No actions are required.

JPS-07109: {0} Resource type entries added.
Category:: Security
Cause:: {0} Resource type entries added.
Action:: No actions are required.

JPS-07110: {0} Resource entries added.
Category:: Security
Cause:: {0} Resource entries added.
Action:: No actions are required.

JPS-07111: {0} Permission set entries added.
Category:: Security
Cause:: {0} Permission set entries added.
Action:: No actions are required.

JPS-07112: {0} Application role membership entries added.
Category:: Security
Cause:: {0} Application role membership entries added.
Action:: No actions are required.

JPS-07113: {0} Application role categories entries added.
Category:: Security
Cause:: {0} Application role categories entries added.
Action:: No actions are required.

JPS-07114: {0} Resources to permission sets added.
Category:: Security
Cause:: {0} Resources to permission set entries added.
Action:: No actions are required.

JPS-07115: {0} Permission set membership entries added.
Category:: Security
Cause:: {0} Permission set membership entries added.
Action:: No actions are required.

JPS-07116: {0} Grantee to permission set entries added.
Category:: Security
Cause:: {0} Grantee to permission set entries added.
Action:: No actions are required.

JPS-07117: {0} Grantee to permission membership entries added.
Category:: Security
Cause:: {0} Grantee to permission membership entries added.
Action:: No actions are required.

JPS-07118: {0} Application roles modified.
Category:: Security
Cause:: {0} Application roles modified.
Action:: No actions are required.

JPS-07119: {0} Role categories modified.
Category:: Security
Cause:: {0} Role categories modified.
Action:: No actions are required.

JPS-07120: {0} Resource type entries modified.
Category:: Security
Cause:: {0} Resource type entries modified.
Action:: No actions are required.

JPS-07121: {0} Resource entries modified.
Category:: Security
Cause:: {0} Resource entries modified.
Action:: No actions are required.

JPS-07122: {0} Permission set entries modified.
Category:: Security
Cause:: {0} Permission set entries modified.
Action:: No actions are required.

JPS-07123: {0} Resources to permission sets added.
Category:: Security
Cause:: {0} Resources to permission set entries modified.
Action:: No actions are required.

JPS-07124: {0} Grantee to permission membership entries modified.
Category:: Security
Cause:: {0} Grantee to permission membership entries modified.
Action:: No actions are required.

JPS-07125: Dissociated {0} members from application roles.
Category:: Security
Cause:: Deassociated {0} members and application roles.
Action:: No actions are required.

JPS-07126: Dissociated {0} categories from application roles.
Category:: Security
Cause:: Deassociated {0} categories and application roles.
Action:: No actions are required.

JPS-07127: Dissociated {0} resources from permission sets.
Category:: Security
Cause:: Deassociated {0} resources and permission sets.
Action:: No actions are required.

JPS-07128: Revoked {0} permission sets from grantees.
Category:: Security
Cause:: Revoked {0} permission sets from grantees.
Action:: No actions are required.

JPS-07129: Revoked {0} permissions from grantees.
Category:: Security
Cause:: Revoked {0} permissions from grantees.
Action:: No actions are required.

JPS-07130: {0} Application roles deleted.
Category:: Security
Cause:: {0} Application roles deleted.
Action:: No actions are required.

JPS-07131: {0} Role categories deleted.
Category:: Security
Cause:: {0} Role categories deleted.
Action:: No actions are required.

JPS-07132: {0} Permission set entries deleted.
Category:: Security
Cause:: {0} Permission set entries deleted.
Action:: No actions are required.

JPS-07133: {0} Resource entries deleted.
Category:: Security
Cause:: {0} Resource entries deleted.
Action:: No actions are required.

JPS-07134: {0} Resource type entries deleted.
Category:: Security
Cause:: {0} Resource type entries deleted.
Action:: No actions are required.

JPS-07135: Progress - Apply Additions ----------------------- {0}% Done
Category:: Security
Cause:: Progress...Apply additions
Action:: No actions are required.

JPS-07136: Progress - Apply Modifications -------------------- {0}% Done
Category:: Security
Cause:: Progress...Apply modifications
Action:: No actions are required.

JPS-07137: Progress - Apply Deletions ----------------------- {0}% Done
Category:: Security
Cause:: Progress...Apply deletions
Action:: No actions are required.

JPS-07138: Dissociated of members from application roles (skipped, not applicable).
Category:: Security
Cause:: Dissociation of members from application roles (skipped, not applicable)
Action:: No actions are required.

JPS-07139: Dissociation of categories from application roles (skipped, not applicable)
Category:: Security
Cause:: Disassociation of categories from application roles (skipped, not applicable)
Action:: No actions are required.

JPS-07140: Dissociation of resources from permission sets (skipped, not applicable).
Category:: Security
Cause:: Disassociation of resources from permission sets (skipped, not applicable)
Action:: No actions are required.

JPS-07141: Revoke of permission sets from grantees (skipped, not applicable).
Category:: Security
Cause:: Revoke of permission sets from grantees (skipped, not applicable)
Action:: No actions are required.

JPS-07142: Revoke of permissions from grantees (skipped, not applicable).
Category:: Security
Cause:: Revoke of permissions from grantees (skipped, not applicable)
Action:: No actions are required.

JPS-07143: Application roles deletion (skipped, not applicable).
Category:: Security
Cause:: Deletion of application roles (skipped, not applicable)
Action:: No actions are required.

JPS-07144: Role categories deletion (skipped, not applicable).
Category:: Security
Cause:: Deletion of role categories (skipped, not applicable)
Action:: No actions are required.

JPS-07145: Permission set entries deletion (skipped, not applicable).
Category:: Security
Cause:: Deletion of permission sets (skipped, not applicable)
Action:: No actions are required.

JPS-07146: Resource entries deletion (skipped, not applicable)
Category:: Security
Cause:: Deletion of resources (skipped, not applicable)
Action:: No actions are required.

JPS-07147: Resource type entries deletion (skipped, not applicable).
Category:: Security
Cause:: Deletion of resource types (skipped, not applicable)
Action:: No actions are required.

JPS-07148: Deletions not applicable when the silent flag is on.
Category:: Security
Cause:: Deletions not applicable when the silent flag is enabled
Action:: No actions are required.

JPS-07150: You can set only one of the two flags - {0} or {1} but not both.
Category:: Security
Cause:: Dual flags have been set. This is not permitted
Action:: Set only one of the two flags - {0} or {1}

JPS-07151: role member {0} of application role: {1} not found.
Category:: Security
Cause:: role member {0} of application role: {1} not found
Action:: Add back role member: {0} or run patching analysis again

JPS-07152: Name collisions have been identified. The patch process halted. Eliminate the collisions by renaming or removing artifacts in production store. Please find artifacts which have name collision between production store and patch version in file {0}.
Category:: Security
Cause:: Name collisions exist.
Action:: Eliminate the name collisions by renaming or removing the policy artifacts in production store.

JPS-07156: {0} Policy rule entries were added.
Category:: Security
Cause:: {0} Policy rule entries added.
Action:: No actions are required.

JPS-07157: {0} Policy entries were added.
Category:: Security
Cause:: {0} Policy entries added.
Action:: No actions are required.

JPS-07158: {0} Policy to permission set entries added.
Category:: Security
Cause:: {0} Policy to permission set entries added.
Action:: No actions are required.

JPS-07159: {0} Policy to policy rule entries were added.
Category:: Security
Cause:: {0} Policy to policy rule entries added.
Action:: No actions are required.

JPS-07160: {0} Policy to grantee entries added.
Category:: Security
Cause:: {0} Policy to grantee entries added.
Action:: No actions are required.

JPS-07161: {0} Policies entries were modified.
Category:: Security
Cause:: {0} Policies entries modified.
Action:: No actions are required.

JPS-07162: {0} Policy rules entries were modified.
Category:: Security
Cause:: {0} Policy rules entries modified.
Action:: No actions are required.

JPS-07163: {0} Policy rules were deleted from policies.
Category:: Security
Cause:: Deleted {0} policy rules from policies.
Action:: No actions are required.

JPS-07164: {0} Principals were deleted from policy.
Category:: Security
Cause:: Deleted {0} principals from policy.
Action:: No actions are required.

JPS-07165: {0} Permission Sets were deleted from policy.
Category:: Security
Cause:: Deleted {0} Permission Set from policy.
Action:: No actions are required.

JPS-07166: {0} Policy entries were deleted.
Category:: Security
Cause:: {0} Policy entries deleted.
Action:: No actions are required.

JPS-07167: {0} Policy rule entries were deleted.
Category:: Security
Cause:: {0} Policy rule entries deleted.
Action:: No actions are required.

JPS-07168: Policy rule entry is null.
Category:: Security
Cause:: {0} Policy rule entry is null.
Action:: No actions are required.

JPS-07169: Delta between patch jazn-data and production policystore was written to report in {0}.
Category:: Security
Cause:: Delta between patch jazn-data and production policystore was written to report in {0}.
Action:: No actions are required.

JPS-07170: Delta between patch jazn-data and production policystore was calculated in {0}.
Category:: Security
Cause:: Delta between patch jazn-data and production policystore was calculated in {0}.
Action:: No actions are required.

JPS-07171: Privilege changes of user or group report between baseline jazn-data and production policystore was created in {0}.
Category:: Security
Cause:: User or group's privilege changes report between baseline jazn-data and production policystore was created in {0}.
Action:: No actions are required.

JPS-07172: Delta between production and baseline jazn-data was validated in {0}.
Category:: Security
Cause:: Policy customization between production and baseline jazn-data was validated in {0}.
Action:: No actions are required.

JPS-07173: Enterprise role privilege changes between production and baseline jazn-data was validated in {0}.
Category:: Security
Cause:: Enterprise user or role privilege changes between production and baseline jazn-data was validated in {0}.
Action:: No actions are required.

JPS-07174: Enterprise user or role privilege validation failed for record: {0}.
Category:: Security
Cause:: Enterprise user or role privilege validation failed for record
Action:: Check the usergroup-privilege-validate-result file for more details

JPS-07175: Policy change validation failed for record: {0}.
Category:: Security
Cause:: Policy change validation failed for record
Action:: Check the policy-validate-result file for more details

JPS-07176: Patch jazn data file {0} will be ignored since this is forceTag mod.
Category:: Security
Cause:: Patch jazn data file {0} will be ignored since this is forceTag mod.
Action:: No action

JPS-07177: Patch application policy name {0} will be ignored since this is forceTag mod.
Category:: Security
Cause:: Patch application policy name {0} will be ignored since this is forceTag mod.
Action:: No action

JPS-07178: Patch delta folder {0} will be ignored since this is forceTag mod.
Category:: Security
Cause:: Patch delta folder {0} will be ignored since this is forceTag mod.
Action:: No action

JPS-07179: Tagging {0} {1} completed in {2}.
Category:: Security
Cause:: Tagging {0} {1} completed in {2}.
Action:: No action

JPS-07180: usergroup-privilege report file {0} not found.
Category:: Security
Cause:: usergroup-privilege report file {0} not found
Action:: Please check the phase used in patching policy store, this file is generated in report phase.

JPS-07181: Metadata support is required on application {0} when there is no baseline file.
Category:: Security
Cause:: Metadata support is required on application {0} when there is no baseline file.
Action:: Please make sure the application policy is supporting meta data when there is no baseline file.

JPS-07182: Report phase requires base line file provisioned.
Category:: Security
Cause:: Report phase requires baseline file.
Action:: Please make sure there is baseline file provisioned during report phase

JPS-07500: Trust protocol {0} is not supported.
Category:: Security
Cause:: Requested trust protocol is not supported
Action:: Provide correct trust protocol

JPS-07501: Token context is invalid.
Category:: Security
Cause:: Token context object is empty or does not contain required parameters
Action:: Check token context object contains required parameter

JPS-07502: Trust Service token provider {0} is not found.
Category:: Security
Cause:: Token provider not configured in the jps-config.xml file
Action:: Check jps-config.xml file and verify that requested token provider is correctly configured

JPS-07503: Trust Service token provider class name {0}.
Category:: Security
Cause:: Token provider class loading
Action:: No action required

JPS-07504: Trust Service Keystore initialization failed.
Category:: Security
Cause:: Keystore is is missing or not configured correctly
Action:: Check the keystore and ensure that necessary certificates and keys are present

JPS-07505: Trust service provider protocol {0}
Category:: Security
Cause:: Trust Service provider protocol information
Action:: No action required

JPS-07506: Token context creation failed.
Category:: Security
Cause:: Incorrct protocol or associated provider configuration.
Action:: Check protocol and associated provider configuration

JPS-07507: Token issue operation
Category:: Security
Cause:: Trust service token issue opertion.
Action:: No action required

JPS-07508: Token issue operation failed.
Category:: Security
Cause:: Trust service token issue opertion failed.
Action:: Check provider configuration

JPS-07509: Invalid token operation
Category:: Security
Cause:: Invalid Trust Service token opertion.
Action:: Check invoked operation name

JPS-07510: Token validate operation.
Category:: Security
Cause:: Trust Service validate token opertion.
Action:: No action required

JPS-07511: Validate operation failed.
Category:: Security
Cause:: Trust service token validate opertion failed.
Action:: Check provider configuration

JPS-07512: Missing token issuer identity.
Category:: Security
Cause:: Token issuer identity missing.
Action:: Provide token issuer identity

JPS-07513: Invalid subject confirmation method.
Category:: Security
Cause:: Invalid subject confirmation method.
Action:: Provide correct subject confirmation method

JPS-07514: Token audience restriction condition check failed.
Category:: Security
Cause:: Invalid token audience condition.
Action:: Check the audience condition

JPS-07515: Token signature validation failed.
Category:: Security
Cause:: Invalid token signature.
Action:: Check token integrity and verify signature using correct certificate

JPS-07516: Invalid token.
Category:: Security
Cause:: Invalid token.
Action:: Check token integrity.

JPS-07517: Input token is not an instance of GenericToken class.
Category:: Security
Cause:: Input token is not an instance of GenericToken class.
Action:: Check the token object class

JPS-07518: Input token is not an instance of UsernameToken class
Category:: Security
Cause:: Input token is not an instance of UsernameToken class.
Action:: Check the token object class

JPS-07519: Setting subject conformation method failed.
Category:: Security
Cause:: Invalid token object.
Action:: Check the token object

JPS-07520: Token signing failed.
Category:: Security
Cause:: Token signing key is unavailable.
Action:: Check the keystore and verify that signing key is present

JPS-07521: Token signature is not available.
Category:: Security
Cause:: Unsigned token.
Action:: No action required.

JPS-07522: Token is not valid yet {0}
Category:: Security
Cause:: Token is not valid yet.
Action:: Check the token validity start date.

JPS-07523: Token has expired {0}
Category:: Security
Cause:: Token has expired.
Action:: Check the token validity end date.

JPS-07524: Certificate is unavailable {0}
Category:: Security
Cause:: Certificate is not available.
Action:: Check the keystore and ensure that the certificate is present.

JPS-07525: Private key is unavailable
Category:: Security
Cause:: Private key is not available.
Action:: Check the keystore and ensure that the private key is present.

JPS-07526: Initializing provider
Category:: Security
Cause:: Provider is initiliazing.
Action:: None

JPS-07527: Shutting down provider
Category:: Security
Cause:: Provider is shutting down.
Action:: None

JPS-07528: Received unknown token type {0}
Category:: Security
Cause:: Received token type is unknown.
Action:: Check the provided token.

JPS-07529: Received unknown token class {0}
Category:: Security
Cause:: Token class is unknown.
Action:: Check the token class.

JPS-07530: Invalid token type or token not found
Category:: Security
Cause:: Invalid token authentication type specified.
Action:: Check the token authentication type.

JPS-07531: Input token is not an instance of {0}
Category:: Security
Cause:: Specified insance is not correct.
Action:: Check the instance type validity.

JPS-07532: Instance of {0} is invalid
Category:: Security
Cause:: Specified instance is invalid.
Action:: Check the specified instance and ensure that it is correct

JPS-07533: Received empty token byte array
Category:: Security
Cause:: Given token is empty.
Action:: Check the token content and ensure that it is not empty.

JPS-07534: Trust service configuration is not valid
Category:: Security
Cause:: Invalid configuration parameters.
Action:: Check the configuration parameters.

JPS-07535: Using {0} Trust service configuration
Category:: Security
Cause:: Configuration type used by Trust Service
Action:: None

JPS-07536: Token credential missing
Category:: Security
Cause:: Token signing or validation credential missing.
Action:: Provide correct credential.

JPS-07537: Token signature missing
Category:: Security
Cause:: Token signature missing.
Action:: Check the token for integrity.

JPS-07538: The input token is not specified
Category:: Security
Cause:: Input token not provided.
Action:: Check if the token has been provided.

JPS-07539: Token signing method is not specified
Category:: Security
Cause:: Token signing algorithm parameter missing.
Action:: Check the token signing algorithm parameter.

JPS-07540: Token signing method is invalid
Category:: Security
Cause:: Token signing algorithm parameter invalid
Action:: Check the specified token signing algorithm.

JPS-07541: Token signing private key is not specified
Category:: Security
Cause:: Token signing private key missing.
Action:: Check the token signing private key parameter.

JPS-07542: Token signing certificate is not specified
Category:: Security
Cause:: Token signing certificate missing.
Action:: Check the token signing certificate parameter.

JPS-07543: Token signing credential is not specified
Category:: Security
Cause:: Token signing credential missing.
Action:: Check the token signing credential parameter.

JPS-07544: The specified token type is invalid
Category:: Security
Cause:: The token type is not supported.
Action:: Check the token type parameter.

JPS-07545: Invalid TokenContext class
Category:: Security
Cause:: Internal Error. The correct TokenContext class is not created.
Action:: Provide the correct TokenProvider class in trust configurations.

JPS-07546: Token cannot be issued for virtual or anonymous user
Category:: Security
Cause:: Trust token cannot be issued for anonymous or virtual users
Action:: Ensure usage of Trust service is limited to users present in configured identity store.

JPS-07600: Application policy for stripe name {0} not found. Nothing to undeploy
Category:: Security
Cause:: No associated application policies
Action:: Check application policy setup or contact system administrator

JPS-07601: Complete staging offline deployment for application {0} in {1}
Category:: Security
Cause:: Complete staging offline deployment for application {0} in {1}
Action:: No action required

JPS-07602: Removal of application policy failed. Reason: {0}.
Category:: Security
Cause:: Exception in removing application policy
Action:: Check application policy setup or contact system administrator

JPS-07603: Cannot purge changelog. Reason {0}.
Category:: Security
Cause:: Purge changelog failed.
Action:: Check policystore configuration.

JPS-07604: Wrong policy combining algorithm name {0} is used.
Category:: Security
Cause:: wrong policy combining algorithm name was used
Action:: Check combining algorithm name being used

JPS-07605: Unsupported policy combining algorithm name {0} is used.
Category:: Security
Cause:: Unsupported policy combining algorithm name was used
Action:: Check combining algorithm name being used

JPS-07606: Cannot clean applications. Reason {0}.
Category:: Security
Cause:: Clean applications failed.
Action:: Refer to the log files for details and correct the error.

JPS-07607: {0} is used in source, but it is not supported by destination policy store.
Category:: Security
Cause:: Source contains policy artifacts that is not supported by destination policy store
Action:: Make sure source only contain policy artifacts which are compatible with destination policy store

JPS-07608: ERROR:not allowed to modify seed policy store {0}.
Category:: Security
Cause:: ERROR:not allowed to modify seed policy store {0}.
Action:: Refer to the log files for details and correct the error.

JPS-07609: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric, underscore, colon, dot and hyphen.
Category:: Security
Cause:: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric, underscore, colon, dot and hyphen.
Action:: Ensure attribute name is of correct datatype.

JPS-07610: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric, underscore, colon, dot and hyphen.
Category:: Security
Cause:: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric, underscore, colon, dot and hyphen.
Action:: Ensure function name is of correct datatype.

JPS-08000: Subject object {0} is not supported.
Category:: Security
Cause:: Specified Object type is not supported by the provider for Subject.
Action:: Check the document for supported object types.

JPS-08001: Action object {0} is not supported.
Category:: Security
Cause:: Specified Object type is not supported by the provider for Action.
Action:: Check the document for supported object types.

JPS-08002: Resource object {0} is not supported.
Category:: Security
Cause:: Specified Object type is not supported by the provider for Resource.
Action:: Check the document for supported object types.

JPS-08003: Environment object {0} is not supported.
Category:: Security
Cause:: Specified Object type is not supported by the provider for Environment.
Action:: Check the document for supported object types.

JPS-08004: Invalid resource string: {0}.
Category:: Security
Cause:: The resource string is invalid.
Action:: Check the document for the resource string format.

JPS-08005: Subject cannot be null.
Category:: Security
Cause:: The subject is null.
Action:: Use a valid subject.

JPS-08006: Action cannot be null.
Category:: Security
Cause:: The action is null.
Action:: Use a valid action.

JPS-08007: Resource cannot be null.
Category:: Security
Cause:: The resource is null.
Action:: Use a valid resource.

JPS-08008: Action list cannot be null or empty.
Category:: Security
Cause:: The action list is null or empty.
Action:: Use a valid action list.

JPS-08009: Resource list cannot be null or empty.
Category:: Security
Cause:: The resource list is null or empty.
Action:: Use a valid resource list.

JPS-08010: The size of action list and resource list is different.
Category:: Security
Cause:: The size of action list and resource list is different.
Action:: The size of action list should be identical to the size of resource list.

JPS-08011: Subject object {0} is not a valid subject on platform {1}.
Category:: Security
Cause:: The subject object is not a valid subject on current platform.
Action:: Use a valid subject.

JPS-08012: Scope cannot be null or empty.
Category:: Security
Cause:: Scope is null or empty.
Action:: Use a valid scope.

JPS-08013: Query Type cannot be null.
Category:: Security
Cause:: Query Type is null.
Action:: Use a valid Query Type.

JPS-08014: Invalid scope string: {0}.
Category:: Security
Cause:: The scope string is invalid.
Action:: Check the document for the scope string format.

JPS-08015: Invalid search scope string: {0}.
Category:: Security
Cause:: The search scope in scope string is invalid.
Action:: Check the document for the scope string format.

JPS-08016: An error has occurred while processing the PepResponse result.
Category:: Security
Cause:: An error has occurred while processing the PepResponse results.
Action:: Check the policy setup and client code.

JPS-08017: Invalid resource string: {0}. Please provide a fully qualified resource string.
Category:: Security
Cause:: Fully qualified resource string is required.
Action:: Please specify application ID, resource type and resource name.

JPS-08018: The configured policy provider {0} does not implement AzPolicy interface.
Category:: Security
Cause:: The configured policy provider does not implement AzPolicy interface.
Action:: You must configure policy provider that implements AzPolicy interface, e.g. by calling Policy.setPolicy().

JPS-08019: Requested operation is not supported.
Category:: Security
Cause:: Requested operation is not supported.
Action:: Do not invoke unsupported operation.

JPS-08020: The authorization service instance is invalid.
Category:: Security
Cause:: The authorization service instance is invalid.
Action:: Check the service instance and ensure that is a supported authorization service instance.

JPS-08021: The input configuration parameter is invalid.
Category:: Security
Cause:: The input configuration parameter is invalid.
Action:: Check the configuration parameter validity.

JPS-08022: Incorrect authorization service instance type.
Category:: Security
Cause:: Incorrect authorization service instance type.
Action:: Check the authorization service instance type.

JPS-08023: The environment parameter is missing.
Category:: Security
Cause:: The environment paramater is missing.
Action:: Check the environment paramater.

JPS-08024: Policy context parameter is missing.
Category:: Security
Cause:: Policy context parameter is missing.
Action:: Check the policy context paramater.

JPS-08025: Session context parameter is missing.
Category:: Security
Cause:: Session context parameter is missing.
Action:: Check the session paramater.

JPS-08026: Database connection parameter is missing.
Category:: Security
Cause:: Database connection parameter is missing or not a right type.
Action:: Check the database connection paramater.

JPS-08027: Security predicate parameter is missing.
Category:: Security
Cause:: Security predicate parameter is missing.
Action:: Check the security predicate paramater.

JPS-08028: Cannot find appName attribute in resource collection.
Category:: Security
Cause:: Can't find appName attribute in resource collection.
Action:: Add appName attribute to resource collection.

JPS-08029: Privilege parameter is missing or not a right type
Category:: Security
Cause:: Privilege parameter is missing or not a right type.
Action:: Check the privilege paramater.

JPS-08030: DB object parameter is missing or not a right type.
Category:: Security
Cause:: DB object parameter is missing or not a right type.
Action:: Check the DB object paramater.

JPS-08031: Client env parameter is not a right type.
Category:: Security
Cause:: Client env parameter is not a right type.
Action:: Check the client env paramater.

JPS-08032: Client env parameter has unsupported value.
Category:: Security
Cause:: Client env parameter has unsupported value.
Action:: Check the client env paramater.

JPS-08033: Check privilege mode parameter has unsupported value.
Category:: Security
Cause:: Check privilege mode parameter has unsupported value.
Action:: Check the Check privilege paramater.

JPS-08034: Value of parameter {0} should be type {1}, but has a wrong type {2}.
Category:: Security
Cause:: Invalid parameter type
Action:: Check the paramater.

JPS-08035: Type of RAS parameter value is not supported.
Category:: Security
Cause:: Type of RAS parameter value is not supported.
Action:: Do not use unsupported type for RAS parameter value.

JPS-08036: Invalid data type in Subject collection, it only accepts RuntimeAttribute.
Category:: Security
Cause:: Invalid data type in Subject collection, it only accepts RuntimeAttribute.
Action:: Use RuntimeAttribute in Subject collection.

JPS-08037: Invalid data type in Action collection, it only accepts RuntimeAttribute.
Category:: Security
Cause:: Invalid data type in Action collection, it only accepts RuntimeAttribute.
Action:: Use RuntimeAttribute in Action collection.

JPS-08038: Invalid data type in Resource collection, it only accepts RuntimeAttribute.
Category:: Security
Cause:: Invalid data type in Resource collection, it only accepts RuntimeAttribute.
Action:: Use RuntimeAttribute in Resource collection.

JPS-08500: Component audit definition {0} already exists.
Category:: Security
Cause:: Component audit definition {0} already exists.
Action:: Check given component type.

JPS-08501: Failed to create component audit definition {0}. Reason: {1}.
Category:: Security
Cause:: Failed to create component audit definition {0}. Reason: {1}.
Action:: See error message.

JPS-08502: Failed to search database mapping table for component {0}. Reason: {1}.
Category:: Security
Cause:: Failed to search database mapping table for component {0}. Reason: {1}.
Action:: See error message.

JPS-08503: Cannot search audit definition for component {0}. Reason: {1}.
Category:: Security
Cause:: Cannot search audit definition for component {0}. Reason: {1}.
Action:: See error message.

JPS-08504: Failed to search generic attribute groups. Reason: {0}.
Category:: Security
Cause:: Failed to search generic attribute groups. Reason: {0}.
Action:: See error message.

JPS-08505: Failed to create database mapping table for component {0}. Reason: {1}.
Category:: Security
Cause:: Failed to create database mapping table for component {0}. Reason: {1}.
Action:: See error message.

JPS-08506: Failed to create filter config for component {0}. Reason: {1}.
Category:: Security
Cause:: Failed to create filter config for component {0}. Reason: {1}.
Action:: See error message.

JPS-08507: Component audit definition {0} does not exist.
Category:: Security
Cause:: Component audit definition {0} does not exist.
Action:: Check given component type.

JPS-08508: Failed to search filter config for component {0}. Reason: {1}.
Category:: Security
Cause:: Failed to search filter config for component {0}. Reason: {1}.
Action:: See error message.

JPS-08509: Failed to update filter config for component {0}. Reason: {1}.
Category:: Security
Cause:: Failed to update filter config for component {0}. Reason: {1}.
Action:: See error message.

JPS-08510: The expected audit store DN {0} was missing.
Category:: Security
Cause:: The expected audit store DN {0} was missing.
Action:: Configure this DN during the bootstrap process.

JPS-08511: Audit store was not fully initialized until data source is available.
Category:: Security
Cause:: Audit store was not fully initialized until data source is available.
Action:: Wait and retry later.

JPS-08512: Failed to retrieve value. Reason: {0}.
Category:: Security
Cause:: Failed to retrieve value. Reason: {0}.
Action:: See error message.

JPS-08513: Failed to search component types. Reason: {0}.
Category:: Security
Cause:: Failed to search component types. Reason: {0}.
Action:: See error message.

JPS-08514: Failed to search system XLF. Reason: {0}.
Category:: Security
Cause:: Failed to search system XLF. Reason: {0}.
Action:: See error message.

JPS-08515: Failed to search XLF for component {0}. Reason: {1}.
Category:: Security
Cause:: Failed to search XLF for component {0}. Reason: {1}.
Action:: See error message.

JPS-08516: Failed to search system definition. Reason: {0}.
Category:: Security
Cause:: Failed to search system definition. Reason: {0}.
Action:: See error message.

JPS-08517: System audit definition already exists.
Category:: Security
Cause:: System audit definition already exists.
Action:: See error message.

JPS-08518: Failed to create system audit definition. Reason: {0}.
Category:: Security
Cause:: Failed to create system audit definition. Reason: {0}.
Action:: See error message.

JPS-08519: Error in creating filter tree. Reason: {0}.
Category:: Security
Cause:: Error in creating filter tree. Reason: {0}.
Action:: See error message.

JPS-08520: Audit definition {0} is invalid.
Category:: Security
Cause:: Audit definition {0} is invalid.
Action:: See error message.

JPS-08521: Attribute mapping table {0} for component type {1} is invalid.
Category:: Security
Cause:: Attribute mapping table {0} for component type {1} is invalid.
Action:: See error message.

JPS-08522: Filter config {0} for component type {1} is invalid.
Category:: Security
Cause:: Filter config {0} for component type {1} is invalid.
Action:: See error message.

JPS-08523: Component type value {0} is invalid.
Category:: Security
Cause:: Component type value {0} is invalid.
Action:: See error message.

JPS-08524: System definition {0} is invalid.
Category:: Security
Cause:: System definition {0} is invalid.
Action:: See error message.

JPS-08525: Audit definition for component type {0} not found.
Category:: Security
Cause:: Audit definition for component type {0} not found.
Action:: See error message.

JPS-08526: XLF for component type {0} not found.
Category:: Security
Cause:: XLF for component type {0} not found.
Action:: See error message.

JPS-08527: Attribute mapping table for component type {0} not found.
Category:: Security
Cause:: Attribute mapping table for component type {0} not found.
Action:: See error message.

JPS-08528: Filter config for component type {0} not found.
Category:: Security
Cause:: Filter config for component type {0} not found.
Action:: See error message.

JPS-08529: Generic attribute groups not found.
Category:: Security
Cause:: Generic attribute groups not found.
Action:: See error message.

JPS-08530: Failed to search audit definition in audit store. Reason: {0}.
Category:: Configuration
Cause:: Failed to search audit definition in audit store. Reason: {0}.
Action:: Ensure that the audit store configuration for audit service are correct in jps-config.xml.

JPS-08531: Failed to create audit metadata in audit store. Reason: {0}.
Category:: Configuration
Cause:: Failed to create audit metadata in audit store. Reason: {0}.
Action:: Ensure that the audit store configuration for audit service are correct in jps-config.xml.

JPS-08532: Audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08533: Component XLF for audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Component XLF for audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08534: Generic attribute groups in destination store do not match those in source store.
Category:: Configuration
Cause:: Generic attribute groups in destination store does not match the one in source store.
Action:: See error message.

JPS-08535: Attribute group "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Attribute group "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08536: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08537: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08538: Event definitions for audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Event definitions for audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08539: Event category "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Event category "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08540: Level list for audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Level list for audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08541: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.
Category:: Configuration
Cause:: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.
Action:: See error message.

JPS-08542: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.
Category:: Configuration
Cause:: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.
Action:: See error message.

JPS-08543: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.
Category:: Configuration
Cause:: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.
Action:: See error message.

JPS-08544: Failed to remove component definition "{0}". Reason: {1}.
Category:: Security
Cause:: Failed to remove component definition "{0}". Reason: {1}.
Action:: See error message.

JPS-08545: Failed to update component definition "{0}". Reason: {1}.
Category:: Security
Cause:: Failed to update component definition "{0}". Reason: {1}.
Action:: See error message.

JPS-08546: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.
Category:: Configuration
Cause:: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.
Action:: See error message.

JPS-08547: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.
Category:: Configuration
Cause:: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.
Action:: See error message.

JPS-08548: Cannot register to audit service for component "{0}".
Category:: Security
Cause:: Cannot register component definition "{0}" to audit service. Reason {1}.
Action:: See error message.

JPS-08549: Audit registration service not available.
Category:: Security
Cause:: Audit registration service not available.
Action:: See error message.

JPS-08550: Audit loader startup failed. Cause: "{0}".
Category:: Security
Cause:: Audit loader startup failed.
Action:: See error message.

JPS-08551: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".
Category:: Security
Cause:: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".
Action:: See error message.

JPS-08552: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".
Category:: Security
Cause:: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".
Action:: See error message.

JPS-08553: Failed to load opss_audit_registration.xml. Reason "{0}".
Category:: Security
Cause:: Failed to load opss_audit_registration.xml, Reason "{0}".
Action:: See error message.

JPS-08554: Failed to register Component type "{0}" due to malformed version number in event definition.
Category:: Security
Cause:: Failed to register Component type "{0}" due to malformed version number in event definition.
Action:: See error message.

JPS-08555: During provisioning operations, subscriptions will not be accepted
Category:: Security
Cause:
Action:

JPS-08556: Component type value null is invalid.
Category:: Security
Cause:: Component type value null is invalid.
Action:: Use the appropriate componentType while doing registration of component to AuditStore

JPS-08557: Component events definition file is invalid. Reason - "{0}".
Category:: Security
Cause:: Component events definition file is invalid. Reason - "{0}".
Action:: Correct the events definition file based on reason

JPS-08558: Failed to rollback audit registration failure for component "{0}" , Reason "{1}".
Category:: Security
Cause:: Failed to rollback audit registration failure for component "{0}" , Reason "{1}".
Action:: See error message.

JPS-08559: No matching system event definition for EventRef "{0}" , regarded as a custom Event.
Category:: Security
Cause:: No matching system event definition for EventRef "{0}" , regarded as a custom Event.
Action:: See error message.

JPS-09000: Resource type {0} already in use for {1}.
Category:: Security
Cause:: Resource type was already in use.
Action:: Use a different resource type name.

JPS-09001: Resource matching class name is missing. A subtype must not have its own matching algorithm.
Category:: Security
Cause:: Resource matching class name was missing.
Action:: A subtype must not have its own matching algorithm.

JPS-09002: The parameter {0} of type {1} does not exist.
Category:: Security
Cause:: This parameter did not exist.
Action:: See the log files for more details.

JPS-09003: For the parameter {0} more than expected values found for the Application name:{1}, Policy Domain:{2}, Query Parameter:{3}, Actual results: {4}
Category:: Security
Cause:: More then expected values for given parameter found.
Action:: See the log files for more details.

JPS-09004: For type {0} the modification is not allowed for {1}.
Category:: Security
Cause:: Modify operation was not allowed.
Action:: See the log files for more details.

JPS-09005: For the parameter {0} the given value {1} is invalid.
Category:: Security
Cause:: The value for the given parameter was invalid.
Action:: Provide the valid value for the given paramter.

JPS-09006: Resource {0} already in use for {1}.
Category:: Security
Cause:: Resource was already in use.
Action:: Use a different resource name.

JPS-09007: RoleCategory {0} cannot be deleted
Category:: Security
Cause:: The role category is referenced by one or more application roles.
Action:: Modify the application role(s) definition that reference this role category by removing the role category for the application role.

JPS-09008: Application policy for application {0} does not exist.
Category:: Security
Cause:: Application policy did not exist.
Action:: The application policy must exist. Check the policy store.

JPS-09009: Only limited set of properties are supported for resource action search. See the documentation for more details.
Category:: Security
Cause:: The property user to search resource action was invalid.
Action:: Only limited set of properties are supported for resource action search. See the documentation for more details.

JPS-09010: Cannot create permission set {0} with a non existent resource type {1}.
Category:: Security
Cause:: Permission set could not be created without resource type.
Action:: Resource type must be pre-defined to create the permission set.

JPS-09011: Cannot create permission set {0} with a non existent resource {1}.
Category:: Security
Cause:: Permission set could not be created without resource.
Action:: Resource must be pre-defined to create the permission set.

JPS-09012: Search value cannot be null. It can be null only if MATCHER is ANY.
Category:: Security
Cause:: Search value was null. It could be null only if MATCHER is ANY.
Action:: Verify the search value for the given query.

JPS-09013: This application roles {0} does not belong to this application {1}.
Category:: Security
Cause:: This application role did not belong to this application.
Action:: Ensure this application role belongs to this application.

JPS-09014: The application role {0} cannot have null name or unique name for the application {1}.
Category:: Security
Cause:: The name or unique name of this application role was null or invalid.
Action:: Ensure the name or unique name of this application role is valid.

JPS-09015: Application role does not exist in current application.
Category:: Security
Cause:: Application role was not found in current application.
Action:: Ensure the application role belongs to this application.

JPS-09016: Unknown policy store service type {0}.
Category:: Configuration
Cause:: Unknown policy store service type {0}.
Action:: Correct the policy store configuration.

JPS-09017: Policy entry {0} cannot be found.
Category:: Configuration
Cause:: Policy entry {0} cannot be found.
Action:: Correct the policy entry.

JPS-09018: Policy object {0} cannot be found.
Category:: Configuration
Cause:: Policy object {0} cannot be found.
Action:: Correct the policy object.

JPS-09019: {0} could not be cached.
Category:: Configuration
Cause:: {0} did not be cached.
Action:: Ensure the Resource has valid actions.

JPS-09020: Principal entry class "{0}", name "{1}" cannot be created.
Category:: Configuration
Cause:: Principal entry class "{0}", name "{1}" cannot be created.
Action:: Ensure that the principal entry class is correct and entry value is valid.

JPS-09021: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.
Category:: Configuration
Cause:: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.
Action:: Ensure that the permission entry class is correct and entry value is valid.

JPS-09022: Resource entry type "{0}", resource "{1}" cannot be created.
Category:: Configuration
Cause:: Resource entry type "{0}", resource "{1}" cannot be created.
Action:: Ensure that the resource entry class is correct and entry value is valid.

JPS-09023: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.
Category:: Configuration
Cause:: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.
Action:: Ensure that the resource type entry class is correct and entry value is valid.

JPS-09024: Resource action entry type "{0}", name "{1}" cannot be created.
Category:: Configuration
Cause:: Resource action entry type "{0}", name "{1}" cannot be created.
Action:: Ensure that the resource action entry class is correct and entry value is valid.

JPS-09025: Permission set entry (name: "{0}", actions: "{1}") cannot be created.
Category:: Configuration
Cause:: Permissionset entry name "{0}", actions "{1}" cannot be created.
Action:: Ensure that the permissionset entry class is correct and entry value is valid.

JPS-09026: Role category entry name "{0}" cannot be created.
Category:: Configuration
Cause:: Role category entry name "{0}" cannot be created.
Action:: Ensure that the role category entry class is correct and entry value is valid.

JPS-09027: Grantee DN was missing for principal {0}.
Category:: Configuration
Cause:: Grantee DN was missing for principal {0}.
Action:: Check principal value.

JPS-09028: Failed to get permission for principal {0}. Reason: {1}.
Category:: Configuration
Cause:: Failed to get permission for principal {0}. Reason: {1}.
Action:: Check principal value.

JPS-09029: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.
Category:: Configuration
Cause:: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.
Action:: Check log for details.

JPS-09030: Code signer data {0} cannot be migrated due to limitation in the destination policy store.
Category:: Configuration
Cause:: Code signer data {0} cannot be migrated due to limitation in the destination policy store.
Action:: Check log for details.

JPS-09031: Failed to read java policies for Application: {0}. Reason: {1}.
Category:: Configuration
Cause:: Failed to read java policies for Application: {0}. Reason: {1}.
Action:: Check log for details.

JPS-09032: Only one of permission array {0} and permission entry list {1} can be null or non-null.
Category:: Configuration
Cause:: Only one of permission array {0} and permission entry list {1} can be null/non-null.
Action:: Ensure one of permission array or permission entry list values is null or non-null.

JPS-09033: No grantee found for grantee entry {0}.
Category:: Configuration
Cause:: No grantee found for grantee entry {0}.
Action:: Ensure the grantee exist in the policy store.

JPS-09034: Modification on single-value attribute {0} but contains multiple attribute values.
Category:: Configuration
Cause:: Modification on single-value attribute {0} but contains multiple attribute values.
Action:: Check modification details.

JPS-09035: Failed to create DN for {0}. Reason: {1}.
Category:: Configuration
Cause:: Failed to create DN for {0}. Reason: {1}.
Action:: Check DN name.

JPS-09036: Failed to read JACC policy {0}. Reason: {0}.
Category:: Configuration
Cause:: Failed to read JACC policy {0}. Reason: {0}.
Action:: Check LDAP configuration to resolve this error.

JPS-09037: No application DN found for name {0} under farm {1}.
Category:: Configuration
Cause:: No application DN found for name {0} under farm {1}.
Action:: Check DN name.

JPS-09038: Resource type {0} does not exist for resource {1}
Category:: Security
Cause:: This resource type does not exist.
Action:: Provide a valid resource type.

JPS-09041: Expression component provided for RuleExpressionEntry must not be null.
Category:: Programmatic
Cause:: Expression component provided for RuleExpressionEntry must not be null.
Action:: Check value of ExpressionComponent.

JPS-09042: Invalid expression component provided to RuleExpressionEntry.
Category:: Programmatic
Cause:: Invalid expression component provided to RuleExpressionEntry.
Action:: Check value of ExpressionComponent.

JPS-09043: Function entry for an expression must not be null.
Category:: Programmatic
Cause:: Function entry for an expression must not be null.
Action:: Check value of FunctionEntry.

JPS-09044: Expression component of type {0} not supported.
Category:: Programmatic
Cause:: Expression component of type {0} not supported.
Action:: Check value of ExpressionComponent.

JPS-09045: Minimum number of input parameters must be less than maximum number of input parameters
Category:: Programmatic
Cause:: Minimum number of input parameters must be less than maximum number of input parameters
Action:: Check parameters to constructor of VarArgsInfo.

JPS-09046: The Matcher {0} in the search query is invalid
Category:: Programmatic
Cause:: The matcher in the search query is invalid
Action:: Provide a valid Search Matcher in the query.

JPS-09047: The Property {0} in the search query is invalid
Category:: Programmatic
Cause:: The search property in the query is invalid
Action:: Provide a valid Search property in the query.

JPS-09048: The search value is invalid
Category:: Programmatic
Cause:: The search value in the query is invalid
Action:: Provide a valid Search value in the query.

JPS-09049: Null value provided for {0}
Category:: Programmatic
Cause:: Invalid value provided to DataType object.
Action:: Provide a non-null value

JPS-09050: Host name {0} is invalid for DNS name
Category:: Programmatic
Cause:: Invalid value provided as DNS host.
Action:: Provide a valid value

JPS-09051: Invalid data. Lower DNS port {0} is greater than higher port {1}.
Category:: Programmatic
Cause:: Lower port is greater than upper range.
Action:: Provide a valid value

JPS-09052: Unknown format, can not parse valid date from string {0}.
Category:: Programmatic
Cause:: Unknown format for date string.
Action:: Provide a valid value

JPS-09053: Invalid string {0} for fractional seconds.
Category:: Programmatic
Cause:: Invalid string for fractional seconds.
Action:: Provide a valid value

JPS-09054: Invalid string {0} for hour offset.
Category:: Programmatic
Cause:: Invalid string for hour offset.
Action:: Provide a valid value

JPS-09055: Invalid string {0} for minute offset.
Category:: Programmatic
Cause:: Invalid string for minute offset.
Action:: Provide a valid value

JPS-09056: Negative value {0} not allowed.
Category:: Programmatic
Cause:: Negative value not aloowed.
Action:: Provide a valid value

JPS-09057: Invalid string {0} for dayTimeDuration. Cannot parse.
Category:: Programmatic
Cause:: Invalid string format for dayTimeDuration
Action:: Provide a valid value

JPS-09058: Invalid string {0} for RFC822 name.
Category:: Programmatic
Cause:: RFC822Name cannot end with @.
Action:: Provide a valid value

JPS-09059: Invalid string {0} for RFC822 domain.
Category:: Programmatic
Cause:: Invvalid RFC822 domain name.
Action:: Provide a valid value

JPS-09060: Invalid string {0} for yearMonthDuration.
Category:: Programmatic
Cause:: Invalid string format for yearMonthDuration
Action:: Provide a valid value

JPS-09061: Invalid string {0} for OpssTime, must be a number.
Category:: Programmatic
Cause:: Invalid string for time field, must be a number.
Action:: Provide a valid value

JPS-09062: Invalid value {0}, must be between lower range {1} and upper range {2}.
Category:: Programmatic
Cause:: Value provided for data type not in required range.
Action:: Provide a valid value

JPS-09063: Invalid inputted Hex Binary value {0}.
Category:: Programmatic
Cause:: Invalid value provided for OpssHexBinary data type.
Action:: Provide a valid value

JPS-09064: Invalid extension manager, cannot be used to find constraint attributes and functions.
Category:: Programmatic
Cause:: Internal error: invalid extension manager cannot be used to find constraint attributes or functions.
Action:: Provide correct function.

JPS-09400: Attribute key cannot be null.
Category:: Requests/Responses
Cause:: Attribute key was null.
Action:: Provide a valid attribute key.

JPS-09401: Name of attribute key cannot be null.
Category:: Requests/Responses
Cause:: Name of attribute key was null.
Action:: Provide a valid name of attribute key.

JPS-09402: Attribute service instance not found in the default context.
Category:: Configuration
Cause:: Attribute service instance not found in the default JpsContext.
Action:: Configure an attribute service instance in the default JpsContext.

JPS-09500: Template name is not initialized, please follow the document for method execution order
Category:: Requests/Responses
Cause:: Template name is not initialized.
Action:: Ensure that execution order is followed as per document

JPS-09501: Either template name or target store or target key or credential object is passed as NULL, {0} is not inserted
Category:: Requests/Responses
Cause:: Either template name or target store or target key or credential objcet is passed as NULL, corresponding credential/key object is not inserted
Action:: Ensure that all the parameters are passed to insert credential/key object

JPS-09502: Error occurred when initializing security artifacts. Reason {0}
Category:: Requests/Responses
Cause:: Security Artifact initialization failed
Action:: Check the logs

JPS-09503: Error occurred when cleaning the environment, please clean it manually
Category:: Requests/Responses
Cause:: Error occurred while cleaning the environment
Action:: Please clean it manually

JPS-09504: Error occurred when processing credentials for template {0}. Reason {1}
Category:: Requests/Responses
Cause:: Failed while processing credentials
Action:: Check the logs

JPS-09505: Error occurred when processing keys for template {0}. Reason {1}.
Category:: Requests/Responses
Cause:: Failed while processing keys
Action:: Check the logs

JPS-09506: Error occurred when commiting changes, calling abort method to clean up the environment
Category:: Requests/Responses
Cause:: Failed while commiting changes
Action:: Please check the logs

JPS-09507: No templates are processed, please call processXXX() methods
Category:: Requests/Responses
Cause:: No templates are processed, please call processXXX() methods
Action:: Please call processXXX() methods before calling end() method

JPS-09508: No artifacts found for template {0}
Category:: Requests/Responses
Cause:: No templates specified in component-security-info.xml file
Action:: Please add new template in component-security-info.xml file

JPS-09509: No processing mode specified for template {0}
Category:: Requests/Responses
Cause:: No processing mode specified for a template
Action:: Please add processing mode for a template in component-security-info.xml file

JPS-09510: No credentials found for template {0}
Category:: Requests/Responses
Cause:: No credentials are available to seed into OPSS security store for template {0}
Action:: Please check the logs or corresponding credential data file in template

JPS-09511: Not able to instantiate credential store object for credential store {0}
Category:: Requests/Responses
Cause:: Scratch directory credential store initialization failed
Action:: Please check the logs

JPS-09512: Not able to instantiate key store service object for key stores {0}
Category:: Requests/Responses
Cause:: Scratch directory key store initialization failed
Action:: Please check the logs

JPS-09513: Not able to get the handle for bootstrap cwallet.sso {0}
Category:: Requests/Responses
Cause:: Not able to get the handle for bootstrap wallet
Action:: Please check the logs

JPS-09514: Credential already exist for map {0} and key {1}
Category:: Requests/Responses
Cause:: Credentials already exist in the Opss CredentialStore Implementation
Action:: Pass credentials with unique map and key name

JPS-09515: CIE CredentialsInfo object should not be null
Category:: Requests/Responses
Cause:: Passed CIE CredentialStoreInfo object is NULL
Action:: Please pass valid CIE credential object

JPS-09516: CIE KeystoreInfo object should not be null
Category:: Requests/Responses
Cause:: Passed CIE KeystoresInfo object is NULL
Action:: Please pass valid CIE key store object

JPS-09517: CIE PrivateKeyInfo object should not be null
Category:: Requests/Responses
Cause:: Passed CIE PrivateKeyInfo object is NULL
Action:: Please pass valid CIE private key object

JPS-09518: Alias '''{0}''' already exist in key store {1}
Category:: Requests/Responses
Cause:: Alias already exist in the Opss key store Implementation
Action:: Please key object with unique alias

JPS-09519: Error occurred when processing audit data for template {0}. Reason {1}
Category:: Requests/Responses
Cause:: Failed while processing audit data
Action:: Check the logs

JPS-09520: Error occurred when processing authorization data for template {0}. Reason {1}.
Category:: Requests/Responses
Cause:: Failed while processing authorization data
Action:: Check the logs

JPS-09521: More than one application stripe {0} found in authorization data file {1}.
Category:: Requests/Responses
Cause:: More than one application stripe in authorization data file
Action:: Ensure that the authorization file does not have more than one application stripe

JPS-09522: Authorization data file {0} is not present.
Category:: Requests/Responses
Cause:: No authorization data file found.
Action:: Verify if the file is present

JPS-09523: No keys found for template {0}
Category:: Requests/Responses
Cause:: No keys are available to seed into OPSS security store for template {0}
Action:: Please check the logs or corresponding keystore data file in template

JPS-09524: More than one component types found in audit store data file {0} for template {1}.
Category:: Requests/Responses
Cause:: More than one component types in audit store data file
Action:: Ensure that the audit store file does not have more than one component type

JPS-09525: Invalid target store is configured in component-security-info.xml. Target store could only be 'SEED' or 'CUSTOMER'.
Category:: Requests/Responses
Cause:: Invalid target store is configured in component-security-info.xml.
Action:: Ensure that target store is 'SEED' or 'CUSTOMER'.

JPS-09600: File {0} is cannot be found. Check if the specified file is expected in the specified location.
Category:: Configuration
Cause:: File {0} cannot be found.
Action:: Check if the specified file exists and accessible in the specified location.

JPS-09601: The value "{0}" is invalid for {1}.
Category:: Configuration
Cause:: An invalid value was provided for this configuration.
Action:: Provide the correct value.

JPS-09602: Fail to find default JPS Context in {0}.
Category:: Configuration
Cause:: Fail to find default JPS Context in the jps-config.xml.
Action:: Check content of jps-config.xml.

JPS-09603: SecurityContext.getSharedSecretStore and getSharedSecretStorePassword return inconsistent values.
Category:: Configuration
Cause:: SecurityContext.getSharedSecretStore and getSharedSecretStorePassword return inconsistent values.
Action:: Both shared secret store name and password are required for configuring a domain with shared database security store.

JPS-09604: JDBC Information {0} is missing for configuring security store to database.
Category:: Configuration
Cause:: JDBC Information is missing for configuring security store to database.
Action:: Check if all required jdbc information is supplied.

JPS-09605: Fail to find JPS Context with id {0} in {1}.
Category:: Configuration
Cause:: Fail to find the specific JPS Context in the jps-config.xml.
Action:: Check content of jps-config.xml.

JPS-09606: Error encountered while importing encryption key in shared database security store.
Category:: Configuration
Cause:: Error encoutered while seeding encryption key in shared database security store.
Action:: Check if encryption key is exported and imported properly.

JPS-09607: OpssSecurityConfiguration is in invalid state.
Category:: Configuration
Cause:: OpssSecurityConfiguration is in invalid state, it has not been initialized properly
Action:: If creating expanded domain, check if database is up and all the required datasource information are provided.

JPS-09608: OpssSecurityConfiguration is in invalid state, start method is not invoked prior to other methods.
Category:: Configuration
Cause:: OpssSecurityConfiguration is in invalid state - start() method is not invoked by CIE prior to other methods
Action:: Check if CIE is invoking OpssSecurityConfiguration in proper order.

JPS-09609: Failed to initialize OPSS security context based on SecurityContext object from CIE.
Category:: Configuration
Cause:: Failed to initialize OPSS security context based on SecurityConext object passed from CIE.
Action:: Check the logs.

JPS-09610: Error during updating audit loader repositoryType. Exception {0}
Category:: Configuration
Cause:: Failed to update audit loader repository type to DB.
Action:: Check the logs.

JPS-09611: Error updating audit loader credential in bootstrap wallet. Exception {0}
Category:: Configuration
Cause:: Failed to add audit loader credentials to bootstrap wallet
Action:: Check the logs.

JPS-09612: JDBC password for {0} is missing for configuring security store to database.
Category:: Configuration
Cause:: JDBC password is missing for configuring security store to database.
Action:: Check if jdbc password is supplied.

JPS-09613: JDBC username for {0} is missing for configuring security store to database.
Category:: Configuration
Cause:: JDBC username is missing for configuring security store to database.
Action:: Check if jdbc username is supplied.

JPS-09614: The supplied password for property {0} is invalid.
Category:: Configuration
Cause:: The supplied password for property {0} is invalid.
Action:: Please provide valid password.

JPS-09615: Update jps configuration file(s) failed for service {0}. Exception {1}
Category:: Configuration
Cause:: Update jps configuration file(s) failed for service {0}.
Action:: Check log file for errors.

JPS-09616: The schema {0} is already in use for security store(s). Please create a new schema.
Category:: Configuration
Cause:: The schema {0} is already in use for security store(s).
Action:: Please create a new schema.

JPS-09617: Failed to create a domain with shared security store because no security store was found in the database schema {0}.
Category:: Configuration
Cause:: Failed to create a domain with shared security store because no security store was found in the database schema {0}.
Action:: Please check if a security store is configured properly for the database schema.

JPS-09618: Data migration failed for configurator {0}
Category:: Configuration
Cause:: Failed to migrate data for configurator {0}.
Action:: Please check the logs and check if a security store is configured properly for the database schema.

JPS-09619: Jps test service failed for configurator
Category:: Configuration
Cause:: Jps test service failed for configurator.
Action:: Please check the logs and check if a security store is configured properly for the database schema.

JPS-09620: Failed to rollback data.
Category:: Configuration
Cause:: Failed to rollback data.
Action:: Please check the logs

JPS-09621: No entry found for artifact type {0} in component-security-info.xml file of template {1}.
Category:: Requests/Responses
Cause:: Artifact is not registered in component-security-info.xml file of template, but artifact data is present as part of template.
Action:: Please register missing artifact in component-security-info.xml file

JPS-09622: Error during configuring DB security store. Exception {0}.
Category:: Configuration
Cause:: Error occured during configuring DB security store.
Action:: Check the logs

JPS-09623: Error during updating JPS configuration in shared DB security store. Exception {0}.
Category:: Configuration
Cause:: Error updating JPS configuration in shared DB security store.
Action:: Check the logs

JPS-09624: JDBC database name for {0} is missing for configuring security store to database.
Category:: Configuration
Cause:: JDBC database name is missing for configuring security store to database.
Action:: Check if jdbc database is supplied.

JPS-09625: Jps test service completed for configurator.
Category:: Configuration
Cause:: Jps test service completed for configurator.
Action:: No action required.

JPS-09626: Rolling back of data for configurator is completed.
Category:: Configuration
Cause:: Rolling back of data for configurator is completed.
Action:: No action required

JPS-09627: Trying to rollback data for configurator.
Category:: Configuration
Cause:: Trying to rollback data for configurator.
Action:: No action required

JPS-09630: Failed to seed MDS credential to bootstrap cwallet file with specified key/map {0}.
Category:: Configuration
Cause:: Failed to seed MDS credential to bootstrap cwallet file.
Action:: Check the logs

JPS-09631: Failed to create tenant config profile {0} in MDS.
Category:: Configuration
Cause:: Failed to create tenant config profiles in MDS.
Action:: Check the logs

JPS-09632: More than one config-security-file.xml are round in templates.
Category:: Configuration
Cause:: More than one config-security-file.xml in templates are found.
Action:: Check the logs

JPS-09633: Start to provisioning partition {0} with OPSS resource group. Parameters: {1}.
Category:: Configuration
Cause:: Start to provisioning a partition with OPSS resource group.
Action:: No action required

JPS-09634: Rollback partition provisioning.
Category:: Configuration
Cause:: Rollback partition provisioning.
Action:: No action required

JPS-09635: Partition provisioning with OPSS resource group is completed.
Category:: Configuration
Cause:: Successfully provisioning a partition with OPSS resource group.
Action:: No action required

JPS-10000: There was an internal error in the policy store.
Category:: Security
Cause:: The opearion is not allowed for multivalued attribute.
Action:: The opearion is not allowed for multivalued attribute.Supply a valid opearion

JPS-10001: Exception happened while decoding value: {0}.
Category:: Security
Cause:: The encoding format is not correct.
Action:: Check encoding format of String value.

JPS-10002: Container is not ready. Reason: {0}.
Category:: Security
Cause:: Container is not ready.
Action:: Wait for container to start up successfully.

JPS-10003: Null search value is not allowed, unless the matcher is ANY.
Category:: Security
Cause:: Query value is null but the matcher is not ANY.
Action:: Do not use null query value if the matcher is not ANY.

JPS-10004: The search value {0} is invalid.
Category:: Security
Cause:: Query value is invalid.
Action:: Use an valid query value.

JPS-10005: Access denied. {0}
Category:: Security
Cause:: Access to policy store is denied.
Action:: Do not perform such operation on policy store.

JPS-10050: The application {0} cannot be found at runtime due to {1}.
Category:: Security
Cause:: Corresponding runtime application does not exist.
Action:: Check if policy is properly distributed.

JPS-10051: Policy object "{0}" already exists in application policy "{1}".
Category:: Security
Cause:: Policy object with same name exists in this application policy.
Action:: Try a different name.

JPS-10052: The list of runtime events is NULL.
Category:: Security
Cause:: The list of runtime events is NULL
Action:: Please contact the security administrator.

JPS-10053: The runtime events is NULL.
Category:: Security
Cause:: The runtime event is NULL
Action:: Please contact the security administrator.

JPS-10100: The policy domain "{0}" does not exist.
Category:: Security
Cause:: The policy domain does not exist
Action:: Check the policy domain name.

JPS-10102: The policy domain "{0}" already exists.
Category:: Security
Cause:: The policy domain exists
Action:: Create a policy domain with a different name.

JPS-10151: Application role {0} does not exist
Category:: Security
Cause:: The application role does not exist.
Action:: Provide correct application role.

JPS-10152: Application Role {0} is used.
Category:: Security
Cause:: Application Role is used.
Action:: Remove the objects which use this application role.

JPS-10153: Application role {0} does not belong to current application.
Category:: Security
Cause:: Application role does not belong to current application policy.
Action:: Modify the application role with application role manager from correct application policy.

JPS-10154: Class {0} is not supported.
Category:: Security
Cause:: The principal class specified is not supported.
Action:: Provide correct principal class.

JPS-10155: The application role attribute {0} is not supported for app role search.
Category:: Security
Cause:: The application role attribute specified is not supported.
Action:: Provide supported attribute.

JPS-10156: Error occurred while fetching the application role {0}.
Category:: Security
Cause:: The internal error occured while fetching the application role.
Action:: Refer to the log files for details and correct the error.

JPS-10157: More than one results found for given Application role:{0}, Application name {1}, query:{2} and Actual result: {3}.
Category:: Security
Cause:: More than one results found for application name.
Action:: Refer to the log files for details and correct the error.

JPS-10158: Invalid parameter.
Category:: Security
Cause:: Invalid parameter value.
Action:: Please check the values are of required type.

JPS-10159: Application Role {0} has an invalid unique name
Category:: Security
Cause:: Application role has an invalid unique name
Action:: See the log files for more details.

JPS-10160: The Application role {0} does not belong to application. The application role dn {1} and unique name {2} are not matching.
Category:: Security
Cause:: The Application role does not belong to application contex.
Action:: See the log files for more details.

JPS-10161: Internal error- More than one grantee entries found.
Category:: Security
Cause:: Internal error- More than one grantee entries found.
Action:: See the log files for more details.

JPS-10162: Grantee DN was missing
Category:: Security
Cause:: Grantee DN was missing
Action:: See the log files for more details.

JPS-10163: Internal error while revoking the permissions. Number of permissions to revoke (or delete) {0} : though only {1} permission(s) would be revoked (or deleted) if this operation were to proceed
Category:: Security
Cause:: Internal error while revoking the permissions.
Action:: See the log files for more details.

JPS-10164: Only one of permission list and permission entry list can be null/non-null.
Category:: Security
Cause:: Only one of permission list and permission entry list can be null/non-null
Action:: See the log files for more details.

JPS-10165: MATCHER.ANY not allowed for this kind of search operation
Category:: Security
Cause:: MATCHER.ANY not allowed for this kind of search operation
Action:: Search is not allowed for the MATCHER.ANY

JPS-10166: Error occurred during performing the operation {0}.
Category:: Security
Cause:: Error occured during performing the operation.
Action:: See the log files for more details.

JPS-10167: Obligation does not exist for the policy domain {0}.
Category:: Security
Cause:: Obligation does not exist for the policy domain {0}.
Action:: See the log files for more details.

JPS-10168: Error occurred while preparing the principal in {0} method of {1} class : {2}. In standalone mode, weblogic specific jars should not be in classpath. Please check the classpath and try again.
Category:: Security
Cause:: Fail to resolve principal.
Action:: Check classpath which may contain weblogic specific jars.

JPS-10169: Default SystemAdminRole should be granted to at least one principal.
Category:: Security
Cause:: Revoking last member of default admin role SystemAdmin
Action:: Keep at least one member of default admin role SystemAdmin

JPS-10200: Administration role {0} already exists
Category:: Security
Cause:: Cannot have two administration roles with the same name.
Action:: Provide a new name to the administration role.

JPS-10201: Administration role {0} does not exist
Category:: Security
Cause:: Administration role is not found.
Action:: Check the administration role name.

JPS-10202: Administration role {0} is used
Category:: Security
Cause:: Administration role is used.
Action:: Remove administration role members first.

JPS-10203: Administration role {0} does not belong to current context
Category:: Security
Cause:: Administration role does not belong to current context.
Action:: Use it in correct context.

JPS-10204: Cannot create admin role with default name {0}
Category:: Security
Cause:: Cannot create admin role with reserved name.
Action:: Use another name for admin role.

JPS-10205: Cannot delete default admin role {0}
Category:: Security
Cause:: Cannot delete default admin role.
Action:: Check the admin role name for deletion.

JPS-10206: Cannot grant {0}, {1} to admin role because its super admin role has no such privilege
Category:: Security
Cause:: Cannot grant privileges to admin role whose super role has not.
Action:: Check the admin resource action to grant.

JPS-10207: Admin resource {0} is not for this scope {1}
Category:: Security
Cause:: This admin resource is not for this scope
Action:: Check the admin resource to grant.

JPS-10208: Cannot change rights of default admin role {0}
Category:: Security
Cause:: Cannot change righs of default admin role for a scope
Action:: Check the admin role name.

JPS-10209: The value for the SEARCH_PROPERTY.PRINCIPAL does implement the java.security.Principal interface. It is of type "{0}".
Category:: Security
Cause:: The search by value is not an instance of java.security.Principal
Action:: Supply an object of type java.security.Principal

JPS-10210: The value for the SEARCH_PROPERTY.PRINCIPAL_NAME is not of type java.lang.String. It is of type "{0}".
Category:: Security
Cause:: The search by value is not an instance of java.lang.String
Action:: Supply an object of type java.lang.String

JPS-10211: Administration role cannot have more than one grantee for parameter Application:{0}, policy Domain:{1}, Query Parameter:{2}, Actual results:{3}.
Category:: Security
Cause:: The admin role cannot have more than one grantee entry.
Action:: Check only one grantee entry available to admin role.

JPS-10250: Resource type reference should not be null.
Category:: Security
Cause:: The parameter resource type reference is null.
Action:: Use a valid object.

JPS-10251: The resource type reference is invalid.
Category:: Security
Cause:: The current resource type reference is invalid.
Action:: Use a valid resource type reference.

JPS-10252: The resource type "{0}" already exists.
Category:: Security
Cause:: The resource type has existed.
Action:: Make sure the resource type does not exist.

JPS-10253: The super resource type {0} does not exist.
Category:: Security
Cause:: The resource type is referring an invalid super resource type.
Action:: Make sure the super resource type exist.

JPS-10254: The resource type {0} should not have its own matcher since it has super type.
Category:: Security
Cause:: The resource type has both its own matching algorithm and super type.
Action:: Remove matching algorithm if the resource type should have super type. Otherwise, remove super type.

JPS-10255: Resource type search context should not be null.
Category:: Security
Cause:: The resource type context could not be gotten.
Action:: Make sure the application policy is available.

JPS-10256: Could not get an available data manager.
Category:: Security
Cause:: The data manager is invalid.
Action:: Make sure policy store and related configuration are correct.

JPS-10257: The modification operator {0} is invalid.
Category:: Security
Cause:: The operator in ModificationItem is invalid.
Action:: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.

JPS-10258: The property name {0} is unknown.
Category:: Security
Cause:: The attribute ID in ModificationItem is undefined.
Action:: Make sure the attribute ID is a valid one.

JPS-10259: The name of resource type could not be modified.
Category:: Security
Cause:: Resource type name could not be modified.
Action:: Do not put resource type name in ModificationItem.

JPS-10260: The super type of resource type could not be modified.
Category:: Security
Cause:: The super type of resource type could not be modified.
Action:: Do not put super type in ModificationItem.

JPS-10261: The matching algorithm of resource type could not be modified.
Category:: Security
Cause:: The matching algorithm of resource type could not be modified.
Action:: Do not put matching algorithm in ModificationItem

JPS-10262: The action delimiter of resource type could not be modified.
Category:: Security
Cause:: The action delimiter of resource type could not be modified.
Action:: Do not put action delimiter in ModificationItem.

JPS-10263: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.
Category:: Security
Cause:: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.
Action:: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.

JPS-10264: The property {0} of resource type is single, could not have more than one value.
Category:: Security
Cause:: The property could not have more than one value.
Action:: First remove the existing value before adding new one.

JPS-10265: Could not add or replace the property {0} since there is no value provided.
Category:: Security
Cause:: There is no value provided when trying to add or replace an property.
Action:: Provide the new value.

JPS-10266: The value data type of property {0} should be String.
Category:: Security
Cause:: The value data type of property is not String.
Action:: Use a String object as value.

JPS-10267: The resource type {0} does not exist.
Category:: Security
Cause:: The resource type does not exist.
Action:: Make sure the resource type exist.

JPS-10268: The resource type {0} is in use, could not be deleted.
Category:: Security
Cause:: The resource type could not be deleted without cascade since it is in use.
Action:: Cascade delete it or first remove all referring objects.

JPS-10269: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute
Category:: Security
Cause:: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute
Action:: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.

JPS-10270: The resource type attribute {0} is used in policy(-ies) and can not be deleted.
Category:: Security
Cause:: The resource type attribute being deleted was used in one or morepolicies and could not be deleted.
Action:: Before deleting the resource attribute, make sure it is not used.

JPS-10271: The resource matcher class of resource type {0} could not be modified to {1}.
Category:: Security
Cause:: The resource type matcher class was changed while modifying.
Action:: Keep matcher class unchanged.

JPS-10272: Permission Class not found in the classpath: {0}
Category:: Security
Cause:: The permission class was not found in the class path.
Action:: Make sure that the permission class is part of the class path for the program.

JPS-10273: Permission class expected to be either oracle.security.jps.ResourcePermission or extending oracle.security.jps.AbstractTypedPermission but found {0} Resource Type: {1} is sharing permission class with Resource Type: {2}
Category:: Security
Cause:: The Permission class is not either ResourcePermission or Abstracted Permission
Action:: The Permission class for the resource type must be a Resource permission

JPS-10274: Permission should be associated with a Resource Type. Permission Name: {0}
Category:: Security
Cause:: The permission should have a resource type associated with it
Action:: Make sure that the permission has a resource type associated with it

JPS-10275: Resource Type Matcher Class and Permissions do not match. {0} and {1} do not match
Category:: Security
Cause:: Resource Type Matcher Class and Permissions do not match.
Action:: Make sure that the Matcher Class and Permissions match.

JPS-10276: Cannot determine the Resource Type from the permission {0}
Category:: Security
Cause:: Cannot determine the Resource Type from the permission.
Action:: Make sure that there is a resource type associated with the permission class

JPS-10277: Allowed attributes can not be modified.
Category:: Security
Cause:: Allowed attributes can not be modified.
Action:: Make sure not modifying allowed attributes

JPS-10278: Requested modification to the resource type {0} is not allowed.
Category:: Security
Cause:: Requested modification to the resource type is not allowed.
Action:: Make sure not to make certain type of changes to the resource type when it is used by resources

JPS-10279: The custom resource matcher class of resource type {0} could not be modified to {1}.
Category:: Security
Cause:: The custom resource matcher class was changed while modifying the resource type.
Action:: Keep custom resource matcher class unchanged.

JPS-10280: The resource attribute {0} does not exist in the resource type {1}.
Category:: Security
Cause:: The resource attribute does not exist in the resource type.
Action:: Check all the valid resource attributes in the resource type.

JPS-10400: Resource reference should not be null.
Category:: Security
Cause:: The parameter resource reference is null.
Action:: Use a valid object.

JPS-10401: The resource reference is invalid.
Category:: Security
Cause:: The current resource reference is invalid.
Action:: Use a valid resource reference.

JPS-10402: The resource {0} does not exist.
Category:: Security
Cause:: The resource does not exist.
Action:: Make sure the resource exist.

JPS-10403: Could not get an available data manager.
Category:: Security
Cause:: The data manager is invalid.
Action:: Make sure policy store and related configuration are correct.

JPS-10404: The resource type {0} does not exist.
Category:: Security
Cause:: The resource type does not exist.
Action:: Make sure the resource type exist.

JPS-10405: The resource "{0}" with type "{1}" already exists in current application policy.
Category:: Security
Cause:: The resource to be created has existed.
Action:: Make sure the resource does not exist.

JPS-10406: The modification operator {0} is invalid.
Category:: Security
Cause:: The operator in ModificationItem is invalid.
Action:: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.

JPS-10407: The property name {0} is unknown.
Category:: Security
Cause:: The attribute ID in ModificationItem is undefined.
Action:: Make sure the attribute ID is a valid one.

JPS-10408: The name and type of resource could not be modified.
Category:: Security
Cause:: The name and type of resource could not be modified.
Action:: Do not put resource name and type in ModificationItem.

JPS-10409: The property {0} of resource is single, could not have more than one value.
Category:: Security
Cause:: The property could not have more than one value.
Action:: First remove the existing value before adding new one.

JPS-10410: Could not add or replace the property {0} since there is no value provided.
Category:: Security
Cause:: There is no value provided when trying to add or replace an property.
Action:: Provide the new value.

JPS-10411: The resource {0} is in use, could not be deleted.
Category:: Security
Cause:: The resource could not be deleted without cascade since it is in use.
Action:: Cascade delete it or first remove all referring objects.

JPS-10412: The resource attribute {0} already exists in the current entry.
Category:: Security
Cause:: The resource attribute could not be added since it already exists.
Action:: Remove duplicate resource attributes.

JPS-10413: The resource action {0} already exists in the current entry.
Category:: Security
Cause:: The resource action could not be added since it already exists.
Action:: Remove duplicate resource actions

JPS-10414: The resource attribute {0} could not be deleted since it does not exist.
Category:: Security
Cause:: The resource attribute could not be deleted since it does not exist.
Action:: Check if the resource attribute exists.

JPS-10415: The resource action {0} could not be deleted since it does not exist.
Category:: Security
Cause:: The resource action could not be deleted since it does not exist.
Action:: Check if the resource action exists

JPS-10416: Resource {0} does not belong to the context.
Category:: Security
Cause:: The resource does not belong to current context
Action:: Pass in correct resource.

JPS-10417: Resource query across different resource type is not allowed.
Category:: Security
Cause:: Resource query across different resource type is not allowed
Action:: Pass in correct query parameter.

JPS-10418: Cannot delete a resource that has one more child resources.
Category:: Security
Cause:: Can not detele a resource that has one or more child resources
Action:: Delete all child resources and then try again.

JPS-10419: Resource hierarchy type change is not allowed.
Category:: Security
Cause:: Resource hierarchy type change is not allowed.
Action:: Check the resource hierarchy type

JPS-10420: Resource name must begin with the resource name delimiter.
Category:: Security
Cause:: Resource name must begin with the resource name delimiter
Action:: Add resource name delimiter in the begining of the resource name.

JPS-10421: The given all action key word exists in actions.
Category:: Security
Cause:: The given all action value already exists
Action:: Check the input all action value and check for duplicate values.

JPS-10422: The resource attribute {0} is used in policy(-ies) and can not be deleted.
Category:: Security
Cause:: The resource attribute is used in policy(-ies) and can not be deleted.
Action:: Before deleting the resource attribute, make sure it is not used.

JPS-10423: The action {0} is used by the {1} and can not be deleted.
Category:: Security
Cause:: The action is used by the permissionSet/permission and can not be deleted.
Action:: Check if the action is used in any PermissionSet/Permission before deleting.

JPS-10424: The resourceType {0} of hierarchy type is invalid as its parent is null.
Category:: Security
Cause:: The heirarical resourcetype's parent is null.
Action:: Make sure to provide a valid name for the heirarical resourcetype

JPS-10425: The resource attribute {0} contains duplicate value {1}.
Category:: Security
Cause:: The resource attribute already contains this value.
Action:: Remove duplicate resource attributes values.

JPS-10426: Cannot set all actions keyword for resource type with non-null matcher class.
Category:: Security
Cause:: All actions keyword cannot be set to resource type with matcher class
Action:: Do not set all actions keyword for a resource type with a matcher class.

JPS-10427: The resource name expression "{0}" is not a valid Java regular expression.
Category:: Security
Cause:: Regular expression provided for resource name expression is invalid.
Action:: Check that the resource name expression is a valid Java regular expression.

JPS-10428: The resource {0} of type {1} does not exist.
Category:: Security
Cause:: The resource of the resource type does not exist.
Action:: Make sure the resource of the resource type exists.

JPS-10429: The value data type of property {0} should be String and not {1}.
Category:: Security
Cause:: The value data type of property is not String.
Action:: Use a String object as value.

JPS-10430: The Resource name {0} has an invalid format
Category:: Security
Cause:: Too many delimiters in the resurce name
Action:: Limit the number of delimiters in the beginning and middle of resource name to one.

JPS-10431: Wrong isSingle property for the attribute {0}; expected {1}, but {2}.
Category:: Security
Cause:: Wrong isSingle property of resource attribute
Action:: Ensure isSingle property of the attribute in resource is the same as the definiton in resource type

JPS-10432: Wrong DataType property for the attribute {0}; expected {1}, but {2}.
Category:: Security
Cause:: Wrong DataType property of resource attribute
Action:: Ensure DataType property of the attribute on resource is the same as the definition in resource type

JPS-10451: Permission set {0} does not belong to the context.
Category:: Security
Cause:: The permission set does not belong to current context
Action:: Pass in correct permission set.

JPS-10452: Permission set {0} has ResourceActionsEntry with null ResourceEntry and null ResourceNameExpression.
Category:: Security
Cause:: Both ResourceEntry and Resource name expression of ResourceActionsEntry is null
Action:: Pass in correct ResourceActionsEntry.

JPS-10454: No resources or actions have been identified by the permission set.
Category:: Security
Cause:: No resources or actions have been identified by the permissionset.
Action:: Ensure that the permission set is created with valid resource actions.

JPS-10455: Type of the resource does not define matcher java permission class.
Category:: Security
Cause:: Resource is not protected by a Java Permission.
Action:: Ensure that the permission set is created with valid resource object.

JPS-10456: ResourceExpression and ResourceAction cannot be specified at the same time.
Category:: Security
Cause:: ResourceExpression and ResourceAction cannot be specified at the same time.
Action:: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.

JPS-10457: Not able to perform operation due to invalid parameter. Cause: "{0}".
Category:: Security
Cause:: Not able to perform operation due to invalid parameter. Cause: {0}.
Action:: Ensure that the operation is called with valid parameters.

JPS-10458: ResourceExpression and ResourceAction cannot be null at the same time.
Category:: Security
Cause:: ResourceExpression and ResourceAction cannot be null at the same time.
Action:: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.

JPS-10459: The modified permission set {0} contains resources of multiple resource types. It is not permitted as there is policy(-ies) that references that permission set and uses resource attributes.
Category:: Security
Cause:: The modified permission set contained resources of multiple resource types. It was not permitted if there was a policy that referenced that permission set and used resource attributes.
Action:: Fix the permission set or modify the policy(-ies).

JPS-10460: The permission set search query {0} is not supported
Category:: Security
Cause:: The permission set search query is not supported.
Action:: Use supported query scenario.

JPS-10463: Requested actions: " {0} " are not a subset of valid actions: " {1}" for the given resource: " {2} " and type: " {3} ".
Category:: Security
Cause:: Invalid resource actions for the given resource.
Action:: Ensure that the actions in the resource-actions are a valid subset of the actions defined by the resource type.

JPS-10464: Error occurred while getting the permission set entry for permission set search query {0}.
Category:: Security
Cause:: Error occured while getting the permission set entry for permission set search query.
Action:: See the log files for more details.

JPS-10465: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.
Category:: Security
Cause:: Expression in ResourceNameExpression of ResourceActionsEntry is null
Action:: Pass in correct ResourceActionsEntry with non-null Resource name expression.

JPS-10466: Resource {0} has no Resource Actions, but Resource Type {1} has resource actions.
Category:: Security
Cause:: Empty resource actions for the given Resource, but Resource type has actions.
Action:: Ensure that the actions in the resource-actions are not null or empty since the resource type has actions.

JPS-10467: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.
Category:: Security
Cause:: Expression in ResourceNameExpression of ResourceActionsEntry is null
Action:: Pass in correct ResourceActionsEntry with non-null Resource name expression.

JPS-10468: Duplicate permission " {0} " in policy store.
Category:: Security
Cause:: Duplicate permission in policy store.
Action:: Check the policy store and ensure that there is no duplicate permission.

JPS-10469: Cannot remove all the ResourceActionsEntrys in PermissionSet.
Category:: Security
Cause:: Try to remove all the ResourceActionsEntrys in existing PermissionSet.
Action:: Check the updated resource actions, make sure PermissionSet does not have up empty resource actions.

JPS-10470: The resource type name "{0}", does not match the resourceType in the encoded target name: "{1}". Permission class is "{2}"
Category:: Security
Cause:: Invalid resource type in permission target.
Action:: Refer to the log files for details.

JPS-10471: Resource type is missing in the target name: "{0}", for permission: "{1}"
Category:: Security
Cause:: Resource type missing in permission target.
Action:: Refer to the log files for details.

JPS-10472: Target "{0}" is missing the prefix "=resourceName=". Unable to determine the resource name for permission: "{1}"
Category:: Security
Cause:: Target name missing in permission target.
Action:: Refer to the log files for details.

JPS-10473: The target name "{0}" is invalid. Should start with "{1}"
Category:: Security
Cause:: Target name encoding is not correct.
Action:: Refer to the log files for details.

JPS-10474: The parameter: "{0}", value: "{1}" cannot be null
Category:: Security
Cause:: Permission target is null.
Action:: Refer to the log files for details.

JPS-10475: The permission actions: "{0}" are not a subset of valid actions defined in resource type: "{1}"
Category:: Security
Cause:: Permission actions do not match with valid resource type actions.
Action:: Refer to the log files for details.

JPS-10476: The resource name can not be null
Category:: Security
Cause:: Invalid resource name in permission target.
Action:: Refer to the log files for details.

JPS-10500: The target policy, {0}, does not exist.
Category:: Security
Cause:: The policy object does not exist.
Action:: Check if the target policy exists.

JPS-10501: Policy query contains unrecognizable information.
Category:: Security
Cause:: Policy query contains unrecognizable information.
Action:: Check the policy query object.

JPS-10502: Policy rule information is missing.
Category:: Security
Cause:: Policy rule information is missing.
Action:: Check if policy rule information exists in policy repository.

JPS-10503: Obligation information is missing.
Category:: Security
Cause:: Obligation information is missing.
Action:: Check if obligation information exists in policy repository.

JPS-10504: Permission set information is missing.
Category:: Security
Cause:: Permission set information is missing.
Action:: Check if permission set information exists in policy repository.

JPS-10505: Grantee information is missing.
Category:: Security
Cause:: Grantee information is missing.
Action:: Check if grantee information exists in policy repository.

JPS-10506: The policy rule, {0}, does not exist.
Category:: Security
Cause:: The policy rule does not exist.
Action:: Check the policy rule name passed in.

JPS-10507: The condition string is in wrong format, {0}.
Category:: Security
Cause:: Condition string is in wrong format.
Action:: Check condition string in policy repository.

JPS-10508: Policy condition contains an unknown function, {0}.
Category:: Security
Cause:: Policy condition contains an unknown function.
Action:: Check condition string in policy repository.

JPS-10509: Policy condition parsing error.
Category:: Security
Cause:: Policy condition parsing error.
Action:: Check condition string in policy repository.

JPS-10510: The expression, {0}, is unknown.
Category:: Security
Cause:: The policy expression is unknown.
Action:: Check condition string in policy repository.

JPS-10511: The data type, {0}, is unknown.
Category:: Security
Cause:: The data type is unknown
Action:: Check condition string in policy repository.

JPS-10512: A ResourceActionsEntry should contain either resource entry or resource name expression.
Category:: Security
Cause:: The ResourceActionsEntry object does not contain resource infomation.
Action:: Check ResourceActionsEntry passed in.

JPS-10513: The search value type {0} is not supported for {1}.
Category:: Security
Cause:: Query criteria type does not support.
Action:: Pass in a correct query value.

JPS-10514: Cannot add PermissionSet to PolicyEntry if it has ResourceType.
Category:: Security
Cause:: Resource type is already defined in PolicyEntry.
Action:: clear resource type of PolicyEntry before adding PermissionSetEntry.

JPS-10515: Cannot set ResourceType to PolicyEntry if it has PermissionSet.
Category:: Security
Cause:: Permission Set is already defined in PolicyEntry.
Action:: clear Permission Set of PolicyEntry before setting Resource Type.

JPS-10516: Cannot add Rule if there is rule already in PolicyEntry
Category:: Security
Cause:: Add rule to policy when the policy already has rule.
Action:: Delete existing rule before adding new rule to policy.

JPS-10517: Delete rule not existing in PolicyEntry
Category:: Security
Cause:: rule does not belong to the PolicyEntry.
Action:: Check the rule before deleting rule from PolicyEntry.

JPS-10518: Delete permission set not existing in PolicyEntry
Category:: Security
Cause:: permission set does not belong to the PolicyEntry.
Action:: Check the permission set before deleting permission set from PolicyEntry.

JPS-10519: Delete obligation not existing in PolicyEntry
Category:: Security
Cause:: obligation does not belong to the PolicyEntry.
Action:: Check the obligation before deleting obligation from PolicyEntry.

JPS-10520: Delete Principal not existing in PolicyEntry
Category:: Security
Cause:: principal does not belong to the PolicyEntry.
Action:: Check the principal before deleting principal from PolicyEntry.

JPS-10521: The obligation {0} already exists.
Category:: Security
Cause:: The obligation already exists in the policy entry.
Action:: Check ObligationEntry passed in.

JPS-10522: The parameters passed in is invalid, we expect {0}, but {1} is passed in.
Category:: Security
Cause:: The parameter passed in the function is not valid.
Action:: Pass in correct parameters.

JPS-10523: The function return type is invalid, we expect OpssBoolean, but {0} is passed in.
Category:: Security
Cause:: The return type of the function is not valid.
Action:: Pass in a function with OpssBoolean return type.

JPS-10524: The query with search property {0}, comparator type {1} and matcher {2} is not supported.
Category:: Security
Cause:: Such query is not supported.
Action:: Pass in a supported query value.

JPS-10525: The attribute assignment {0} could not be added since it already exists.
Category:: Security
Cause:: The attribute assignment could not be added since it already exists.
Action:: Remove duplicate attribute assignments.

JPS-10526: The permission set {0} could not be added since it already exists.
Category:: Security
Cause:: The permission set could not be added since it already exists.
Action:: Remove duplicate permission sets.

JPS-10527: The principal {0} could not be added since it already exists.
Category:: Security
Cause:: The principal could not be added since it already exists.
Action:: Remove duplicate principals.

JPS-10528: The Policy {0} referenced multiple resource types and resource attribute is used in policy condition or obligation.
Category:: Security
Cause:: Policies that used resource attributes in their conditions or obligations could not refrence one or more permission sets that contain resources of multiple types.
Action:: Split the policy to reference only one resource type in each policy.

JPS-10529: The resource attribute {0} used in policy condition or obligation is invalid resource attribute of type {1}.
Category:: Security
Cause:: The resource attribute used in policy condition was invalid for the referenced resource type
Action:: Fix the policy condition to use only valid attributes for the given resource type.

JPS-10530: Cannot create a policy {0} with AdminRole(s) {1}.
Category:: Security
Cause:: Cannot create a policy with AdminRoleEntry(s).
Action:: Remove the AdminRole principals from the principal list.

JPS-10531: Cannot grant permission to AdminRole(s) {0}.
Category:: Security
Cause:: Cannot grant permission to AdminRoleEntry(s).
Action:: Remove the AdminRole principals from the principal list.

JPS-10532: Cannot grant AdminRole {0} to another AdminRole {1}.
Category:: Security
Cause:: Cannot grant AdminRole to another AdminRole.
Action:: Change to grant AdminRole to either enterprise role or user.

JPS-10533: Cannot revoke AdminRole {0} from another AdminRole {1}.
Category:: Security
Cause:: Cannot revoke AdminRole from another AdminRole.
Action:: Change to revoke AdminRole from either enterprise role or user.

JPS-10534: Cannot grant AdminRole {0} to an AppRole {1}.
Category:: Security
Cause:: Cannot grant AdminRole to an AppRole.
Action:: Change to grant AdminRole to either enterprise role or user.

JPS-10535: Cannot revoke AdminRole {0} from an AppRole {1}.
Category:: Security
Cause:: Cannot revoke AdminRole from an AppRole.
Action:: Change to revoke AdminRole from either enterprise role or user.

JPS-10536: AdminRole {0} cannot be managed outside of the AdminManager.
Category:: Security
Cause:: AdminRole cannot be managed outside of AdminManager.
Action:: Use AdminManager for all AdminRole related administrative tasks.

JPS-10537: Cannot modify grant permission to AdminRole(s) {0}.
Category:: Security
Cause:: Cannot modify grant permission to AdminRoleEntry(s).
Action:: Remove the AdminRole principals from the principal list.

JPS-10538: Cannot revoke permission from AdminRole(s) {0}.
Category:: Security
Cause:: Cannot revoke permission from AdminRoleEntry(s).
Action:: Remove the AdminRole principals from the principal list.

JPS-10539: Basic policy cannot have {0} information.
Category:: Security
Cause:: Basic policy cannot have {0} information.
Action:: Remove the information from basic policy.

JPS-10540: Basic policy cannot have ResourceActionsEntry without ResourceEntry.
Category:: Security
Cause:: Basic policy cannot have ResourceActionsEntry without ResourceEntry.
Action:: Use ResourceActionsEntry with ResourceEntry for basic policy.

JPS-10541: Basic policy cannot use Resource {0} without Resource Matcher Class.
Category:: Security
Cause:: Basic policy cannot use Resource {0} without Resource Matcher Class.
Action:: Use Resource with Resource Matcher Class for basic policy.

JPS-10542: Default TransformerFactory cannot be located.
Category:: Security
Cause:: The TransformerFactory cannot be loaded
Action:: Check the environment

JPS-10543: Failed to retrieve Transformer.
Category:: Security
Cause:: The TransformerFactory cannot generate a Transformer.
Action:: Check the environment

JPS-10544: The policy "{0}" already exists.
Category:: Security
Cause:: The role policy object exists.
Action:: Create a role policy with a different name.

JPS-10545: The application role {0} could not be added since it already exists.
Category:: Security
Cause:: The application role could not be added since it already exists.
Action:: Remove duplicate application role.

JPS-10546: The resource {0}, {1} could not be added since it already exists.
Category:: Security
Cause:: The resource could not be added since it already exists.
Action:: Remove duplicate resource.

JPS-10547: The resource name expression {0}, {1} could not be added since it already exists.
Category:: Security
Cause:: The resource name expression could not be added since it already exists.
Action:: Remove duplicate resource name expression.

JPS-10548: The policy rule {0} already exists.
Category:: Security
Cause:: The policy rule already exists.
Action:: Create policy rule with different name.

JPS-10549: The policy rule {0} is in use, could not be deleted.
Category:: Security
Cause:: The policy rule could not be deleted without cascade since it is in use.
Action:: Cascade delete it or first remove all referring objects.

JPS-10550: Attribute "{0}" already exists
Category:: Security
Cause:: Cannot have two attributes with the same name.
Action:: Provide a new name to the attribute.

JPS-10551: Attribute {0} does not exist
Category:: Security
Cause:: Attribute not found.
Action:: Check the attribute name.

JPS-10552: Attribute {0} is used.
Category:: Security
Cause:: Attribute is already used.
Action:: Remove the objects which use this attribute.

JPS-10553: Attribute {0} does not belong to current application.
Category:: Security
Cause:: Attribute does not belong to current application policy.
Action:: Modify the attribute with extension manager from correct application policy.

JPS-10554: The name of Attribute in policy repository is missing
Category:: Security
Cause:: Attribute in policy store has no name.
Action:: Check the underline policy repository.

JPS-10555: The type of Attribute in policy repository is missing
Category:: Security
Cause:: Attribute in policy store has no type.
Action:: Check the underline policy repository.

JPS-10556: The category of Attribute in policy repository is missing
Category:: Security
Cause:: Attribute in policy store has no category.
Action:: Check the underline policy repository.

JPS-10557: Cannot overwrite a built-in attribute, {0}.
Category:: Security
Cause:: Try to overwrite a built-in attribute.
Action:: Do not overwrite a built-in function.

JPS-10558: Cannot modify a built-in attribute, {0}.
Category:: Security
Cause:: Try to modify a built-in attribute.
Action:: Do not modify a built-in attribute.

JPS-10559: Cannot delete a built-in attribute, {0}.
Category:: Security
Cause:: Try to delete a built-in attribute.
Action:: Do not delete a built-in attribute.

JPS-10581: Cannot overwrite a built-in function, {0}.
Category:: Security
Cause:: Try to overwrite a built-in function.
Action:: Do not overwrite a built-in function.

JPS-10582: The function does not exist, {0}.
Category:: Security
Cause:: The function does not exist.
Action:: Check the function name passed in.

JPS-10583: The function is in use, {0}.
Category:: Security
Cause:: The function is in use.
Action:: Cannot delete a function in use.

JPS-10584: The function is used in some policies, your changes on return type may lead to unpredictable issues.
Category:: Security
Cause:: The function is in use.
Action:: Cannot change return type of a function in use.

JPS-10585: The function is used in some policies, your changes on parameter types may lead to unpredictable issues.
Category:: Security
Cause:: The function is in use.
Action:: Cannot change parameter types of a function in use.

JPS-10586: Cannot modify a built-in function, {0}.
Category:: Security
Cause:: Try to modify a built-in function.
Action:: Do not modify a built-in function.

JPS-10587: Cannot delete a built-in function, {0}.
Category:: Security
Cause:: Try to delete a built-in function.
Action:: Do not delete a built-in function.

JPS-10588: The function "{0}" already exists.
Category:: Security
Cause:: The function exists.
Action:: Create a function with a different name.

JPS-10589: Cascade delete is not supported.
Category:: Security
Cause:: Cascade delete not supported.
Action:: Set the cascade delete parameter to false.

JPS-10590: Cannot find the function entry for function name {0}.
Category:: Security
Cause:: Cannot find the function entry for function name.
Action:: Check function entry in policy repository.

JPS-10591: Cannot find the expression type for expression {0}.
Category:: Security
Cause:: Cannot find the expression type for the expression.
Action:: Check expression in policy repository.

JPS-10592: Operation {1} is not allowed for multi valued attribute {0}
Category:: Security
Cause:: The category of Attribute is Invalid.
Action:: The category of Attribute is Invalid. Supply a valid Attribute category

JPS-10600: Failed to initialize PD instance.
Category:: Security
Cause:: Failed to initialize PD instance.
Action:: Refer to the base exception in logs to resolve the issue.

JPS-10601: Failed to initialize PolicyDistributionManager instance.
Category:: Security
Cause:: Failed to initialize PolicyDistributionManager instance.
Action:: Refer to the base exception in logs to resolve the issue.

JPS-10602: PD has not been initialized.
Category:: Security
Cause:: PD has not been initialized.
Action:: Check if OPSS policy store provider has been initialized successfully.

JPS-10603: FAILURE: Retry {0} failed after {1} times retries due to following exception {2}.
Category:: Security
Cause:: PD operation failed to retry.
Action:: Check connectivity to backend repository.

JPS-10604: The operation is not allowed for non-controlled mode application {0}.
Category:: Security
Cause:: Can not distribute policy for non-controlled policy distribution mode application
Action:: Refer to the log files for details.

JPS-10605: Failed to distribute policy for catch exception.
Category:: Security
Cause:: Distribute policy failed for catch exception
Action:: Refer to the log files for details.

JPS-10606: Failed to distribute policy to PDP {0} for catch exception {1}.
Category:: Security
Cause:: Failed to distribute policy to pdp for catch exception
Action:: Refer to the log files for details.

JPS-10607: Invalid cache key {0} in {1} cache.
Category:: Security
Cause:: Invalid cache key
Action:: Refer to the log files for details.

JPS-10608: Failed to copy files from active directory {0} to update directory {1}.
Category:: Security
Cause:: Failed to copy cache file from active directory to update directory
Action:: Refer to the log files for details.

JPS-10609: Failed to write state.chk file.
Category:: Security
Cause:: Failed to write state.chk file
Action:: Refer to the log files for details.

JPS-10610: Failed to update local cache since distributed payload for application {0} is empty.
Category:: Security
Cause:: Failed to update local cache since distributed payload is empty
Action:: Refer to the log files for details.

JPS-10611: Invalid distribution state {0} in step {1}.
Category:: Security
Cause:: Invalid distribution state
Action:: Refer to the log files for details.

JPS-10612: Local cache file verification failed, so redistribute all binding applications
Category:: Security
Cause:: Failed to verify local cache file, so need to redistribution all binding applications
Action:: Refer to the log files for details.

JPS-10613: Failed to parse PD port number, do not start PD registration web service.
Category:: Security
Cause:: Failed to parse PD port number, do not start PD registration web service.
Action:: Refer to the log files for details.

JPS-10614: Failed to start PD registration web service for catch exception.
Category:: Security
Cause:: Failed to start PD registration web service for catch exception.
Action:: Refer to the log files for details.

JPS-10615: Catch exception.
Category:: Security
Cause:: Catch interrupt exception in start registration service thread.
Action:: Refer to the log files for details.

JPS-10616: Failed to find local host name, do not start PD registration web service.
Category:: Security
Cause:: Failed to find local host name, do not start PD registration web service.
Action:: Refer to the log files for details.

JPS-10617: Failed to start PD push policy web service for catch exception.
Category:: Security
Cause:: Failed to start PD registration web service for catch exception.
Action:: Refer to the log files for details.

JPS-10618: Invalid SSL configuration.
Category:: Security
Cause:: Invalid SSL configuration, please check log for details
Action:: Refer to the log files for details.

JPS-10619: Failed to initialize cipher {0} for local cache encryption/decryption.
Category:: Security
Cause:: Failed to initialize cipher for local cache encryption/decryption.
Action:: Refer to the log files for details.

JPS-10620: Exception reported in registration thread.
Category:: Security
Cause:: Catch interrupt exception in start registration service thread.
Action:: Refer to the log files for details.

JPS-10621: PD Lock not found
Category:: Security
Cause:: PD Lock node not found.
Action:: Refer to the log files for details.

JPS-10622: Invalid PD Lock update time {0}.
Category:: Security
Cause:: Invalid PD Lock update time stamp.
Action:: Refer to the log files for details.

JPS-10623: PD is running in another Admin, please distribute policy after the process finished.
Category:: Security
Cause:: PD is running in another Admin, please distribute policy after the process finished.
Action:: Refer to the log files for details.

JPS-10624: Failed to connect primary server, try secondary server.
Category:: Security
Cause:: Failed to connect primary server, try secondary server.
Action:: Refer to the log files for details.

JPS-10625: Failed to read from the local cache. The cache will be removed. Reason: {0}
Category:: Security
Cause:: Failed to read from the local cache. The cache will be removed.
Action:: Refer to the log files for details.

JPS-10626: Encryption/Decryption of the local cache file using the algorithm {0} is not supported.
Category:: Security
Cause:: The specified algorithm for local cache encryption/decryption is not supported.
Action:: Please check PDP service configuration in jps-config.xml file.

JPS-10627: The key length used to initialize cipher {0} is not valid. Expected key length is {1} bits, but raw key length is {2} bits.
Category:: Security
Cause:: The key length used to initialize cipher is not valid.
Action:: Refer to the log files for details.

JPS-10628: Retry {0} for the {1} times.
Category:: Security
Cause:: Retry {0} for the {1} times.
Action:: No actions are required

JPS-10629: SUCCESS: Retry {0} successfully after {1} times retries.
Category:: Security
Cause:: SUCCESS: Retry {0} successfully after {1} times retries.
Action:: No actions are required

JPS-10630: The default DB policy store is missing for mixed mode.
Category:: Security
Cause:: The default DB policy store is missing for mixed mode.
Action:: Configure one DB policy store instance.

JPS-10631: Failed to distribute policy to Real Application Security Database, target RAS database {0}, exception {1}.
Category:: Security
Cause:: Failed to distribute policy to Real Application Security Database
Action:: Refer to the log files for details.

JPS-10632: Failed to obtain the datasource for Real Application Security Database, target RAS database {0}, exception {1}
Category:: Security
Cause:: Failed to obtain the datasource for Real Application Security Database
Action:: Refer to the log files for details.

JPS-10633: Failed to fetch the information from the intermediate table, target RAS database {0}, exception {1}"
Category:: Security
Cause:: Failed to fetch the information from the intermediate table
Action:: Refer to the log files for details.

JPS-10634: Failed to prepare data for distributing policy to Real Application Security Database, application name {0}, exception {1}.
Category:: Security
Cause:: Failed to prepare data for distributing policy to Real Application Security Database
Action:: Refer to the log files for details.

JPS-10635: Failed to update the intermediate table in the policy store database, target RAS database {0}, exception {1}.
Category:: Security
Cause:: Failed to update the intermediate table in the policy store database
Action:: Refer to the log files for details.

JPS-10636: Incorrect Real Application Security PDP address format.
Category:: Security
Cause:: Incorrect Real Application Security PDP address format
Action:: Refer to the log files for details. The correct format should start with "ras:"

JPS-10700: The value of attribute {0} should be unique
Category:: Security
Cause:: The unique attribute has duplicated values.
Action:: Keep attribute value unique.

JPS-10701: Data Source lookup failure. It is safe to ignore the warning during Websphere server starts up. If you still get the warning after WebSphere server starts up, check your configuration.
Category:: Security
Cause:: Websphere data source lookup failure.
Action:: Safe to ignore during WebSphere starts up.

JPS-10702: The datasource {0} is not found.
Category:: Security
Cause:: Given datasource jndi name is not found.
Action:: Check datasource jndi name.

JPS-10750: Application Policy unique name: "{0}" is invalid
Category:: Security
Cause:: The application policy unique name is invalid
Action:: Refer to the log files for details.

JPS-10751: The version number of Application policy : "{0}" is invalid
Category:: Security
Cause:: The application policy version number is invalid
Action:: Refer to the log files for details.

JPS-10752: The policy entry unique name: "{0}" is invalid
Category:: Security
Cause:: The policy entry unique name is invalid
Action:: Refer to the log files for details.

JPS-10800: The role policy object "{0}" does not exist.
Category:: Security
Cause:: The role policy object does not exist.
Action:: Check if the target role policy exists.

JPS-10801: The role policy object "{0}" already exists.
Category:: Security
Cause:: The policy object exists.
Action:: Create a policy with a different name.

JPS-10802: Application role hierarchy cannot participate in a role mapping policy.
Category:: Security
Cause:: One or more principals in the role mapping policy are of type: ApplicationRole or AnonymousRole or AuthenticatedRole or and AdminRole.
Action:: Identify the principal type in the incomming principals, and ensure only a user or group principal type is supplied.

JPS-10803: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.
Category:: Security
Cause:: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.
Action:: Ensure that resource(s)/resource name expression(s) are not permission based.

JPS-10804: The advice {0} already exists.
Category:: Security
Cause:: The advice already exists in the policy entry.
Action:: Check AdviceEntry passed in.

JPS-10850: The SM Config Tool is used to configure the Security Modules for Oracle Entitlements Server Here are the various options that it will accept -smType <java, wls, ws, rmi, was, jboss> -smConfigId <config id of sm is always required> -serverLocation <in case of was, wls, jboss, this is the location of the server> -pdServer OES Admin Server hostName -pdPort SSL Port for OES Admin Server -pdClientPort SSL Port for WLS SM client -serverNodeName - server node name of websphere -serverName - server instance name of websphere -serverUserName - user name of application server -serverPassword - password of application server -prpFileName - path for the prp file used.
Category:: Security
Cause:: When help is asked for
Action:: Help message, no action required

JPS-10851: Please enter a value for {0}:
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10852: Configuring for PDP proxy mode
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10853: Configuring for Controlled Policy Distribution Mode
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10854: Configuring for Direct Connection to the Database Policy Store
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10855: Configuring for Direct Connection to the Ldap Policy Store
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10856: Configuring for Direct Connection to the Derby Policy Store
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10857: Value is missing or corrupt {0}. Please supply an appropriate value.
Category:: Security
Cause:: Error Message
Action:: Please supply the required parameters as specified in the message.

JPS-10858: Security Module configuration is created at: {0}
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10859: Please re-enter a value for {0}:
Category:: Security
Cause:: Prompt Message
Action:: Prompt message, no action required

JPS-10890: sys_obj_q
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10891: Full qualified resource name on which the query is performed: /foo/bar
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10892: sys_subjectroles
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10893: List of unqualified role names granted to user for current request
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10900: The enrollment response is truncated.
Category:: Security
Cause:: Enrollment response is truncated.
Action:: Refer to the log files for details.

JPS-10901: Keystore {0} does not exist.
Category:: Security
Cause:: Keystore {0} does not exist.
Action:: Check the file system.

JPS-10902: Enrollment server error.
Category:: Security
Cause:: Enrollment server error.
Action:: Check enrollment server status.

JPS-10903: Enrollment is proceeded successfully.
Category:: Security
Cause:: Enrollment is proceeded successfully.
Action:: Prompt message, no action required

JPS-10904: Enrollment is not proceeded successfully.
Category:: Security
Cause:: Enrollment is not proceeded successfully.
Action:: Prompt message, no action required

JPS-10905: The program works in console mode only.
Category:: Security
Cause:: The program works in console mode only.
Action:: Prompt message, no action required

JPS-10906: Enter password for {0}:
Category:: Security
Cause:: Enter password for {0}:
Action:: Prompt message, no action required

JPS-10907: Enter password for {0} again:
Category:: Security
Cause:: Enter password for {0} again:
Action:: Prompt message, no action required

JPS-10908: The passwords you inputted do not match.
Category:: Security
Cause:: The passwords you inputted do not match.
Action:: Prompt message, no action required

JPS-10909: Passwords are saved in credential store.
Category:: Security
Cause:: Passwords are saved in credential store.
Action:: Prompt message, no action required

JPS-10910: Passwords are not saved in credential store.
Category:: Security
Cause:: Passwords are not saved in credential store.
Action:: Prompt message, no action required

JPS-10911: {0} is not set.
Category:: Security
Cause:: {0} is not set.
Action:: Prompt message, no action required

JPS-10912: Keystores are initialized successfully.
Category:: Security
Cause:: Keystores are initialized successfully.
Action:: Prompt message, no action required

JPS-10913: Keystores are not initialized successfully.
Category:: Security
Cause:: Keystores are not initialized successfully.
Action:: Prompt message, no action required

JPS-10914: Enter username for {0}:
Category:: Security
Cause:: Enter username for {0}:
Action:: Prompt message, no action required

JPS-10915: Enter credential map name:
Category:: Security
Cause:: Enter credential map name:
Action:: Prompt message, no action required

JPS-10916: Enter credential key name:
Category:: Security
Cause:: Enter credential key name:
Action:: Prompt message, no action required

JPS-10917: Input password can not be null.
Category:: Security
Cause:: The passwords you inputted can not be null.
Action:: Prompt message, no action required

JPS-10920: function: urn:oasis:names:tc:xacml:1.0:function:integer-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10921: function: urn:oasis:names:tc:xacml:1.0:function:date-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10922: function: urn:oasis:names:tc:xacml:1.0:function:time-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10923: function: urn:oasis:names:tc:xacml:1.0:function:string-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10924: function: urn:oasis:names:tc:xacml:1.0:function:integer-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10925: function: urn:oasis:names:tc:xacml:1.0:function:date-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10926: function: urn:oasis:names:tc:xacml:1.0:function:time-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10927: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10928: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10929: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10930: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10931: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10932: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10933: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10934: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10935: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10936: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10937: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10938: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10939: function: urn:oasis:names:tc:xacml:1.0:function:string-regexp-match The LHS should be a single-value string type attribute/value. The RHS should be a single value string which complies with Java Regular Expression.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10940: function: urn:oasis:names:tc:xacml:1.0:function:or The function stands for an OR operation between two single-value boolean expressions/values.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10941: function: urn:oasis:names:tc:xacml:1.0:function:and The function stands for an AND operation between two single-value boolean expressions/values.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10942: function: urn:oasis:names:tc:xacml:1.0:function:not The function stands for a NOT operation on a single-value boolean expression/value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10943: function: valid_for_mseconds The function accepts a single integer value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10944: function: valid_for_seconds The function accepts a single integer value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10945: function: valid_for_minutes The function accepts a single integer value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10946: function: valid_for_hours The function accepts a single integer value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10947: function: valid_until_time The function accepts a single time value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10948: function: valid_until_date The function accepts a single date value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10949: function: sys_defined The function accepts a single string value.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10950: current_gmt_time
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10951: current_gmt_date
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10952: sys_subjectgroups
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10953: sys_user
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10954: sys_app
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10955: sys_obj_type
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10956: sys_obj
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10957: sys_privilege
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10958: boolean_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10959: string_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10960: integer_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10961: date_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10962: time_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10963: string_is_in
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10964: integer_is_in
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10965: date_is_in
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10966: time_is_in
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10967: integer_greater_than
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10968: integer_greater_than_or_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10969: integer_less_than
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10970: integer_less_than_or_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10971: time_greater_than
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10972: time_greater_than_or_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10973: time_less_than
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10974: time_less_than_or_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10975: date_greater_than
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10976: date_greater_than_or_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10977: date_less_than
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10978: date_less_than_or_equal
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10979: string_regexp_match
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10980: or
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10981: and
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10982: not
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10983: valid_for_mseconds
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10984: valid_for_seconds
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10985: valid_for_minutes
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10986: valid_for_hours
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10987: valid_until_time
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10988: valid_until_date
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10989: attribute_has_value
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10990: The attribute will be assigned current time value n GMT time zone during evaluation
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10991: The attribute will be assigned current date value n GMT time zone during evaluation
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10992: List of unqualified group names to which user belongs: ["admin", "managers"]
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10993: Current user: unqualified form: system
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10994: Unqualified name of the binding resource for the resource on which the query is performed: admin
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10995: ResourceType on which the query is performed: LibraryResourceType
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10996: Resource on which the query is performed: bar
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10997: Unqualified name of the action on which the resource is being queried.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10998: function: urn:oasis:names:tc:xacml:1.0:function:boolean-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side);If LHS or RHS is a multiple value attribute and the other side is single value attribute,the function returns false;If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-10999: function: urn:oasis:names:tc:xacml:1.0:function:string-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.
Category:: Security
Cause:: built-in attribute/function display name and desription
Action:: Prompt message, no action required

JPS-11000: Policy Set member with type: "{0}" and name "{1}" does not exist
Category:: Security
Cause:: The policy set member does not exist in policy store
Action:: Refer to the log files for details.

JPS-11001: Can not delete policy set "{0}" which is referred by other policy set
Category:: Security
Cause:: The policy set to be deleted is referred by other policy set
Action:: Refer to the log files for details.

JPS-11002: Policy set dependency loop could be introduced by modifyPolicySet operation
Category:: Security
Cause:: The policy set depdency could be introduced by modifyPolicySet operation
Action:: Refer to the log files for details.

JPS-11003: Policy set "{0}" does not exist
Category:: Security
Cause:: The policy set entry with specified name does not exist in policy store
Action:: Refer to the log files for details.

JPS-11004: Multiple principal entries provided have principal constraint
Category:: Security
Cause:: Multiple principal entries have principal constraint
Action:: Refer to the log files for details.

JPS-11005: Can not add AllResource to permission set: "{0}"
Category:: Security
Cause:: Adding AllResource to Permission set is not supported
Action:: Refer to the log files for details.

JPS-11006: Adding {0} combiner parameters for {0} "{1}" not referred in this policy set
Category:: Security
Cause:: Adding policy or policy set combiner paramers for policy or policy set not referred in this policy set
Action:: Refer to the log files for details.

JPS-11007: Can not add codesource, principals, resource actions or permission sets to {0}: "{1}" which has XACML3 target
Category:: Security
Cause:: Adding codesource, principals, resource actions or permissin sets to policy, policy set or rule which has XACML3 target
Action:: Refer to the log files for details.

JPS-11008: Can not add XACML3 target to {0}: "{1}" which has codesource, principals, resource actions or permission sets
Category:: Security
Cause:: Adding XACML3 target to policy, policy set or rule which has codesource, principals, resource actions or permissin sets
Action:: Refer to the log files for details.

JPS-11009: Policy set "{0}" already exists
Category:: Security
Cause:: The policy set entry with specified name already exists in the policy store
Action:: Refer to the log files for details.

JPS-12000: No such Configuration Profile "{0}" exists in the system.
Category:: Configuration
Cause:: The specified configuration profile is not registered with configuration service.
Action:: Check the name, or try listing the registered profiles.

JPS-12001: Cannot create ContextConfiguration, A JPS Context with name "{0}" already exists in the system.
Category:: Configuration
Cause:: A jpsContext with the specified contextId exists in the system.
Action:: Use another unique contextId.

JPS-12002: Could not Construct the ConfigurationManagementService: Configuration Context Descriptor NOT FOUND in jps-config.xml or specifies an invalid Configuration serviceInstance descriptor.
Category:: Configuration
Cause:: A jpsContext by the name "ConfigContext" that references a Configuration Service Instance Descriptor is missing from jps-config.xml.
Action:: Check the MultiTenancy Enablement steps and/or scripts.

JPS-12003: Could not Construct ConfigurationManagementService from its Descriptor in jps-config.xml, due to empty/missing configuration data in the Descriptor.
Category:: Configuration
Cause:: The configuration jpsContext does seem to contain a <serviceInstanceRef> pointing to the ConfigurationManagementService instance descriptor.
Action:: Check the MultiTenancy Enablement steps and/or scripts.

JPS-12004: No such JpsContext "{0}" exists in jps-config.xml.
Category:: Configuration
Cause:: A jpsContext with the specified contextId does not exists in the system.
Action:: Check jps-config.xml of the domain.

JPS-12005: A ContextConfiguration with "{0}" "{1}" already exists in the system.
Category:: Data
Cause:: A ContextConfiguration with the specified name already exists.
Action:: Use another unique name.

JPS-12006: No Registered ContextConfiguration with "{0}" "{1}" exists in the system.
Category:: Data
Cause:: The specified configuration profile is not registered with configuration service.
Action:: Check the name, or try listing the registered profiles.

JPS-12007: Cannot delete ContextConfiguration "{0}" in "{1}" state.
Category:: Data
Cause:: A ContextConfiguration in ACTIVE state cannot be deleted.
Action:: DeActivate the context and then try deleting it.

JPS-12008: Cannot DeActivate ContextConfiguration "{0}" as it is in state "{1}".
Category:: Data
Cause:: A ContextConfiguration ACTIVE state (only) can be DeActivated. DeActivation from other states is illegal.
Action:: Make sure the context configuration is ACTIVE and then try deactivating it.

JPS-12009: Cannot Activate ContextConfiguration "{0}" as it is in state "{1}".
Category:: Data
Cause:: A ContextConfiguration must be in COMPLETE or INACTIVE state for Activation to succeed.
Action:: Check to make sure the state of the Context is COMPLETE or INACTIVE.

JPS-12010: Cannot Update ContextConfiguration "{0}" as it is in state "{1}".
Category:: Data
Cause:: A ContextConfiguration must be in CREATED or INACTIVE state before it can be UPDATED.
Action:: Check to make sure the state of the Context is CREATED or INACTIVE. A configuration in COMPLETE or ACTIVE states cannot be updated

JPS-12011: OPSS Runtime Cannot fetch Configuration for context "{0}", The context does not exist or is not in ACTIVE state.
Category:: Data
Cause:: OPSS Runtime failed to fetch the Configuration for the context. Either the context does not exist or is not in ACTIVE state. The Runtime can only view ContextConfigurations in ACTIVE state
Action:: Check to make sure the Context exists and is in ACTIVE state.

JPS-12012: Cannot initialize Configuration Store : One of DataSource/JDBC-URL/FilePath for MetaDataStore should be Configured in the Configuration Service Descriptor.
Category:: Configuration
Cause:: The configuration serviceInstance descriptor does not seem to contain a property for DataSource/JDBC-URL/FilePath for connecting to the Configuration Store.
Action:: Check MultiTenancy enablement steps/scripts.

JPS-12013: File based Configuration Store should be used only for Development and not in Production.
Category:: Configuration
Cause:: File based Configuration Store should be used only for Testing and not in Production.
Action:: Nothing to do if this is a Test Environment, else check Multi-Tenancy enablement steps.

JPS-12014: Map/Key name(s) for Credential required to bind to MetaDataStore with JDBC-URL not configured in the Configuration Service.
Category:: Configuration
Cause:: A Password Credential is required when JDBC-URL is used to connect to the Configuration Store.
Action:: Check to see that the Configuration serviceInstance descriptor contains properties for the Map and Key name of the credential.

JPS-12015: Property JPS_CONFIG_PATH not set for use by PersistenceManager.
Category:: Process
Cause:: Internal Error/Bug: The Configuration Management Service is expected to set a property JPS.CONFIGSERVICE.PATH for use by the PersistenceManager.
Action:: Report Bug on Oracle OPSS with relevant logs.

JPS-12016: Internal Error: Unable to locate ContextConfiguration named "{0}" in the Configuration Profile "{1}".
Category:: Process
Cause:: Internal Error/Bug: The Configuration Service is in a state where it thinks the specified contextId should exist under the specified profileId, but the persisted information in the store does not match the expectation.
Action:: Report Bug on Oracle OPSS with relevant logs.

JPS-12017: Invalid Xpath expression , specified XPath "{0}" does not evaluate to a "{1}".
Category:: Data
Cause:: The XPath expression specified in Customization spec does not point to the intended element in the Configuration Profile document.
Action:: Check the XPath expression against the structure of the configuration Profile being referenced..

JPS-12018: Invalid Location Override in Global Scope. Location Override can be specified for ServiceInstances only.
Category:: Data
Cause:: The Location Override in Customization spec is only applicable to a serviceInstance attribute and cannot be applied to an element in Global Scope.
Action:: Check the XPath expression.

JPS-12019: Cannot apply "{0}" overrides on element of type "{1}", expected an element of type "{2}", check the Element XPath specified in the customization.
Category:: Data
Cause:: The XPath expression specified in Customization spec does not point to the intended element in the Configuration Profile document.
Action:: Check the XPath expression against the structure of the configuration Profile being referenced..

JPS-12020: Cannot modify values of existing ExtendedProperty elements during customization.
Category:: Data
Cause:: Cannot modify values of existing ExtendedProperty elements during customization.
Action:: This is an Unsupported Customization spec, change the customization instructions supplied to the Configuration Management Service.

JPS-12021: Cannot create ContextConfiguration "{0}", No such profile "{1}" exists in the system.
Category:: Data
Cause:: Cannot create ContextConfiguration as the referenced Configuration Profile does not seem to exist.
Action:: Check the name of the specified profile.

JPS-12022: MetaDataObject "{0}" not found. Ensure ContextConfiguration "{1}" exists or first create it.
Category:: Configuration
Cause:: The PersistenceManager is unable to find the MetaDataObject corresponding to the specified contextId.
Action:: Check the name of the context or make sure it is registered with the Configuration Service.

JPS-12023: Mutable MetadataObject "{0}" cannot be obtained from MetadataStore specified since there are pending writes to other MetadataStores. Do flushChanges/cancelChanges on MDSSession to proceed.
Category:: Process
Cause:: Internal Error/Bug : The persistence manager is in a state where it is trying to perform multiple updates to the profile document concurrently.
Action:: Report a Bug on Oracle OPSS with relevant logs.

JPS-12024: A profile with name "{0}" already exists.
Category:: Data
Cause:: A configuration profile with the given name already exists.
Action:: Try using a unique profileId.

JPS-12025: Cannot Delete Profile "{0}" ,Named ContextConfigurations exist under the profile.
Category:: Data
Cause:: A configuration profile which has named ContextConfiguration's referencing it cannot be deleted.
Action:: Try deleting the ContextConfiguration's before attempting to delete the profile.

JPS-12026: No such ContextConfiguration "{0}" exists in the system.
Category:: Data
Cause:: The specified ContextConfiguration is not registered with the Configuration Service.
Action:: Check the name or try listing the registered ContextConfigurations.

JPS-12027: Required PasswordCredential at Map = "{0}",Key = "{1}" was not found in Specified Bootstrap CredentialStore.
Category:: Configuration
Cause:: A required PasswordCredential does not exist at the specified map, and key in the supplied bootstrap credential store.
Action:: Check the bootstrap credential store.

JPS-12028: Malformed jps-config.xml : stale service instance reference "{0}" from JpsContext.
Category:: Configuration
Cause:: The PersistenceManager found a STALE <serviceInstanceRef> that does not exist in the jps-config.xml.
Action:: Check the jps-config.xml of the Profile or the Out-of-the-Box jps-config.xml as appropriate.

JPS-12029: Cannot set Name for ContextConfiguration "{0}" in state "{1}", deactivate it first.
Category:: Data
Cause:: Cannot set contextName for a ContextConfiguration in ACTIVE.
Action:: DeActivate it first and then set a Name for it.

JPS-12030: Cannot setContextName, ConfigurationContext "{0}" is already Named "{1}", unset the Name first.
Category:: Data
Cause:: A ContextConfiguration that is already has a Name cannot be Named again.
Action:: Unset the current Name first and then set a new Name for it.

JPS-12031: Cannot unset Name for ContextConfiguration "{0}" in state "{1}", deactivate it first.
Category:: Data
Cause:: Cannot unset the contextName for a ContextConfiguration in ACTIVE state.
Action:: DeActivate the Context first and then unset the contextName.

JPS-12032: Error in initializing JAXBContext.
Category:: Configuration
Cause:: Internal Error: JAXB context initialization in PersistenceManager Failed.
Action:: Report a Bug on Oracle OPSS with relevant logs.

JPS-12033: Invalid profile jps-config.xml document, does not contain a required element "{0}".
Category:: Configuration
Cause:: Internal Error: the profile document does not contain a mandatory element.
Action:: Check the jps-config.xml that was used as a Configuration Profile.

JPS-12034: MDSPersistenceManager Cannot handle Persistence of Element "{0}".
Category:: Configuration
Cause:: Unsupported operation : The persistence manager configured with the Configuration Service does not handle persistence of the specified element.
Action:: Report a Bug on Oracle OPSS with relevant logs.

JPS-12035: Cannot setContextName for ConfigurationContext "{0}" to Name "{1}", as the Name is already assigned to "{2}".
Category:: Data
Cause:: Names used for ContextConfiguration must be unique, an attempt is being made to set the same Name for more than one ContextConfiguration.
Action:: Use a different unique Name.

JPS-12036: ContextConfiguration "{0}" does not have any name set for it, Naming a ContextConfiguration is mandatory before its configuration STATE can be set to COMPLETE.
Category:: Data
Cause:: An attempt is being made to set the STATE of an Un-Named ContextConfiguraton to COMPLETE.
Action:: Use the setContextName(contextId) method to set a Name.

JPS-12037: Service configuration update done for Configurator.
Category:: Data
Cause:: Service configuration update done for Configurator.
Action:: No action required.

JPS-12038: Failed to check if audit is enabled.
Category:: Configuration
Cause:: Configuration management events logging was not enabled.
Action:: Check the audit configuration to ensure auditing enabled.

JPS-12039: Failed to log audit record.
Category:: Configuration
Cause:: Configuration management audit event logging failed.
Action:: Contact the administrator.

JPS-12040: Missing Property set props.db.1.
Category:: Configuration
Cause:: No Prorperty Set props.db.1 in jps-config.xml
Action:: Check the jps-config.xml.

JPS-12100: The expiry time should be in format {0}
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input.

JPS-12101: The filter value is {0} invalid
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input.

JPS-12102: One of the attributes {0} is undefined
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input.

JPS-12103: Parameter {0} is missing
Category:: Configuration
Cause:: Missing Parameter
Action:: Correct the input.

JPS-12104: Alias {0} did not exist or point to a key
Category:: Configuration
Cause:: Alias did not exist or point to a key
Action:: Correct the input Alias.

JPS-12105: Tenant with id {0} does not exist.
Category:: Configuration
Cause:: Tenant does not exist
Action:: Correct the tenant id.

JPS-12106: The param {0} is invalid - null or empty.
Category:: Configuration
Cause:: Tenant config parameter passed to the API is invalid
Action:: Make sure all parameters are valid

JPS-12107: The param {0} was supplied a restricted value {1}.
Category:: Configuration
Cause:: Tenant config parameter value passed to the API is restricted
Action:: Make sure no restricted values are used

JPS-12109: It is invalid that both of "{0}" and "{1}" are null or empty.
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure at least one of them is not null or empty

JPS-12110: It is invalid that both of "{0}" and "{1}" have value.
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure only one of them is not null or empty

JPS-12111: It is invalid that "{0}" is less than "{1}".
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure the data is reasonable

JPS-12112: It is invalid that "{0}" is less than or equal to "{1}".
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure the data is reasonable

JPS-12113: Property "{0}" cannot be updated/modified.
Category:: Configuration
Cause:: Unmodifiable property
Action:: Correct the input, make sure the data is reasonable

JPS-12114: Cannot specifify resource name delimiter for non-hierachical resource type
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure the data is reasonable

JPS-12115: "{0}" is an invalid resource name delimiter character. Valid characters are [/ \ $ # : ; , ! . - _ @ |]
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure the data is reasonable

JPS-12116: For the attribute "{0}", "{1}" is not a valid value.
Category:: Configuration
Cause:: Invalid input
Action:: Correct the input, make sure the data is reasonable

JPS-12117: Cannot set multiple values to a single value attribute "{0}".
Category:: Configuration
Cause:: Set multi values to a single value attribute
Action:: Correct the input, make sure the data is reasonable

JPS-20000: GlobalPolicy can not be created by MAPI methods
Category:: Programmatic
Cause:: GlobalPolicy can not be created by MAPI methods.
Action:: Set up policy store using reassociation or upgrading

JPS-20001: GlobalPolicy can not be deleted by MAPI methods.
Category:: Programmatic
Cause:: GlobalPolicy can not be deleted by MAPI methods.
Action:: GlobalPolicy is a built-in stripe, can not be deleted

JPS-20002: GlobalPolicy can not be returned from the method.
Category:: Programmatic
Cause:: GlobalPolicy can not be returned from the method.
Action:: Gets GlobalPolicy from the method getGlobalPolicy

JPS-20003: Cannot add global role to application role
Category:: Security
Cause:: Attempted to add a global role {0} to members of an application role or grant a global role {0} to an applicaton role
Action:: Do not add a global role to members of an application role and do not grant a global role to an application role.

JPS-20004: Principals can not contain global role.
Category:: Security
Cause:: Principals contain global role {0}
Action:: Remove global role from principals.

JPS-20005: Cannot delete global role "{0}".
Category:: Security
Cause:: Global role "{0}" is referenced in a Policy defined in an Application.
Action:: Make sure the global role is not referenced in any application policy,then remove it.

JPS-20006: Authorization policy is not supported in global policy.
Category:: Security
Cause:: Authorization policy is not supported in global policy.
Action:: Do not create authorization policies in global policy.

JPS-20007: Permission grant is not supported in global policy
Category:: Security
Cause:: Permission grant is not supported in global policy.
Action:: Do not grant permissions in global policy

JPS-20008: {0} : {1} in global policy which are referenced in application have been changed but not distributed
Category:: Security
Cause:: {0} : {1} in global policy which are referenced in application have been changed but not distributed.
Action:: Distribute global policy firstly

JPS-20010: Attribute name {0} already exist in {1}.
Category:: Programmatic
Cause:: Attribute name {0} already exist in {1}
Action:: Choose another name

JPS-20011: Function name {0} already exist in {1}.
Category:: Programmatic
Cause:: Function name {0} already exist in {1}
Action:: Choose another name

JPS-20012: Global attribute {0} is used in application {1}.
Category:: Programmatic
Cause:: Global attribute {0} is used in application policy {1}
Action:: Make sure the global attribute is not used in any applications including global policy

JPS-20013: Global function {0} is used in application {1}.
Category:: Programmatic
Cause:: Global function {0} is used in application policy {1}
Action:: Make sure the global function is not used in any applications including global policy

JPS-20014: Policy domain is not supported in global policy
Category:: Security
Cause:: Policy domain is not supported in global policy.
Action:: Do not use policy domain in global policy

JPS-20020: Resource type name {0} already exists in application {1}.
Category:: Programmatic
Cause:: Resource type name {0} already exists in application {1}
Action:: Choose another name

JPS-20021: Global resource type {0} is used in application {1}.
Category:: Programmatic
Cause:: Resource type {0} is used in application {1}
Action:: Make sure global resource type is not used in any application

JPS-20022: Global policy can not be unbound from SM
Category:: Programmatic
Cause:: Global policy can not be unbound from SM
Action:: Do not unbind global policy from SM

JPS-20050: Combining algorithm {0} not found.
Category:: Programmatic
Cause:: Combining algorithm not found.
Action:: Make sure the used combining algorithm exists.

JPS-20051: Exception in converting execution frequency {0}, message is {1}
Category:: Programmatic
Cause:: Exception in converting value of algorithm execution frequency.
Action:: Make sure the execution frequency is valid.

JPS-20052: Exception in converting algorithm usage {0}, message is {1}
Category:: Programmatic
Cause:: Exception in converting value of algorithm usage.
Action:: Make sure the usage is valid.

JPS-20053: A combining algorithm must be provided if policy is using more than one rule.
Category:: Programmatic
Cause:: Policy uses multiple rules, but no combining algorithm provided.
Action:: Provide a combining algorithm.

JPS-20054: A acl match type must be provided if policy is a RAS one.
Category:: Programmatic
Cause:: RAS policy has no acl match type to be provided.
Action:: Provide a ACL Match Type.

JPS-20055: A list of RAS policy rule must be provided if policy is a RAS one.
Category:: Programmatic
Cause:: RAS policy has no policy rule to be provided.
Action:: Provide policy rule(s).

JPS-20056: A list of RAS resource must be provided if policy is a RAS one.
Category:: Programmatic
Cause:: RAS policy has no resource to be provided.
Action:: Provide resource(s).

JPS-20060: Number of input parameters to the function and provided value types for them are not of same size.
Category:: Programmatic
Cause:: Number of input parameters to the function and provided value types for them are not of same size.
Action:: Parameter value types, if provided, must be provided for all input parameters

JPS-20061: Value collection added to expression is null.
Category:: Programmatic
Cause:: Value collection added to expression is null.
Action:: Provide a non-nulll collection of values to expression.

JPS-20062: Value collection passed to input parameter when a single object is expected.
Category:: Programmatic
Cause:: Value collection passed to input parameter when a single object is expected.
Action:: Provide a single object as input parameter.

JPS-20063: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.
Category:: Programmatic
Cause:: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.
Action:: Provide correct type of collection as function input parameter.

JPS-20064: Function {0} is unknown.
Category:: Programmatic
Cause:: Function {0} is unknown.
Action:: Provide correct function.

JPS-20070: In mixed mode, PDP configuration id could not be null
Category:: Programmatic
Cause:: PDP configuration id is missing.
Action:: Specify the PDP configuration id

JPS-20100: Rules {0} for policy {1} is in use by other policies. It will not be deleted.
Category:: Security
Cause:: Rule {0} of policy {1} is shared by other policies.
Action:: Provide correct Rule.

JPS-20101: Policy {0} is referred by one or more policy sets. It can not be deleted if cascading is set to false.
Category:: Security
Cause:: Policy {0} is referred by other policie sets.
Action:: Either use cascading delete or remove references from policy sets.

JPS-20102: Rule {0} used in policy is not sharable. The policy will not be created or updated.
Category:: Security
Cause:: Rule {0} used in policy is not sharable.
Action:: Provide correct Rule.

JPS-20103: Policy can not have both private rules and sharable rules.
Category:: Security
Cause:: Policy can not have both private rules and sharable rules.
Action:: Provide correct Rule.

JPS-20104: Exclusive rule {0} can not be deleted explicitly.
Category:: Security
Cause:: Exclusive rule {0} can not be deleted explicitly.
Action:: Delete the referred policy.

JPS-20105: The permission {0} has no target name.
Category:: Programmatic
Cause:: Permission has no target name.
Action:: Make sure the usage is valid.If not revoke the permission.

JPS-20200: Adding attributes to data security resource type {0} is not allowed.
Category:: Security
Cause:: Attributes present in Data Security Resource Type.
Action:: Remove Attributes present in Data Security Resource Type.

JPS-20201: Adding matcher class to data security resource type {0} is not allowed.
Category:: Security
Cause:: Matcher Class present in Data Security Resource Type.
Action:: Remove Matcher Class present in Data Security Resource Type.

JPS-20202: Hierarchical data security resource type {0} is not allowed.
Category:: Security
Cause:: Data Security Resource Type is Hierarchial.
Action:: Change Data Security Resource Type to Flat. It cannot be Hierarchial.

JPS-20203: Adding both actions and action collection references to data security resource type {0} is not allowed.
Category:: Security
Cause:: Both Actions and Action Collection References are added to Data Security Resource Type.
Action:: Add either Actions or Action Collection References to Data Security Resource Type.

JPS-20204: Adding null data security information object to data security resource type {0} is not allowed.
Category:: Security
Cause:: Null data security information object found for data security resource type.
Action:: Add data security information object to data security resource type.

JPS-20205: Data source name is required for a data security resource type {0}.
Category:: Security
Cause:: Data security information object found for data security resource type has no data source name.
Action:: Provide valid data source name for data security information object for data security resource type.

JPS-20206: Invalid value for data source type of data security resource type {0}.
Category:: Security
Cause:: Data security information object found for data security resource type has invalid data source type.
Action:: Data Security information object found for data security resource type has invalid data source type

JPS-20207: Constraint required for data security resource type {0} as data source type is virtual.
Category:: Security
Cause:: Virtual data source type requires data source constraint to be present.
Action:: Provide valid data source constraint for virtual data source.

JPS-20208: Actions List cannot contain actions that are inherited by default for resource type {0}.
Category:: Security
Cause:: Actions list in resource type contains default inherited data security actions.
Action:: Remove default data security actions from data security resource type.

JPS-20209: Duplicate column definition (same column names) not allowed in data source of resource type {0}.
Category:: Security
Cause:: Duplicate column definition (same names) in secured data source in resource type.
Action:: Remove duplicate column definition from secured data source.

JPS-20210: Action collection reference name {1} referred in resource type {0} not found in policy store.
Category:: Security
Cause:: Action collection reference in resource type not found in the policy store.
Action:: Either create action collection in store or remove the reference from resource type.

JPS-20220: Data Security Resource Type should be present for Data Security Resource {0}.
Category:: Security
Cause:: No RAS resource type present for RAS resource OR is not of type RAS resource type.
Action:: Add RAS resource type for RAS resource.

JPS-20221: For data security resource {0} SQL predicate or XML expression is required.
Category:: Security
Cause:: Both SQL predicate and XML expression missing in data security resource.
Action:: Add either SQL Predicate or XML expression to data security resource.

JPS-20240: Multiple rules not allowed for triton policy {0}.
Category:: Security
Cause:: Multiple rules in triton data security policy.
Action:: Add only one rule to triton data security policy.

JPS-20241: Data security policy {0} has invalid type {1} and category {2}.
Category:: Security
Cause:: Invalid policy category and type combination.
Action:: Provide valid policy category and type combination.

JPS-20242: RAS policy only takes resources with same resource type.
Category:: Security
Cause:: RAS Policy have resources with different resource types.
Action:: Provide resources just with same resource type for RAS policy.

JPS-20243: For RASParameterValue, only EXACT matcher is supported.
Category:: Security
Cause:: Search RAS Policy by RASParameterValue ONLY support MATCHER.EXACT.
Action:: Use MATCHER.EXACT for search by RASParameterValue.

JPS-20244: For RASParameterValue, only EQUALITY comparator is supported.
Category:: Security
Cause:: Search RAS Policy by RASParameterValue ONLY support COMPARATOR.EQUALITY.
Action:: Use COMPARATOR.EQUALITY for search by RASParameterValue.

JPS-20260: RAS Resource type name referred in RAS policy set {0} is Null.
Category:: Security
Cause:: RAS resource type reference in RAS policy set is Null.
Action:: Either create given resource type in store beforehand or use an existing one.

JPS-20261: Data security policy set {0} has invalid type {1} and category {2}.
Category:: Security
Cause:: Invalid policy set category and type combination.
Action:: Provide valid policy set category and type combination.

JPS-20262: Policy set {0} is an ACL protecting an Attribute Collection and cannot be deleted.
Category:: Security
Cause:: Attempt to delete ACL that is protecting an Attribute Collection.
Action:: Check that the ACL is not protecting any Attribute Collection.

JPS-20263: RAS Policy set only takes policies whose ras resources are of same ras resource type.
Category:: Security
Cause:: RAS policy set only takes policies whose ras resources are of same ras resource type.
Action:: Use ras policies with same ras resource type for ras policy set.

JPS-20264: The length of RAS {0} name plus the length of RAS application name can not exceed 29.
Category:: Security
Cause:: The length of RAS artifact name plus the length of ras application name exceeds 29.
Action:: Shorten the RAS artifact name

JPS-20265: The name of RAS {0} is allowed to consist of only alphanumeric characters and the special characters $, _, and #, and MUST begin with a letter.
Category:: Security
Cause:: The RAS artifact name is allowed to consist of only alphanumeric characters and the special characters $, _, and #, and MUST begin with a letter.
Action:: Change the RAS artifact name

JPS-20300: The action or implied action "{0}" already exists in action collection "{1}" or its parent(s).
Category:: Security
Cause:: Duplicate action or implied action found in action collection or one of its parents.
Action:: Verify the action and implied action lists of this action collection and its parents.

JPS-20301: The action collection "{0}" is already referenced in action collection "{1}" or its parent(s).
Category:: Security
Cause:: Duplicate action collection reference found in action collection or one of its parents.
Action:: Verify the action collection reference lists of this action collection and its parents.

JPS-20302: The action collection "{0}" already exists in application policy "{1}".
Category:: Security
Cause:: Action collection already exists in the application.
Action:: Verify the action collection in the application or try modify operation.

JPS-20303: The action collection "{0}" was not found in application policy "{1}".
Category:: Security
Cause:: Action collection not found in application.
Action:: Verify the action collection is present in the application.

JPS-20304: The action collection "{0}" is in use by another policy object.
Category:: Security
Cause:: Action collection is in use by another policy object.
Action:: Verify the usages of the action collection.

JPS-20305: Create, modify & delete operations are not permitted on built-in action collection "{0}".
Category:: Security
Cause:: The action collection being deleted, created or modified is built-in in the database.
Action:: Use a different name for the action collection.

JPS-20306: Action {0} referred in implied action {1} is not defined in action collection {2} or any of its parents.
Category:: Security
Cause:: The mapping specified for given implied action is not found in action collection or its parents.
Action:: Check the implied actions mappings.

JPS-20307: The action or implied action "{0}" already exists in implied action "{1}".
Category:: Security
Cause:: The mapping specified for given implied action contains duplicate actions.
Action:: Check the implied actions mappings.

JPS-20308: The implied action "{0}" refers to itself.
Category:: Security
Cause:: The mapping specified for given implied action contains reference to itself.
Action:: Check the implied actions mappings.

JPS-20320: "{0}" is not a RAS target database.
Category:: Security
Cause:: The SM is not a RAS target database.
Action:: make sure the name corresponds to a RAS target database

JPS-20321: "{0}" is not a RAS application.
Category:: Security
Cause:: The application is not a RAS application.
Action:: make sure the name corresponds to a RAS application

JPS-20322: "{0}" is not found or it is not a RAS target database.
Category:: Security
Cause:: RAS target database not found
Action:: make sure the name corresponds to a RAS target database

JPS-20350: All of handlerSchemaName, handlerPackageName and handlerFunctionName must be present or must be null in an attribute collection.
Category:: Security
Cause:: Atleast one of schema name, package name or function name of handler function is null.
Action:: Verify the schema name, package name and function name of handler function.

JPS-20351: The attribute "{0}" already exists in attribute collection "{1}".
Category:: Security
Cause:: Duplicate attribute found in attribute collection.
Action:: Verify the attribute list of this attribute collection and its parents.

JPS-20352: Attributes in attribute collection must be of category DYNAMIC.
Category:: Security
Cause:: Category of added attribute was wrong.
Action:: Verify the added attribute is of category DYNAMIC.

JPS-20353: The attribute collection "{0}" already exists in application policy "{1}".
Category:: Security
Cause:: Attribute collection already exists in the application.
Action:: Verify the attribute collection in the application or try modify operation.

JPS-20354: The attribute collection "{0}" was not found in application policy "{1}".
Category:: Security
Cause:: Attribute collection not found in application.
Action:: Verify the attribute collection is present in the application.

JPS-20355: Attributes in attribute collection must be single-valued.
Category:: Security
Cause:: Multi-valued attributes not supported.
Action:: Verify the added attribute(s) are all single-valued.

JPS-20356: The ACE(Policy Rule) "{0}" is not present in the application.
Category:: Security
Cause:: ACE(policy rule) protecting Attribute collection not found in application.
Action:: Verify the ACE(Policy Rule) is present in the application.

JPS-20357: The attributes in an attribute collection "{0}" is null or empty.
Category:: Security
Cause:: RASAttribute list is null or empty
Action:: Make sure RASAttribute list is not null or empty.

JPS-20400: The definition for attribute "{0}" exists in the application policy with wrong category. Expected: {1}, Found: {2}
Category:: Security
Cause:: Attribute definition exists in application with different category than expected.
Action:: Verify the attribute definition in the application.

JPS-20401: The definition for attribute "{0}" exists in the application policy with wrong type. Expected: {1}, Found: {2}
Category:: Security
Cause:: Attribute definition exists in application with different type than expected.
Action:: Verify the attribute definition in the application.

JPS-20403: Attribute designator functionality is not supported for this schema version.
Category:: Security
Cause:: Attribute designator functionality is not supported for this schema version.
Action:: Don't use designator functionality or upgrade to newer version.

JPS-20411: Invalid match function. Match function for a constraint must take two input parameters, provided function requires {0} input parameters.
Category:: Security
Cause:: Match function for constraint does not take 2 input parameters.
Action:: Provide a corret match function for constraint.

JPS-20412: Invalid match function. Both input parameters to a match function must be of same data type; provided function takes input parameters of type {0} and {1}.
Category:: Security
Cause:: Match function for constraint musts take two input parameters of same data type.
Action:: Provide a correct match function for constraint.

JPS-20413: Invalid match function. First parameter for a match function must be a single value.
Category:: Security
Cause:: Match function for a constraint cannot take bag or set of values.
Action:: Provide a correct match function for constraint.

JPS-20414: Mismatch of attribute category in constraint. Expected {0}, actual {1}.
Category:: Security
Cause:: Category of attribute provided to the constraint must either be dynamic or match the constraint type.
Action:: Provide attribute with correct category type to the constraint.

JPS-20415: The data type {0} of attribute "{1}" does not match data type {2} of function second parameter passed to AttributeValueAssertion.
Category:: Security
Cause:: Attribute data type and expected function parameter data type are different.
Action:: Verify the data type of attribute entry passed to AttributeValueAssertion.

JPS-20416: Data type of value and expected input parameter type of function provided for attribute value assertion does not match. Expected type {0}, provided {1}
Category:: Security
Cause:: Data type of value and expected input parameter type of function provided for attribute value assertion does not match.
Action:: Provide value with correct data type to the constraint.

JPS-20417: Constraints are only supported for TargetEntry and SimpleTargetEntry
Category:: Security
Cause:: Constraints are supported only for TargetEntry and SimpleTargetEntry.
Action:: If a constraint must be used, add it using a TargetEntry or SimpleTargetEntry.

JPS-20420: Function Element is not supported as return type of a function.
Category:: Security
Cause:: Function Element is not supported as return type of a function.
Action:: Provide some other return type.

JPS-20421: Data type for a Function Element input parameter must be OpssString.
Category:: Security
Cause:: Data type for a Function Element input parameter must be OpssString.
Action:: Provide correct data type.

JPS-20422: Function Element not supported for this version of policystore.
Category:: Security
Cause:: Function element not supported for this schema version.
Action:: Don't use function element or upgrade.

JPS-20423: AttributeAssignment can not be defined using a Function Element.
Category:: Security
Cause:: Attribute assignment cannot be defined using a function element.
Action:: Don't use function element.

JPS-20500: Quoted name for {0}, must be terminated by double-quote (").
Category:: Security
Cause:: Quoted id for triton entity needs to be terminated with double-quote(").
Action:: Verify the id provided.

JPS-20501: Length of {0} name must be between 1 and 30 characters (excluding the quotes ("), in case of quoted identifier), but was {1}
Category:: Security
Cause:: Id for triton entity has invalid length.
Action:: Verify the id provided.

JPS-20502: Quoted name for {0} contains invalid character ''{1}'' at position {2}. Quoted names must not contain null character(\0) or double-quote(") within the name
Category:: Security
Cause:: Quoted id for triton entity has invalid character.
Action:: Verify the id provided.

JPS-20503: Unquoted name for {0} contains invalid character ''{1}'' at position {2}. Unquoted names must begin with an alphabet. They may contain a letter, digit, underscore(_), dollar($), hash(#), or dot(.) symbols at other positions.
Category:: Security
Cause:: Unquoted id for triton entity has invalid character.
Action:: Verify the id provided.

JPS-20504: The name "{0}" is an implicit object name in the database and cannot be used as a name for {1}.
Category:: Security
Cause:: Id provided for triton entity is an implicit object name in the database.
Action:: Verify the id provided.

JPS-20505: The value "{0}" is of an unsupported type.
Category:: Security
Cause:: Parameter value is using an invalid type.
Action:: Verify the parameter value provided.

JPS-20521: A simple target must have at least one resource action entry or permission set reference.
Category:: Security
Cause:: A simple target must have at least one resource action entry or permission set reference.
Action:: Provide resource actions or permission sets.

JPS-20600: MetaData-Provisioned is true, but no meta data found in policy object {0}.
Category:: Programmatic
Cause:: MetaData-Provisioned is true, but no meta data found in policy object {0}.
Action:: Check the policy store, make sure it is in an consistent state.

JPS-20601: Provided version "{0}" is invalid. Only alphabetic characters, digits, underscores, and dots are allowed.
Category:: Programmatic
Cause:: Provided version {0} is invalid. Only alphabetic characters, digits, underscores, and dots are allowed.
Action:: Provide a valid version.

JPS-20602: Provided meta data {0} is invalid. Reason: {1}
Category:: Programmatic
Cause:: Provided meta data {0} is invalid. Reason: {1}.
Action:: Provide a valid meta data.

JPS-90600: Security Module with the configuration id {0} already exists.
Category:: Security
Cause:: Security Module with the configuration id {0} already exists.
Action:: Provide a unique configuration id.

JPS-90601: Failed to create Security Module with the configuration id {0}, with error {1}
Category:: Security
Cause:: Failed to create Security Module with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90602: Security Module with the configuration id {0} not found.
Category:: Security
Cause:: Security Module with the configuration id {0} not found.
Action:: Make sure the configuration id is valid.

JPS-90603: AuditService is improperly configured.
Category:: Security
Cause:: Audit Service is not initializable.
Action:: Configure an audit server for audit trails

JPS-90604: Security Module with the configuration id {0} successfully created.
Category:: Security
Cause:: Security Module with the configuration id {0} successfully created.
Action:: Audit message, no action required

JPS-90605: Security Module with the configuration id {0} successfully modified.
Category:: Security
Cause:: Security Module with the configuration id {0} successfully modified.
Action:: Audit message, no action required

JPS-90606: Security Module with the configuration id {0} successfully deleted.
Category:: Security
Cause:: Security Module with the configuration id {0} successfully deleted.
Action:: Audit message, no action required

JPS-90607: Security Module with the configuration id {0} successfully retrieved.
Category:: Security
Cause:: Security Module with the configuration id {0} successfully retrieved.
Action:: Audit message, no action required

JPS-90608: Failed to modify Security Module with the configuration id {0}, with error {1}
Category:: Security
Cause:: Failed to modify PIP with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90620: PIP with the configuration id {0} already exists.
Category:: Security
Cause:: PIP with the configuration id/name {0} already exists.
Action:: Provide a unique configuration id/name.

JPS-90621: Failed to create PIP with the configuration id {0}, with error {1}
Category:: Security
Cause:: Failed to create PIP with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90622: PIP with the configuration id {0} not found.
Category:: Security
Cause:: PIP with the configuration id/name {0} not found.
Action:: Make sure the configuration id/name is valid.

JPS-90623: PIP with the configuration id {0} successfully created.
Category:: Security
Cause:: PIP with the configuration id {0} successfully created.
Action:: Audit message, no action required

JPS-90624: PIP with the configuration id {0} successfully modified.
Category:: Security
Cause:: PIP with the configuration id {0} successfully modified.
Action:: Audit message, no action required

JPS-90625: PIP with the configuration id {0} successfully deleted.
Category:: Security
Cause:: PIP with the configuration id {0} successfully deleted.
Action:: Audit message, no action required

JPS-90626: PIP with the configuration id {0} successfully retrieved.
Category:: Security
Cause:: PIP with the configuration id {0} successfully retrieved.
Action:: Audit message, no action required

JPS-90627: Failed to modify PIP with the configuration id {0}, with error {1}
Category:: Security
Cause:: Failed to modify PIP with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90630: Application Policy with the configuration id {0} not found.
Category:: Security
Cause:: Application with the id {0} not found.
Action:: Make sure the Appplication Policy is valid.

JPS-90631: SM Binding with the configuration id {0} and application name {1} successfully retrieved.
Category:: Security
Cause:: SM Binding with the configuration id {0} and application name {1} successfully retrieved.
Action:: Audit message, no action required

JPS-90632: SM with the configuration id {0} to application bindings retrieved.
Category:: Security
Cause:: SM with the configuration id {0} to application bindings retrieved.
Action:: Audit message, no action required

JPS-90633: SM with the configuration id {0} and application name {1} successfully unbound.
Category:: Security
Cause:: SM with the configuration id {0} and application name {1} successfully unbound.
Action:: Audit message, no action required

JPS-90634: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.
Category:: Security
Cause:: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.
Action:: Audit message, no action required

JPS-90635: PIP with the configuration id {0} to application bindings retrieved.
Category:: Security
Cause:: PIP with the configuration id {0} to application bindings retrieved.
Action:: Audit message, no action required

JPS-90636: PIP with the configuration id {0} and application name {1} successfully unbound.
Category:: Security
Cause:: PIP with the configuration id {0} and application name {1} successfully unbound.
Action:: Audit message, no action required

JPS-90637: Failed to create SM binding with the configuration id {0}, with error {1}
Category:: Security
Cause:: Failed to create SM binding with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90638: Failed to create PIP binding with the configuration id {0}, with error {1}
Category:: Security
Cause:: Failed to create PIP binding with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90639: Application {0} already bound to configuration {1}
Category:: Security
Cause:: Application {0} already bound to configuration {1}
Action:: No need to bind again

JPS-90640: Failed to unbind SM configuration
Category:: Security
Cause:: Failed to unbind SM with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90641: Failed to unbind PIP Configuration
Category:: Security
Cause:: Failed to unbind PIP with the configuration id {0}, with error {1}
Action:: Check error message for further details.

JPS-90642: The non-controlled policy distribution mode application {0} can not be bound to SM configuration
Category:: Security
Cause:: The non-controlled policy distribution mode application can not be bound to SM configuration
Action:: Bind controlled policy distribution mode application