security.configrpt.core.Security.properties=SECJ7083I: Properties None None security.policy.parser.encodeFilePath=SECJ0172E: Error {0} in encoding the FilePath While encoding the FilePath, there was an error. Check the specified syntax. To identify which policy file has a problem, enable security trace for the component com.ibm.ws.security.policy.*. trace.log will show the policy file name. security.configrpt.core.range=SECJ7185I: Range None None security.wsaccessmanager.classloadingaudit=SECJ0158I: Problem loading class {0}, using default authorization table provided by WebSphere The Vendor specified Authorization Table could not be loaded successfully. The WebSphere provided authorization table will be used. Make sure that the vendor's implementation of Authorization Table is in the CLASSPATH and that it could be loaded. security.zos.saf.credtoken.finalize.error=SECJ6215E: The SAF credential token {0} has been finalized but the underlying native credential has not been destroyed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.zos.saf.authen.refresh.failed.error=SECJ6221E: A native credential for user "{0}" cannot be recreated. The native service results related to this failure are: {1}. An authorized service used to create a native z/OS credential has failed. The credential cannot be used by the caller. Use the provided SAF service information to determine the cause of the failure. If the problem persists, contact the IBM support center. security.admintask.InvalidWrapBehavior=SECJ7470E: An invalid value has been specified for the binary audit log wrapping behavior. An invalid value was specified for the binary audit log wrapping behavior. Valid values are: WRAP, NOWRAP or SILENT_FAIL. Specify a valid value for the binary audit log wrapping behavior. security.configrpt.core.activeProtocol=SECJ7004I: Active RMI/IIOP authentication protocol None None security.configrpt.core.krb5Config=SECJ7236I: Kerberos configuration file None None security.sasconfig.startup.error=SECJ0049E: Configuration error encountered while starting the server An unexpected RemoteException, OpException or IOException occurred during server startup. There could be problems with loading or writing of security configuration URL property files. Verify that the file associated with security configuration URL property file (typically sas.server.props) has read permission and is writable. security.admintask.InvalidLDAPServerType=SECJ7321E: Invalid LDAP user registry type LDAP registry type was not a valid type Ensure user registry type is a valid type security.configrpt.core.serverAuthentication=SECJ7060I: Server Authentication None None security.jaas.update=SECJ4040W: {0} :Warning: update() method passed either a null or empty string. null or empty string was passed to update() method. This is a warning. security.audit.service.extra.warning=SECJ6010W: Extra AuditServiceProvider definition detected and discarded: {0}. Extra AuditServiceProvider was defined and is discarded. The com.ibm.wsspi.security.audit.auditServiceProvider properties contains extra information than necessary. Any information following the valid AuditServiceProvider definition is discarded. security.registry.userentry.notfound=SECJ0080E: User entry is not found in the registry This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.loginModules=SECJ7044I: JAAS login modules None None security.policy.perminstance.exception=SECJ0198E: An exception was caught while constructing the permission object. The exception is {0}. An Exception occurred while constructing the permission object. Check the exception. security.configrpt.No.AdminSecurityManager.Role.User=SECJ7231I: No AdminSecurityManager user or group None None security.web.ta.srcpatherr=SECJ0130E: Unable to get source path from request header 'via' When using WebSealTrustAssociationInterceptor, the "via" HTTP header in the HTTP Request object is examined. This message appears when the value for this header is not valid or corrupted. Make sure that WebSeal, the HTTP Server or both are properly working. security.admintask.naming.invalid.users.groups.SECJ7758E=SECJ7758E: The following users or groups or special subjects {0} cannot be added to role {1}. The users or groups are already assigned to this role. Run the command by correcting the user, group or specialSubject list. security.web.ta.nointclass=SECJ0124E: Trust Association Init No interceptor class {0} found The interceptor class file specified in trustedservers.properties cannot be found. Verify that the appropriate Trust Association classes are installed and the class path is correct. Also verify that the class specified in the trustedservers.properties file is correct and that the file has at least read permission. security.policy.app.parserexception=SECJ0189E: Caught ParserException while creating template for Application Policy {0}. The exception is {1}. ParserException occurred when creating the application policy template in the hashmap of all the templates. Check the ParserException data. Check the specified policy file. security.zos.saf.authen.pw.check.failed.info=SECJ6219I: Basic authentication failed for user "{0}". The native service results related to the authentication failure are: {1}. WebSphere was unable to authenticate the user with the password that was presented. It is likely that the user ID or password were not valid. Verify that the user ID is valid. If the user is valid, use the provided SAF serivce information to get more information about the cause of the failure. security.jaas.invalidLocalOSToken=SECJ4003E: Credential token login is not valid for LocalOS JAAS Login failure occurred while invoking login() with token for LocalOS. LocalOS does not support login with token. Make sure that the application program is valid. security.init.wccmjaas.wrongclasserror=SECJ0213E: Unexpected JAAS login provider class {0} is currently configured. The expected configured class is {1}. When WebSphere security is enabled, this class is required. WebSphere provides an implementation of javax.security.auth.login.Configuration and dynamically installs this class at server startup. Either some application code has installed a different login provider class or a problem occurred when WebSphere tried to dynamically install the class. Check for other server startup warning or error messages. security.configrpt.core.keyAlias=SECJ7200I: Key Alias None None security.configrpt.core.authContextImplClass=SECJ7016I: Authentication context implementation class None None security.admintask.NoKeyStorePathValue=SECJ7411E: No key store location was specified for the audit key store. Must specify a key store location for the audit key store Supply a key store location for the audit key store security.ssl.config.initialization=SECJ0139E: Error to get initial naming context This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.GetFiltersFailure=SECJ7372E: Failure to retrieve the audit specifications. Failure while retrieving the audit specifications. None security.configrpt.core.Session.Security=SECJ7276I: Session Security None None security.configrpt.core.trustAssociation=SECJ7141I: Trust association None None security.configrpt.core.Session.Management=SECJ7280I: Session management None None security.init.wccmjaas.setcfg=SECJ0215I: Successfully set JAAS login provider configuration class to {0}. WebSphere provides an implementation of the javax.security.auth.login.Configuration class. This class was successfully set at server startup. None. Informational only. security.profiletask.ExceptionAddAdminIdToUserRegObj=SECJ7350E: Exception raised while adding adminId to user registry Exception raised while adding adminId to user registry None security.admintask.checkpoint.not.enabled=SECJ7471W: Warning: automatic repository checkpoints is not enabled. To capture changes to the configuration repository and emit the corresponding audit records, you must enable automatic repository checkpoints of the extended repository service. Admin repository save changes will not be audited if checkpointing is not enabled. Verify that checkpointing is enabled. security.admintask.checkCluster.SECJ7824E=SECJ7824E: The {0} cluster is mapped to the {1} security domain. The cluster member being added to the {2} cluster must be on a node that is version 7.0 or higher if the cluster is mapped to a security domain. When a cluster is mapped to a security domain all members of that cluster have to be running on a version 7.0 or higner. Ensure the node of the cluster member is version 7.0 or higher. security.audit.service.everyone.audit=SECJ6109I: Access to a web resource is allowed because either the EVERYONE Special Subject was mapped to at least one of the required security role or if there is no auth constraint. Access to a web resource is granted to any user without requiring authentication when the Everyone Special Subject was mapped to at least one of the required security role. Modify the security constraint if the current behavior does not fit your needs. security.servcomp.get.rar=SECJ0292E: Failed to retrieve the information of Resource Adapter of {0} to call setupPolicy(). An unexpected exception occurred when trying to retrieve the information of the Resource Adapter to call the setupPolicy() method. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.SecurityContext.getActualCreds.invoke=SECJ0269E: Failed to get actual credentials. The exception is {0}. java.lang.reflect.InvocationTargetException occurred when trying to run getActualCredential() method. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.swam.remove.prin.ex=SECJ0262E: Exception occurred when removing {0} during cleanup. The exception is {1} Unexpected exception occurred when removing the specified principal during cleanup. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.ssl.config.initialization.fatal=SECJ0141E: Error to initialize default SSL configuration This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.sa.get.realm=SECJ0303E: Error getting registry''s realm. The exception is {0} Exception occurred when getting registry's realm. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.basic.challenge.audit=SECJ6123I: HTTP authorization header is missing. Send out 401 challenge. The authentication failed because there is no authorization header in the HTTP header. WebSphere Application Server will send a 401 challenge to the web client. No action is required. security.merge.node.signer.not.exchanged=SECJ0422I: During addNode from node "{0}" the default node certificate did not exchange its signer with the cell default truststore. This might cause a handshake failure when the cell tries to communicate with the node. Manual signer exchange might need to occur. It's likely the TrustStore named CellDefaultTrustStore or KeyStore named NodeDefaultKeyStore does not exist in the configuration. The node's signer certificates need to be added to the cell's truststores. security.registry.ldap.initerror=SECJ0068E: LDAP initialization error. The exception is {0}. An unexpected exception occurred when configuring for LDAP. Verify that the WebSphere LDAP configuration settings such as the provider URL are correct in the Security Center GUI. If using SSL, make sure that the SSL configuration is correct. security.admintask.AutogenCertFailure=SECJ7417E: Failure creating the self signed certificate for audit encryption Failed to create the self signed certificate for audit encryption None security.policy.ratemplate.parserexception=SECJ0193E: Caught ParserException while creating template for resource adaptor(read from ra.xml) {0}. The line is [{1}]. The exception is {2}. ParserException occurred when putting the resource adaptor template in the hashmap of all the templates. Check the ParserException data. Check the ra.xml's permission specification. security.admintask.mustSpecifyDomain.SECJ7823E=SECJ7823E: A security domain name must be specified when not in an AdminAgent process To obtain the pathname of a security domain belonging to a non-AdminAgent process, a security domain name must be specified. Ensure a security domain name has been specified if the process is not an AdminAgent. security.configrpt.domain.trustAssociation=SECJ7266I: Trust Association None None security.ltpa.factory.tokencreate.error=SECJ5016E: The LTPA TokenFactory {0} could not create a new LTPA token. The exception is {1}. The LTPA TokenFactory implementation had a problem in the createToken method or the keys used to create a token were not present. Ensure that the LPTA keys are configured properly and check the createToken implementation on the TokenFactory interface. security.getting.remote.server.ex=SECJ0253E: Generic Exception while getting remote security server. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.saml.element.id.negative.SECJ8042E=SECJ8042E: {0} {1} is not valid, specify a non-negative value. The parameter value must be non-negative. Specify a non-negative value for the given parameter. security.configrpt.core.algorithm=SECJ7177I: Algorithm None None security.scanner.risk.adminid.ok=SECJ7520I: Multiple Administrative user IDs are configured. When WebSphere Application Server security is enabled, a single security ID under the Administrator role is initially configured as the Security Server ID. Configuring multiple administrative user ids as Administrator can protect this server ID and enable more effective audit logging Multiple Administrative user IDs are configured. When WebSphere Application Server security is enabled, a single security ID under the Administrator role is initially configured as the Security Server ID. Configuring multiple administrative user ids as Administrator can protect this server ID and enable more effective audit logging None security.init.svcstart=SECJ0242I: Security service is starting Security service started. None. Informational only security.sas.configurl.missing=SECJ0047E: Missing or malformed security configuration URL specified by property {0} The URL used to specify Secure Association Service properties is missing or malformed. The URL is usually specified as a property name when starting WebSphere from the command line with the -D argument. For example: -Dcom.ibm.CORBA.ConfigURL=file:/C:/wastd/AppServer/properties/sas.server.props. Verify that the property and URL is specified and refers to a valid file and the file has the read permission. security.admintask.ExceptionIsAppSecEnabled=SECJ7336E: Exception raised while getting Application Security setting Caught exception while getting Application Security setting None security.registry.nt.noprivid=SECJ0070E: No privilege id configured for: {0} Unable to find a SID for the specified user in the Windows user registry. The user might not exist in the user registry. If appropriate create the user in the user registry. security.admintask.mismatch.krbConfig.SECJ7779E=SECJ7779E: Mismatch Kerberos configuration file (krb5.ini/krb5.conf). The krb5.ini/krb5.conf file for Kerberos authentication mechanism is {0} but the krb5.ini/krb5.conf file for SPNEGO Web authentication is {1} The Kerberos configuration file (krb5.ini/krb5.conf) for Kerberos authentication mechanism is not the same with the SPNEGO Web authentication. Verify the krb5.ini/krb5.conf file for Kerberos authentication and SPNEGO Web authentication are the same one. security.scanner.error.invalid.class=SECJ7504E: The security ConfigChecker class "{0}" could not be loaded due to the following exception: {1} The class could not be loaded. Check exception message for details Check that the class name exists and the class has been added to the plugin.xml. Check the exception message for details security.merge.node.keystore.creation.failed=SECJ0424E: During addNode from node "{0}" the default keystore and truststore were not already created. An attempt to create them on the DMGR failed with exception: {1}. The creation of keystore and truststore with self-signed certificate failed. The node agent did not have certificates created when it was federated into the cell. The attempt to create them during addNode failed. security.configrpt.core.krb5SpnPassword=SECJ7240I: Kerberos service name password None None security.web.ta.invalidprincipal=SECJ0394E: Principal exists in Subject returned by TAI.getSubject() but it does not implement java.security.Principal. The Trust Association Interceptor did not have the correct principal in the Subject. The principal must implement java.security.Principal. Contact the provider of the Trust Association Interceptor to ensure this problem gets resolved. security.configrpt.general.settings=SECJ7217I: General settings None None security.admintask.CertificateException=SECJ7465E: A certificate exception was raised while trying to load the keystore. The keystore could not be loaded due to a certificate exception. none security.authtbl.apphomefinder=SECJ0091E: Error looking up Application home This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.filterCriteria=SECJ7251I: SPNEGO Filter criteria None None security.web.ta.validationfailed=SECJ0126E: Trust Association failed during validation. The exception is {0}. Make sure that the setup is correct and that the user credentials are valid. When the appropriate interceptor is found for a given request, that interceptor then validates its trust with the reverse proxy server. This error message suggests that the validation has failed and therefore the reverse proxy cannot be trusted. For example, an incorrect or expired password might have been provided. In a production environment, the user might be alerted to check if there is an intruder in the system. In a development environment in which testing is underway, verify if the expected inputs from the reverse proxy server is in fact being passed to the interceptor correctly. The nature of these inputs really depends on how trust association is being established. For example, the simplest method would be to pass a user name/password through the Basic Authentication header. security.admintask.badCustomProp.SECJ7773E=SECJ7773E: Custom property string {0} is not formatted correctly. The custom property string is not formatted correctly. The format needs to be a comma separated string of attribute=value pairs, each pair should be in quotes. Ensure the custom property string is formatted correctly. security.util.get.reg=SECJ0264E: fillAccessids: Error getting user registry. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.useRegistryServerId=SECJ7155I: Use the registry server id instead of the internal server id None None security.policy.fileCanonicalPath=SECJ0182W: An exception was caught while trying to get the Canonical path for the file {1}. The exception is {0}. Could not get the Canonical path for the specified file Check the specified file name passed to security. It could be caused by incorrect data in xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.adminapp.jaspi.unsuppoterd.version.SECJ8030E=SECJ8030E: Applications with JASPI bindings can be deployed only on nodes at version 8 and higher. An application to be deployed contains JASPI bindings in ibm-application-bnd or in ibm-web-bnd files. JASPI authentication is supported on version 8 and higher nodes. Verify JASPI bindings are not defined in the application's bindings. security.admintask.InvalidEventFormatterClassName=SECJ7363E: Non valid or no reference specified for the event formatter class name. The eventFormatterClassName reference is a required field. Verify that a valid reference has been specified for the eventFormatterClassName security.policy.was.parserexception=SECJ0191E: Caught ParserException while creating template for was.policy {0} . The exception is {1}. ParserException occurred when putting the was.policy template in the hashmap of all the templates. Check the ParserException data. Check the specified was.policy file. security.scanner.error.check.exception=SECJ7505E: The security check, {0}, threw the following exception: {1} A security check threw an unexpected exception Examine the associated exception to determine the cause security.sambean.expltpakeys=SECJ0235E: An unexpected exception occurred when trying to export the LTPA Keys from the security mbean. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.InvalidProvider=SECJ7369E: Non valid or no reference specified for the audit service provider. The provider field is required. Verify that a valid reference has been specified for the audit service provider security.loadresource.error=SECJ0207E: Failed to load {0} resource from cell. The exception is {1} The specified resource could not be loaded due to an exception. The failure might be related to a configuration problem related to the resource. security.secsrv.get.initCtx=SECJ0282E: Error getting initial context. The exception is {0}. javax.naming.NamingException occurred while getting the initial naming context. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.authz.role.success.audit=SECJ6150I: The user has the required roles {0}. The user has been granted to one or more of the required roles. No action is required. security.configrpt.domain.CSI=SECJ7265I: RMI/IIOP Security None None security.jaas.parser.stringreader=SECJ4042E: {0} :ERROR: A file parser exception occurred with file : {1}. The exception is {2} IOException occurred trying to connect the specified stringreader. Investigate the exception. Check the specified string. security.formlogin.badconfig=SECJ0154E: SSO Configuration error. FormLogin is configured for web application {0} but SSO is not enabled in the global security settings. SSO must be enabled to use FormLogin. When LTPA is the authentication mechanism SSO must also be enabled if any web applications use FORM login. Enable SSO in the global security settings and restart WebSphere security.configrpt.CORBA.Naming.Users=SECJ7218I: CORBA Naming Service Users None None security.admintask.NoSuchProviderException=SECJ7463E: Exception was raised while trying to get an instance of the keystore with the specified provider. No such provider exists. No such provider exists for this keystore. Verify that the provider is valid and that the keystore does exist. security.configrpt.core.krb5Spn=SECJ7239I: Kerberos service name None None security.registry.notexist=SECJ0078E: User registry does not exist Unable to lookup RegistryHome in name space or narrow failed. The class for the user registry was not registered in the name space correctly or the class file for the user registry cannot be found. Verify that the class path is correct and that the required classes exist. security.sap.error.uniqueid.not.found.in.hashtable=SECJ5005E: Cannot create WSCredential without a valid com.ibm.wsspi.security.cred.uniqueId property value. The com.ibm.wsspi.security.cred.uniqueId property has not been found during a properties login attempt. Ensure that the java.util.Hashtable used for a properties login contains a valid property value for com.ibm.wsspi.security.cred.uniqueId. security.admintask.ProviderInUse=SECJ7380E: Unable to delete audit service provider: provider in use Audit service provider is in use by an audit event factory implementation and cannot be deleted. None security.configrpt.AdminSecurityManager.Role.Group=SECJ7232I: AdminSecurityManager Group None None security.wsaccessmanager.classloaded=SECJ0157I: Loaded Vendor AuthorizationTable: {0} The vendor specified Authorization Table is loaded successfully. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.sap.error.single.signon.token.not.mapped=SECJ5012E: Could not create default SingleSignonToken during propagation login. The following exception occurred: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.authn.failed.foruser=SECJ0055E: Authentication failed for {0}. The user id or password might have been entered incorrectly or misspelled. The user id might not exist, the account could have expired or disabled. The password might have expired. The user could not be authenticated. The user id or password might have been entered incorrectly. The user might not exist in the user registry that WebSphere is configured to authenticate to. If WebSphere security is configured to use LDAP as the user registry, the WebSphere security LDAP user and group search filter configuration might not match what the LDAP directory expects. Verify that the user id and password are entered correctly and exist in the user registry. If LDAP is configured as the security user registry, verify the WebSphere security LDAP user and group filters configuration match what the LDAP directory expects. Consult with the administrator of the user registry that WebSphere is configured to use if the problem persist. security.admintask.CreateKeyStoreObjectFailure=SECJ7415E: Failure creating the audit keystore object Failed to create the audit keystore ObjectName None security.audit.service.provider.info=SECJ6003I: Successfully loaded {0} name {1} and class name {2}. Indicate that the specified provider class was loaded. No action is required. security.util.remove.reg=SECJ0265E: removeAccessIds: Error getting user registry. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.policy.removepolicy.rarpath=SECJ0184W: An exception was caught while trying to get the absolute path for the resource adaptor {1} in removePolicy(). The exception is {0}. Could not get the absolute path for the resource adaptor in removePolicy(). Check the specified path. It could be caused by incorrect data in xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.audit.authz.success.audit=SECJ6130I: Access is allowed. Access to the resource is allowed because the user or the groups the user is in have the required security role. No action required if this is the desired behavior. security.registry.uniqueusrid.error=SECJ0351E: Could not get the uniqueId of the user {0} due to the following exception {1}. Internal Error. Make sure that the user is valid. Contact your service representative if the problem persists. security.admintask.jaspi.provider.undefined.SECJ8002E=SECJ8002E: Authentication provider {0} is not defined in the cell. An authentication provider with the specified name does not exist in the security configuration. Specify the name of an existing authentication provider. Use the displayJaspiProviderNames command to list the names of defined authentication providers. security.configrpt.core.timeout=SECJ7020I: Timeout of authentication data forwarded between servers None None security.configrpt.core.issuePermissionWarning=SECJ7011I: Warn if applications are granted custom permissions None None security.saml.idp.element.already.exist.SECJ8043E=SECJ8043E: {0} already exists in the SAML TAI IdP security configuration. An element can only be added in one security configuration. Rerun the command using an element that is not already defined in a SAML TAI configuration. security.registry.ldap.updated.audit=SECJ0421I: Security run time has successfully updated LDAP registry binding information. new LDAP bind information has been pushed to security run time. No user action is required. security.admintask.InvalidNotificationName=SECJ7383E: Non valid name for Audit Notification. Non valid name for audit notification specified. Verify that a valid name has been specified for the audit notification security.admintask.InvalidCertRef=SECJ7443E: Non valid or no value specified for the audit encryption certificate reference. The reference ID for the audit encryption certificate has not been specified correctly Specify a valid value for the audit encryption certificate reference. security.configrpt.core.primaryAdminId=SECJ7216I: Primary administrative user name None None security.merge.node.internal.serverid.used=SECJ0426E: InternalServerId is used in the current dmgr configuration. Cannot add an older node. Modify the dmgr security configuration to use the serverID/passwd before adding an older version node. An earlier leveled node cannot be added to a dmgr whose configuration is using the internalServerId. The dmgr configuration needs to be modified to use the serverID/password before an older version node can be added security.securityserver.error=SECJ0395E: Could not locate the SecurityServer at host/port: {0} to validate the userid and password entered. You might need to specify valid securityServerHost/Port in WAS_INSTALL_ROOT/profiles/profile_name/properties/sas.client.props file. A SecurityServer could not be located for login. In some cases it is necessary to specify a valid bootstrap host/port in the com.ibm.CSI.securityServerHost and com.ibm.CSI.securityServerPort properties in the ${WAS_INSTALL_ROOT}/profiles/profile_name/properties/sas.client.props file. See sas.client.props for details. security.configrpt.Operator.Role.Group=SECJ7109I: Operator Group None None security.audit.eventfactory.init.error=SECJ6050E: Audit Event Factory did not initialize. Exception = {0}. Audit Event Factory was not initialized, which occurred most likely due to incorrect class definition, incorrect class path, or missing class files. Examine the exception for the cause of the problem. security.admintask.ClassNotDefaultEventFactory=SECJ7432E: Cannot change the default audit event factory implementation classname. The classname specified does not match the default audit event factory implementation classname. Ensure that when specifying class name on the modify command and the implementation is the default audit event factory implementation, that it matches the default classname. security.policy.parser.expandperm=SECJ0169W: Expand exception occurred. Skip the permission entry. The exception is {0} While expanding the permission, caught an expand exception Check the permission entry syntax in your policy file. To identify which policy file has a problem, enable security trace for the component com.ibm.ws.security.policy.*. The trace.log file will show the policy file name. security.configrpt.core.reloadTimeout=SECJ7247I: SPNEGO Configuration reload timeout None None security.audit.form.login.redirect.audit=SECJ6153I: Redirect to form based login page {0} to prompt for web client authentication data. The web resource requires Form based authentication. Typically a web user will be redirected to a login page to enter user id and password. No action is required. security.admintask.UnknownHost=SECJ7461E: Failed to get the host name of the machine on which the Audit Reader is running. An exception was raised while attempting to obtain the host name of the machine on which the Audit Reader is running. none security.configrpt.core.confidentiality=SECJ7057I: Confidentiality None None security.ltpaconfig.createexcp=SECJ0061E: LTPAConfig creation exception This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.csi.session.not.exist.audit=SECJ6134I: Session does not exist on server. The client context id (= 0) in a MessageInContext message is not valid. No action required. security.admintask.rsaTokenNotPresent.SECJ7751E=SECJ7751E: The RSAToken authentication mechanism is missing from the security.xml configuration which may cause problems with administrative security. A security configuration does not have the required RSAToken authentication mechanism configured. This may be a problem with a migrated configuration that needs correction. security.configrpt.Naming.Role.Name=SECJ7113I: CORBA Naming Role Name None None security.jaas.IdentityAssertion.identity=SECJ4066E: Could not find identity to perform identity assertion. A Custom Login module must provide an identity to perform identity assertion. Check a Custom Login module to make sure an idenity is provided to the perform identity assertion. security.admintask.notExist.SECJ7754E=SECJ7754E: {0} does not exist. The realm name or resource name provided does not exist. Ensure the realm name or resource name being used exists. security.servcomp.setupPolicy=SECJ0287E: Failed to call setupPolicy for {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.service.undefined.error=SECJ6007E: Undefined {0} = {1}. The specified properties was not defined properly in the global security customer properties. Verified that the specified properties is defined properly in the global security custom properties. security.secsrv.badltpconfig=SECJ0237E: One or more vital LTPAServerObject configuration attributes are null or not available. The attributes and values are password : {0}, expiration time {1}, private key {2}, public key {3}, and shared key {4}. LTPA is the configurated authentication mechanism but it has not yet been properly configured. Keys or other LTPA configuration attributes are missing. Disable WebSphere security, restart the application server and properly configure LTPA authentication. security.policy.malformedURL=SECJ0177W: An exception was caught while converting class path {1} to URL. The exception is {0}. Could not convert the above class path to a URL Check the class path. Usually, this path was picked up from xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.admintask.oldZDomainPropsConfigured.SECJ7784W=SECJ7784W: The security custom properties security.zOS.domainName and security.zOS.domainType are specified in the security configuration, but these properties are deprecated. For backwards compatibilty, these values will override the one specified in the new custom property com.ibm.security.SAF.profilePrefix. The security custom properties security.zOS.domainName and security.zOS.domainType are deprecated, but they are currently specified in the security configuration. For backwards compatibilty, the values of these old properties will override whatever is specified in the the new custom property com.ibm.security.SAF.profilePrefix. The deprecated properties should be deleted from the security configuration, unless the configuration is part of a mixed-version cell that has a member at 6.1 or previous. security.rolebauthz.authzfail.checkTrustedAppsProfile=SECJ0432I: Check that the Trusted Applications Profile Facility has been configured properly. Through the use of the FACILITY class and BBO.TRUSTEDAPPS class profile, trusted applications, as a general rule, are needed when using SAF as the local operating system user registry or when you plan to use SAF authorization. You must enable the trusted applications by ensuring that the WebSphere Application Server has SAF access of READ to the RACF class of FACILITY and profile of BBO.TRUSTEDAPPS.<cell short name>.<cluster short name>. security.registry.groupdisplayname.notfound=SECJ0339E: Could not get the display name of the group {0}. Problem getting display name of a group. Make sure that the group is valid and has a display name. security.registry.exception=SECJ0081E: Registry exception This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.mismatch.krbRealm.SECJ7768E=SECJ7768E: Mismatch Kerberos realm name. The krb5Realm is {0} but the default Kerberos realm in the {1} is {2} The Kerberos realm name is not the same with default Kerberos realm in the Kerberos configuration file (krb5.ini/krb5.conf). Verify the Kerberos realm name against the default Kerberos default realm in the Kerberos configuration file. security.configrpt.Certificate.Alias=SECJ7131I: Certificate Alias None None security.configrpt.core.trustedId=SECJ7156I: Trusted identity None None security.sap.error.ltapserver.null=SECJ5017E: The Lightweight Third Party Authentication (LTPA) token could not be validated because the LTPA services are not available. This error most likely occurs when the Simple WebSphere Authentication Mechanism (SWAM) authentication mechanism is the active authentication mechanism. SWAM is meant for stand-alone servers and is not supported by WebSphere Process Server or by an environment that requires cross server (server-to-server) secure communications. Ensure that the active authentication mechanism is LTPA. security.configrpt.AdminSecurityManager.Role.User=SECJ7230I: AdminSecurityManager User None None security.policy.parser.expandsignedby=SECJ0171W: Expand exception occurred. Skip the signedby key entry. The exception is {0}. An expand exception occurred while expanding the signedby entry. Check the signedby entry syntax in your policy file. To identify which policy file has a problem, enable security trace for the component com.ibm.ws.security.policy.*. The trace.log file will show the policy file name. security.configrpt.Console.Users.Groups=SECJ7095I: Administrative users and groups None None security.configrpt.core.Security.Naming.Navigation=SECJ7122I: CORBA Naming Service Groups None None security.secsrv.find.registry=SECJ0284E: Error trying to find User Registry. The exception is {0}. javax.naming.NamingException occurred while finding the user registry. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.auditorId.change.ws.error=SECJ6052E: Workspace error occurred attempting to change the primary auditor ID. An error occurred accessing the workspace. None security.j2sec.init.error=SECJ0324E: Error during Java 2 Security and Dynamic Policy initialization. The exception is {0}. An unexpected error occurred during Java 2 Security and Dynamic Policy initialization. This is a general error. Look for previous messages that might be related to the failure or a configuration problem. Enabling security debug trace for security component com.ibm.ws.security.* might yield additional information. security.admintask.ExceptionGetGlobalSec=SECJ7337E: Exception raised while getting Global Security setting Caught exception while getting Global Security setting None security.authtbl.getmg=SECJ0090E: Error obtaining method group for method {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.InvalidLoginModuleType.SECJ7705E=SECJ7705E: Login module type is not valid. Valid login module types are: system, application. Ensure that the login module type is a valid type. security.admintask.InvalidMaxLogsValue=SECJ7395E: Non valid value for maximum number of audit logs was specified. The maximum number of audit logs needs to a number greater than 0. Supply a valid value for maximum number of audit logs security.ltpa.validate.nulltoken=SECJ0370E: Validation of the token failed because the token is null. Cannot validate the token since the token is null. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.ltpaconfig.removeexcp=SECJ0062E: LTPAConfig remove exception This is an internal error. The ejbRemove() operation failed on the LTPAConfigBean. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.policy.rarfile=SECJ0178E: An exception was caught while retrieving the data from the hashmap for the keyword {1}. The exception is {0}. Could not retrieve the resource adaptor policy file from the hashmap passed to setupPolicy(). Check the data stored in the hashmap for the resource adaptor keyword. It could be caused by incorrect xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.admintask.NoKeyStorePasswordValue=SECJ7413E: No key store password was specified for the audit key store. Must specify a key store password for the audit key store Supply a key store password for the audit key store security.configrpt.core.initializeAtStartup=SECJ7165I: Initialize at startup None None security.policy.imcomplete.filter.permission=SECJ0317W: The permission {0} specified in the application policy file({1}) is a part of the permission {2} specified in filter.policy. The permission class specified in the application policy is not be removed. However, it is a part of the permission specified in filter.policy. If the permission should be filtered out, divide the permission specified in the application policy. security.saml.existing.cert.alias.is.used.SECJ8052I=SECJ8052I: The existing alias name {0} is used because the certificate already exists in the trust store. The certificate already exists in the trust store. You cannot assign a new alias to this certificate. The existing alias name is used. Use the same alias for the same certificate that is already in the trust store. security.formlogin.nostoredurl=SECJ0223E: User {0} authenticated successfully but unable to send redirect to the original request page. The {1} cookie is not present. The HTTP cookie that contains the originally requested page was not found. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.ssl.config.initialization.failed=SECJ0140E: Failed to initialize Default SSL Settings This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.registry.mapcert.failed=SECJ0333E: The mapCertificate method failed. The mapCertificate method failed to return a user from the certificate chain. Make sure that the certificate should contain a valid user in the registry. This problem should have preceeded with other exception(s). Looking into them would help in narrowing down the problem. In addition if a custom registry is being used make sure you return a valid userId after successfully mapping the certificate. security.jaas.wccm.notLoaded=SECJ4044E: WCCM jaas objects is not yet load. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jaas.missingAuthData=SECJ4008E: Missing some of the authentication data Some of the authentication data is missing. Check the next message. It identifies what is missing. security.policy.parser.keystore=SECJ0168W: Keystore {0} of type {1} is being ignored Keystore of the above type is not supported. Use the supported type of keystores. security.configrpt.core.baseDN=SECJ7219I: Base distinguished name None None security.policy.parser.syntax.error=SECJ0320E: Error parsing {0}: {1} There is a syntax error in the policy file. Use ${java.home}/jre/bin/policytool to verify the syntax or edit the policy file and correct the syntax error. security.saml.idp.http.post.notexistent.SECJ8062W=SECJ8062W: There is not a SingleSignOnService binding for HTTP POST in the IdP metadata file {0}. The SingleSignOnService binding for HTTP POST is missing from the IdP metadata file. Verify the IdP metadata file. security.registry.uniquegrpid.error=SECJ0341E: Could not get the uniqueId for the group {0} because of the following exception {1}. Problem getting uniqueId of a group. Make sure that the group is valid in the registry and if it is a custom registry make sure it also has an uniqueId. security.jaas.close.stream=SECJ4043W: {0} :Warning: An unexpected IOException occurred when closing a stream. Unexpected IOException occurred trying to close a stream. This is a warning. security.admintask.timeout.SECJ7765E=SECJ7765E: The timeout value must have a minimum value of {0}. The value should be the minimum value specified. Ensure the timeout value has the minimum value specified. security.configrpt.Console.Role.Value=SECJ7097I: Administrative Role Value None None security.configrpt.core.cryptoHardware=SECJ7078I: Cryptographic token None None security.admintask.ReadOnlyCreate=SECJ7401E: Creating a read only key store object. File should already exist. When creating a hardware key store object the file in the path specified should already exist. Rerun the command with a specifying a file that already exists. security.policy.parser.methodinvocationfailed=SECJ0230E: Invoking reflection method {0} of object type {1} throws exception {2}. Reflection method invocation failed. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jaspi.configuration.file.missing.SECJ8027E=SECJ8027E: The path and name of file where JASPI persistent registrations are stored must be specified using property {0}. The named property must specify path and name of file where JASPI persistent registrations are stored. Specify the path and name of a file where JASPI persistent registrations are stored. security.methodgroups.nohome=SECJ0103E: MethodGroupHome does not exist This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.init.error=SECJ0007E: Error during security initialization. The exception is {0}. An unexpected error occurred during security initialization. This is a general error. Look for previous messages that might be related to the failure or to a configuration problem. Enabling security debug trace for components com.ibm.ws.security.* and com.ibm.ejs.security.* might yield additional information. security.jaas.getProperty=SECJ4035E: {0} :ERROR: Could not get System property: {1} Failed to get the specified property. Check if you defined the specified property correctly. security.admintask.IsAdminLockedOut=SECJ7330E: Failed to verify admin user would not be locked out of console Exception raised while verifying at least one admin id in the admin-authz.xml exists in the user registry None security.configrpt.core.keyStore=SECJ7144I: Key stores None None security.audit.cert.registry.audit=SECJ6120I: Authentication failed becasue the user registry was not defined. The authentication failed because there is no active user registry defined to map the client certificate user name to a valid WebSphere Application Server user. Verify that the registry and mapping configuration. security.web.ta.loadclass=SECJ0121I: Trust Association Init class {0} loaded successfully Self Explanatory. None, informational only. security.getting.initctx.error=SECJ0254E: Error getting Initial Naming Context. The exception is {0}. javax.naming.NamingException occurred when getting Initial Naming Context. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.noTrustedRealm.SECJ7757E=SECJ7757E: There are no trusted realms in {0}. There are no trusted realms for the realm, resource, or domain provided. Run the command on realm, resourse, or domain that has trusted realms. security.admintask.ListCertFailure=SECJ7427E: Failed to list the certificate aliases. Could not list the certificate aliases in the referenced keystore. Verify that at least one certificate alias exists in the keystore. security.admintask.InvalidBinaryAuditLog=SECJ7448E: Non valid or no value specified for the fully qualified path of the Binary Audit Log. The expected fully qualified filename for the Binary Audit Log was specified incorrectly. Check the pathname specified for the location of the Binary Audit Log. security.policy.parser.expandgrant=SECJ0170W: Expand exception occurred. Skip the grant entry. The exception is {0}. While expanding the grant entry, caught an expand exception Check the grant entry syntax in your policy file. To identify which policy file has a problem, enable security trace for the component com.ibm.ws.security.policy.*. The trace.log file will show the policy file name. security.admintask.authMechNotConfigured.SECJ7766E=SECJ7766E: The authentication mechanism is not configured. The specified authentication mechanism needs to be configured before it can be used. Ensure that an authentication mechanism is configured. security.admintask.InvalidCryptoAlgorithmInPassword=SECJ7472E: LDAP bind password could not be encoded. An invalid value was specified for the LDAP bind password or an invalid cryptographic algorithm was used. If you are using a WebSphere Application Server assigned algorithm, ensure that your password does not contain a bracket character. The bracket character conflicts with the cryptographic algorithm WebSphere Application Server assigns. If you are using custom password encryption, verify you have assigned a valid algorithm. security.secsrv.get.realm=SECJ0280E: Error getting realm from registry. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.useJACCProvider=SECJ7032I: External authorization using a JACC provider None None security.configrpt.core.logToSystemOut=SECJ7207I: Log to SystemOut None None security.admintask.noTrustedRealm.SECJ7755E=SECJ7755E: The trusted realm object does not exist. The trusted realm object does not exist. Run the command on a security domain that has the trusted realm object defined. security.sambean.impltpakeys=SECJ0236E: An unexpected exception occurred when trying to import the LTPA Keys from the security mbean with properties {0}. The exception is {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jacc.provider.pcontextkey.error=SECJ0389E: Problem getting the PolicyContext key {0}. The exception is {1}. The policy context key cannot be obtained to make the access decision. Make sure that the Policy Context Key in question is registered by the container. security.admintask.InvalidFilterRef=SECJ7370E: Non valid or no value specified for the audit specification reference. The audit specification reference field is required. Verify that a valid value has been specified for the audit specification reference security.admintask.noAuthConfig.SECJ7764E=SECJ7764E: The authorization configuration object does not exist. The authorization configuration object does not exist in the configuration. Ensure an authorization configuration object exists. security.configrpt.domain.securitySettings=SECJ7259I: Application and Java 2 Security None None security.configrpt.core.firstClass=SECJ7181I: Class name None None security.init.wccmjaas.wrongclasswarning=SECJ0214W: Unexpected JAAS login provider class {0} is currently configured. The expected configured class is {1}. When WebSphere security is enabled, this class is required. WebSphere provides an implementation of javax.security.auth.login.Configuration and dynamically installs this class at server startup. Either some application code has installed a different login provider class or a problem occurred when WebSphere tried to dynamically install the class. Check for other server startup warning or error messages. security.ltpa.init.error=SECJ0364E: Cannot initialize ltpa object because of the following exception {0}. The LTPA server object cannot be initialized. In most cases, this error occurs because the LTPA keys cannot be decrypted using the LTPA password. The password that is used to encrypt the keys is not the same password that is saved in the repository. The server might not come up when this problem occurs. If this happens, disable security, start the server, and then enter a new password for LTPA. Save the password, generate the keys, and then save again. Finally, turn on security and then stop and restart the server. Contact your service representative if the problem persists. security.authtbl.listerror=SECJ0089E: Error obtaining all permissions This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.service.no.auth.constraint.audit=SECJ6108I: Access to a web resource is allowed because there is no auth constraint. According to Servlet V2.4 Spec, access to a web resource should be permitted if there is no auth constraint in the security constraint. Modify the security constraint if the current behavior does not fit your needs. security.admintask.NoAuditXML=SECJ7424E: Audit.xml is not found. No audit.xml was found for this profile. Auditing is not configured. Ensure auditing is configured properly. security.audit.logger.write.error=SECJ6035E: Failure to write to the Audit log. Could not write the audit record to the Audit log. Verify the log exists. Check the error logs for any possible IO exceptions. security.j2c.mappingFailed=SECJ4061W: Exception {0} was thrown during mapping. An exception was created by the WebSphere default principal/credential mapping function. This is most likely caused by incorrect authentcaiton data configuration. security.addprovider.error=SECJ0385W: Cannot find and load the FIPS approved IBM JSSE or JCE providers. This can be a problem if your environment must use FIPS approved cryptographic algorithms and you are not using your own FIPS approved providers. The error status/exception is {0}. Cannot find and load the FIPS approved IBM JSSE or JCE providers. This is a problem when the IBM FIPS approved JCE provider is missing. Websphere Application Server depends on it when a FIPS approved provider is required. However, a missing FIPS approved IBM JSSE provider might not be a problem provided that you have configured it to use your own FIPS approved JSSE provider. Make sure that the missing provider jar, if needed, is in the JDK ext directory. security.admintask.scope.in.domain.SECJ7703E=SECJ7703E: {0} already exists in the {1} security configuration. A scope can only be mapped in one security configuration at time. Rerun the command using a scope that is not already mapped to a security configuration. security.configrpt.core.autoReload=SECJ7246I: Automatically reload SPNEGO Configuration None None security.configrpt.core.hostList=SECJ7164I: Host list None None security.configrpt.core.Security.Console.Name=SECJ7089I: Console Name None None security.ltpa.factory.null.error=SECJ5015E: The LTPA TokenFactory {0} returned is null. The LTPA TokenFactory implementation is likely not present in the class path or it cannot be initialized. Ensure that the LTPA TokenFactory implementation is located in the WebSphere class path. Typically these implementations are put in the ${WAS_INSTALL_ROOT}/classes directory. security.configrpt.core.keyFileName=SECJ7072I: Key file name None None security.admintask.NoKeyStoreNameValue=SECJ7410E: No name was specified for the audit key store. Must specify a name for the audit key store Supply a name for the audit key store security.admintask.CertAliasExists=SECJ7419E: Found certificate with the same alias in the keystore. A certificate with the same alias name already exists in the keystore. Cannot add. None security.admintask.serverIdAndPassword.SECJ7713E=SECJ7713E: Password and server id must be provided at the same time. When a server id is proviced then a password must be specified as well. Ensure a server id and password are provided. security.audit.fatal.error=SECJ6047E: Unrecoverable error occurred in the audit subsystem. An unrecoverable error occurred in the audit subsystem. Auditing is discontinued. Examine the error logs for the cause of the problem. security.jaas.invalidType.cred.exception=SECJ4052E: InvalidCredentialType exception is caught while serialized Subject is being restored. The exception is {0}. InvalidCredentialType exception occurred while restoring the credential. Investigate the SAS problem. Contact your service representative if the problem persist. security.audit.service.config.error=SECJ6006E: Security auditing is REQUIRED but {0} was not defined. At least one AuditEventFactory and an AuditServiceProvider must be defined when the security auditing policy is set to REQUIRED. Verify that the two properties com.ibm.websphere.security.audit.auditEventFactory and com.ibm.wsspi.security.audit.auditServiceProvider are defined proerly in the global security custom properties. security.adminapp.notexist=SECJ0094E: Admin Application does not exist This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.managementScope=SECJ7147I: Management scope None None security.load.secConfig=SECJ0273E: Failed to load SecurityServer.xml. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.j2c.reflectionFailure=SECJ4063E: Exception {0} caught in processing callback {1} Unexpected problem occured when processing a WebSphere Application Server V5 mapping callback type. Contact your service representative with information present in the error log. security.zos.saf.threadid.sync.error=SECJ6223E: Thread identity synchronization of user "{0}" failed. The native service results related to this failure are: {1}. An authorized service used to perform thread identity synchronization has failed. The thread security environment might not have been associated with the current thread of execution. User the provided SAF service information to determine the cause of the failure. If the problem persists, contact the IBM support center. security.configrpt.core.enforceFineGrainedJCASecurity=SECJ7009I: Restrict access to resource authentication data None None security.audit.basic.success.audit=SECJ6126I: Basic authentication was successful. Authentication using the user id and password in the HTTP header was successful. No action is required. security.jaspi.configuration.factory.undefined.SECJ8032W=SECJ8032W: AuthConfigFactory implementation is not defined, using the default JASPI factory implementation class: {0}. The JASPI factory implementation is not defined. The default JASPI factory implementation has been set in the server runtime. However, JASPI may not function for a client. Set the fully qualified class name of the default JASPI factory implementation class as the value for the property authconfigprovider.factory in java.security. security.audit.enforcing.silent_fail.error=SECJ6054E: The audit log wrapping behavior is set to SILENT_FAIL and the maximum number of audit logs has been reached. Audit logging will stop. Audit logging stopped: maximum number of audit logs has been reached and the wrapping behavior is set to SILENT_FAIL. Determine whether the maximum number of audit logs needs to be increased. Archive all the saved audit logs to a safe repository and restart the server to restart the auditing service security.registry.ldap.mapcredentialBadFilter=SECJ0147E: Cannot map the credential of the given credential token for certificate subject DN {0} into LDAP because of an LDAP filter mapping exception. The CertificateMapperException is {1} The Certificate mapping filter specified by the user in the global security settings is missing or malformed. Review the certificate mapping filter configuration in the LDAP Advanced properties in the Security Center and verify it is present and correct. security.webseal.nopdauth=SECJ0225W: PD Authentication disabled. PD Authentication disabled. None, informational only. security.scanner.risk.admin.role.improve=SECJ7523W: Multiple Administrative User Roles are not configured. A number of administrative roles are defined to provide degrees of authority that are needed to perform certain administrative functions from either the Web-based administrative console or the system management scripting interface. The authorization policy is only enforced when administrative security is enabled. Multiple Administrative User Roles are not configured. A number of administrative roles are defined to provide degrees of authority that are needed to perform certain administrative functions from either the Web-based administrative console or the system management scripting interface. The authorization policy is only enforced when administrative security is enabled. None security.jaas.open.stringreader=SECJ4041E: {0} :ERROR: Could not create or open StringReader: {1}. The exception is {2}. Could not create or open the specified StringReader. Investigate the exception. security.scanner.risk.admin.security.ok=SECJ7524I: Administrative Security is enabled. Only users with specific rights can use the WebSphere Application Server administrative tools to perform any administrative operation This message is for informational purposes only. None security.scanner.risk.need.admin.security=SECJ7501I: Administrative Security is not being used, therefore this option is not being used Administrative Security is not being used, therefore this option is not being used None security.configrpt.Naming.Everyone=SECJ7117I: Everyone None None security.configrpt.core.TrustAssociation.interceptors=SECJ7142I: Interceptors None None security.admintask.unableToRunCommand.SECJ7810E=SECJ7810E: The {0} command can not be run on the {1} security domain. Security configuration operation can not be run on the special security domain. This operation can not be performed on the security domain. security.admintask.NoKeyStoreConfirmPasswordValue=SECJ7414E: No key store confirmation password was specified for the audit key store. Must specify a confirmation key store password to for the audit key store Supply a confirmation key store password for the audit key store security.scanner.risk.samples.improve=SECJ7540W: WebSphere Application Server Sample Applications are installed. WebSphere Application Server ships with examples to demonstrate various parts of WebSphere Application Server. These samples might be installed by default and are not intended for use in a production environment. Some of these samples can provide an intruder with information about your system. WebSphere Application Server Sample Applications are installed. WebSphere Application Server ships with examples to demonstrate various parts of WebSphere Application Server. These samples might be installed by default and are not intended for use in a production environment. Some of these samples can provide an intruder with information about your system. Un-install sample application if not needed. security.scanner.write.to.file=SECJ7544I: Output is logged in the following location: {0} None None security.init.secdm.init=SECJ0231I: The Security component''s FFDC Diagnostic Module {0} registered successfully: {1}. Describes whether the Security component's FFDC Diagnostic module was successfully registered. None. Informational only. security.ltpa.credmap.failed=SECJ0064E: Credential mapping failed The credential mapping can fail for a number of reasons: The credential token is not an instance of a supported CredentialToken type for a mapping. The principal identified in the credential cannot be mapped to an entry or found in the user registry. A user registry exception occurs if the user registry has been stopped. Verify that the user registry is operational. Also verify that the principal exists in the target user registry if appropriate. The exception reported with this error message might help to diagnose the problem. security.ssl.config.initialization.warning.badSecurityLevel=SECJ0152W: SecurityLevel was either missing or set to a wrong value (valid values are: high, medium, low); default to high. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.aliasPrefix=SECJ7194I: Key alias prefix name None None security.registry.ldap.update.audit=SECJ0420I: Security run time is unable to update LDAP registry binding information. new bind information might be incorrect. Verify bind DN and password are correct. security.registry.initerror=SECJ0357E: The registry initialization failed with the following exception {0}. Registry cannot be initialized. Internal Error. Make sure that the user who is running WebSphere Application Server has administrative and "act as part of operating system" privileges in the Windows machine and is also an administrator in the domain machine. Contact your service representative if the problem persists. security.configrpt.core.serverKeyAlias=SECJ7176I: Default server certificate alias None None security.admintask.strategyTypeMismatch.SECJ7707E=SECJ7707E: The number of authentication startegies in the list must match the number of login modules in the list. Each login module provided must have a corresponding authentication strategy. Ensure that there is an authenticatino startegy type for each login module. security.admintask.notClassProvided.SECJ7744E=SECJ7744E: A custom registry class name must be provided. When configuring a custom user registry a class name must be provided. Run the command providing custom registry class name. security.init.startinit=SECJ0239I: Security service initialization started Security service initialization started. None. Informational only security.scanner.error.invalid.file=SECJ7503E: Unable access file or directory "{0}". The file or directory might be missing or corrupted. Unable to fine the specified file or directory. Ensure that the file or directory reported exists and is not corrupted before continuing. security.policy.deployedapp.appobj=SECJ0180E: An exception was caught while trying to get the data from the hashmap using the keyword {1}. The exception is {0}. Could not retrieve the deployed application policy file from the hashmap passed to setupPolicy(). This is an internal error. However, it could be caused by incorrect data in xml file. Check the type of the policy file and the hashmap being passed to setupPolicy(). Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.admintask.globalfedoption.globalnonfedchange.SECJ7826E=SECJ7826E: Cannot change the user registry at the global security domain to be a non-federated repository. The following application security domains are configured to use the global federated repository option: {0}. The global security domain was originally configured to use a federated repository as the user registry and one or more application security domains were configured to use the global federated repository. The user registry at the global security domain cannot be changed when application security domains are using the global federated repository option. Before changing the user registry configuration for the global security domain to not use a federated repository, the following needs to be done: The application security domains which are using the global federated repository will have to be configured to use a different user registry. security.jacc.tools.authzprovider.error=SECJ0411E: An exception occurred when getting the authorization provider object from the configuration. The exception is {1}. Because of an exception, the security policy information might not have been updated to the provider. Make sure that the provider is up and running and the JACC configuration is correct. Once the problem is fixed, one can also use the wsadmin tool to manually propagate the security policy information to the provider instead of reinstalling the application. See the information center documentation for more details on running this tool. If problem persists, contact your service representative. security.jaas.invalidCORBAAttribute=SECJ4020E: CORBA: Invalid Attribute Type: {0} {1} CORBA credential has attribute that is not valid. Contact your service representative with exception stack trace information present in the error log. security.admintask.CannotDeleteEncryptionCert=SECJ7442E: Empty value specified for encryption certificate reference. Cannot delete the encryption certificate when encryption is enabled or being enabled. Encryption is enabled or is being enabled. The encryption certificate is in use and cannot be deleted Disable encryption before deleting the encryption certificate. security.zos.threadid.connmgmt.denied=SECJ6212W: Connection management thread identity synchronization has been disabled by the z/OS security product. The server has been configured to perform J2EE and operating system thread identity synchronization for connectors that are able to exploit it but the security product has not authorized the use of this support. Contact your security product administrator to request authorization to use thread identity synchronization. security.configrpt.core.customRegistryClassName=SECJ7225I: Custom registry class name None None security.admintask.FileNotFound=SECJ7467E: The named file "{0}" does not exist. Could not open or read the file. Specify a valid filename. security.admintask.CreateObjFailure=SECJ7366E: Failed to create object. Failure occurred trying to create a configuration object. None security.admintask.NoNameForFilter=SECJ7429E: Missing unique name for audit specification. A unique name was not specified for the audit specification. Specify a unique name for the audit specification. security.roleauthz.appalreadyload=SECJ0220W: The role based authorizer for module {0} has already been loaded. The role based authorizer will load only once per module. None, informational only. security.policy.param.setupPolicy=SECJ0175E: An exception was caught while retrieving data from the hashmap for the keyword {1}. The exception is {0}. The data stored for the keyword "type" in the hashmap is incorrect This is an internal error. However, it could be caused by an incorrect xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.admintask.cannotRemoveRealm.SECJ7796E=SECJ7796E: The security domain default realm {0} can not be removed form the list of trusted realms. The security domain default realm is always trusted and can not be removed form the list of trusted realms. Ensure the realm being removed is not domain default realm. security.configrpt.core.alias=SECJ7043I: Alias None None security.audit.signing.error=SECJ6031E: Failure to sign the audit record. Exception = {0}. Signing error generated while trying to sign the audit record. Examine the exception for the cause of the problem. security.admintask.greater.SECJ7756E=SECJ7756E: The {0} value must be greater then 0. The number of elements return by the task needs to be greater then 0. Ensure the number is greater then 0. security.jsecman.permdenied=SECJ0134E: The current Java 2 Security policy does not permit the requested action.{0}Java 2 Security Permission: {1}, denied with exception message: {2}.{3}Violating code: {4} The Java Security Manager checkPermission() threw a SecurityException on the subject Permission. Verify that the attempted operation is permitted. security.ltpaconfig.notexist=SECJ0060E: LTPA configuration not found This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.zos.saf.authen.cert.map.failed.info=SECJ6220I: Certificate authentication failed for certificate with SubjectDN="{0}" and IssuerDN="{1}". The native service results related to the authentication failure are: {2}. WebSphere was unable to map the certificate that was presented to a valid user. It is likely that the issuer of the certificate is not trusted or that the mapping rules do not account for issuer and subject distinguished names. Verify that the certificate chain is trusted. If the chain is valid and trusted, use the provided SAF service information to get more information about the cause of the failure. security.lc.create.err=SECJ0222E: An unexpected exception occurred when trying to create a LoginContext. The LoginModule alias is {0} and the exception is {1}. A JAAS LoginContext could not be created due to the unexpected exception. The problem could be due to a configuration error. security.custom.registry.initialized=SECJ0136I: Custom Registry:{0} has been initialized Reports the Custom User Registry implementation that is being used. None, informational only. security.jaas.NoWSLoginHelperImpl=SECJ4007E: Not supposed to construct WSLoginHelperImpl object WSLoginHelperImpl object instance should not be constructed. Check the user application. WSLoginHelperImpl should not be directly constructed. security.audit.exception.audit=SECJ6128I: Authentication failed due to internal error. Authentication failed and a runtime exception was caught. Report this problem to IBM. security.wsaccessmanager.VendorAuthTableError=SECJ0161E: Error returned from Vendor AuthorizationTable. The exception is {0} The vendor specified Authorization Table failed during authorization check. Refer to the vendor's specific exception for details. If vendor's specific exception is not present, contact your service representative with the exception stack trace information present in the error log. security.admintask.cannotRemoveRealm.SECJ7795E=SECJ7795E: The global security realm {0} can not be removed from the list of trusted realms. The global security configuration realm is always trusted and can not be removed form the list of trusted realms. Ensure the realm being removed is not the global security realm. security.ssl.config.initialization.warning.invalidkeystoretype=SECJ0380W: The keystore or truststore type specified is invalid. Adjusting to use the correct type, however, correct the SSL configuration for performance reasons. The keystore or truststore type specified is not valid. Modify the SSL configuration so that the keystore or truststore type is a valid type. You can check the keystore and truststore types by loading them in WebSphere's IKeyMan tool. security.policy.filter.ioexception=SECJ0194E: Caught IOException while adding permission to the set of filtered permissions. The exception is {0}. IOException occurred when adding permission to the set of filtered permissions. Check the filter.policy file. security.admintask.invalidAuthMechType=SECJ7547E: Authentication mechanism type is not valid Valid authentication mechanism types are: KRB5, LTPA Ensure user authentication mechanism type is a valid type security.sambean.getgrperr=SECJ0234E: An unexpected exception occurred when trying to get groups from the User Registry with pattern {0} and limit {1}. The exception is {2}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.invalid.SPN.SECJ7767E=SECJ7767E: serverSpn {0} is malformed, it must be in the format of <service>/<host name> or <service>/<host name>@KerberosRealm. The Kerberos service principal name format is malformed. Verify the Kerberos service principal name (SPN) security.admintask.InvalidClassName=SECJ7362E: Non valid or no reference specified for the class name of this implementation. The className reference is a required field. Verify that a valid reference has been specified for the className security.admintask.InvalidAuditPolicy=SECJ7388E: Non valid value specified for the audit policy. Valid values are WARN, NOWARN, and FATAL. Specify a valid audit policy value security.zos.trusted.apps.enabled=SECJ6207I: Authorized credential management is enabled. Applications running in this server are considered "trusted". When applications are trusted, the security infrastructure will allow the creation of MVS credentials without a password, passticket, or certificate as an authenticator. Trusted applications must be enabled in order to use the LTPA authentication mechanism, identity assertion, or a Trust Association Interceptor with a "Local OS" user registry on z/OS. Trusted applications must also be enabled to use SAF authorization. No user action is required. security.methodgroups.predef.createerror=SECJ0104E: Error creating predefined method groups This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.policy.removepolicy.modulepath=SECJ0185W: An exception was caught while trying to get the absolute path for the module {1} in removePolicy(). The exception is {0} Could not get the absolute path for the module in removePolicy(). Check the specified path. It could be caused by incorrect data in xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.jsecman.illegal.perm=SECJ0133E: Illegal {0} : {1} An illegal Permission was attempted. Only the main thread can set the security manager. Verify that the code that is trying to set the security manager is not trying to subvert the WebSphere security manager. security.create.server.error=SECJ0250E: Error creating security server. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.web.initerror=SECJ0082E: Error during web security initialization This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.ltpa.validate.tokenexpired=SECJ0371W: Validation of the LTPA token failed because the token expired with the following info: {0}. This warning might indicate expected behavior. Please refer to technote at {1}. Cannot validate the token since the token has expired. Once the token timeout is reached, the token is not validated and you must authenticate again. This is normal. Make sure that all the WebSphere nodes and cell(s) are synchronized with respect to time, date and time zone. You can change the token expiration time if necessary. security.mg.updateerr=SECJ0100E: Error storing method group This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Naming.Create.Name=SECJ7124I: Create None None security.jaas.configNewInstance=SECJ4023E: Failed to create a Configuration instance. Failed to create a configuration instance Contact your service representative with exception stack trace information present in the error log. security.registry.usersecurityname.notfound=SECJ0353E: Could not get the name of the user whose uniqueId is {0}. Internal Error. Make sure that the user is valid. Contact your service representative if the problem persists. security.jaas.getCurrentException=SECJ4012E: Error getting SecurityCurrent from the ORB {0} Getting security current caused an exception. Make sure that the ORB is initialized correctly in the user application. security.configrpt.core.clientAuthenticationSupported=SECJ7158I: Client Authentication Supported None None security.authtbl.deleteerror=SECJ0088E: Error deleting permission This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jacc.server.task.error=SECJ0399E: Error updating deployment.xml information with the appContextIDForSecurity for application {0}. The exception is {1}. The appContextIDForSecurity atribute is required when using JACC as the authorization. If JACC will not be used for authorization then this should not impact anything. If JACC will be used for authorization, contact your IBM representative if this problem persists. security.admintask.config.does.not.exist.SECJ7702E=SECJ7702E: Security domain {0} does not exist. The security configuration does not exist. Run the command with a pre-existing security configuration. security.audit.service.no.role.audit=SECJ6105I: Access to a web resource is denied because no security role is defined in the auth constraint. According to Servlet V2.4 Spec, access to a web resource should be precluded if there is an auth constraint in the security constraint but there is no security role defined in the auth constraint. Modify the security constraint if the current behavior does not fit your needs. security.admintask.noKeyStore.SECJ7749E=SECJ7749E: A key store must be specified when a certificate alias is specified. When a certificate alias is specified a key store object must be specified. Run the command providing a key store. security.configrpt.messages=SECJ7215I: messages None None security.jsecman.permdeniedmsg=SECJ0314W: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. Refer to the InfoCenter for further information.{0}Permission:{1}Code:{2}{3}Stack Trace:{4}Code Base Location:{5} The Java Security Manager checkPermission() threw a SecurityException on the subject Permission. A caller on the call stack does not have the required permission. This might not be a problem if the caller properly handles this exception. Verify that the attempted operation is permitted by examining all Java 2 security policy files and application code. Additional permissions might be required, a doPrivileged API might be needed in some code on the call stack, or the Security Manager properly prevented access to a resource the caller does not have permission to access. security.web.cred.nopubname=SECJ0115W: The credential has a null value for the public name The credential is possibly malformed or corrupted. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.multidomain.oldServerSecurity.SECJ7789E=SECJ7789E: Can not convert the server level security configuration to a domain configuration since the {0} server does not have a server level security configured. A server should contain the server level security configuration to be converted to a security domain. Make sure that the server name is correct and it has a server level security configuration associated with it. security.authn.error=SECJ0336E: Authentication failed for user {0} because of the following exception {1} Authentication failed with the specified reason. Verify that the user id and password are entered correctly. Consult with the administrator of the user registry if the problem persist. security.configrpt.core.hour=SECJ7204I: Hour None None security.authtbl.apphome=SECJ0092E: Application home not found This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.Security.Configuration.Name=SECJ7000I: Security Configuration Name None None security.policy.unresolved.permission=SECJ0325W: The permission {0} specified in the policy file {1} is unresolved. The permission class specified in the policy file was not loaded. Confirm that the specified permission in then policy file is correct. If permission class is incorrect, this warning is issued. security.admintask.multidomain.oldServerSecurity.SECJ7788E=SECJ7788E: The {0} resource cannot be mapped to a domain since a server level security configuration is associated with the resource either directly or indirectly. A server that contains server lever security configuration is being associated with a domain. The server level security configuration is deprecated. The offending server or a cluster member should not contain the server level security configuration if it needs to be mapped to a domain. security.registry.getgrpsforuser.notfound=SECJ0343E: Could not get the groups that the user {0} belongs to. Internal Error. Make sure that the user is valid. Contact your service representative if the problem persists. security.rolebauthz.nocred=SECJ0306E: No received or invocation credential exist on the thread. The Role based authorization check will not have an accessId of the caller to check. The parameters are: access check method {0} on resource {1} and module {2}. The stack trace is {3}. No invocation or received credentials were established on this thread. This might cause the role based authorization check to fail. The stack trace is obtained by a local throw catch block that might be useful for debugging the problem. security.web.config.initerror=SECJ0084W: Error while initializing security web configuration. The exception is {0}. An error internal occurred while initializing the security attributes of a Web Application. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.jaspi.type.invalid.SECJ8005E=SECJ8005E: The command result object type is not valid: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.RSAKeyStore.SECJ7747E=SECJ7747E: {0} is not a RSA token key store. A RSA key store must be used on a RSA authorization mechanism. Run the command specifying a RSA key store. security.registry.getusers.error=SECJ0352E: Could not get the users matching the pattern {0} because of the following exception {1}. Internal Error. Make sure that the users matching the pattern exist in the registry. Contact your service representative if the problem persists. security.configrpt.core.interceptorClassName=SECJ7023I: Interceptor class name None None security.admintask.cannotRemove.SECJ7737E=SECJ7737E: Cannot remove {0}. The specified login module cannot be removed. Certian login module cannot be removed. Run the command with a login module that can be removed. security.admintask.ExceptionProcessingWizardSettings=SECJ7334E: Exception raised while applying wizard security settings Caught exception while applying wizard security settings None security.configrpt.core.keySet=SECJ7192I: Key set None None security.audit.report.EventType.name=SECJ7445I: Event Type None None security.admintask.InvalidFileLocation=SECJ7364E: Non valid or no reference specified for the location of the binary audit file. The fileLocation reference is a required field. Verify that a valid reference has been specified for the fileLocation security.registry.ldap.mapcredentialNSEE=SECJ0151E: Cannot create a credential for the mapped credential token into LDAP with subjectDN {0} and mapped name {1} using filter {2}. The exception is {3} The DN in the certificate was successfully mapped to an entry in LDAP but, an unexpected exception occurred when trying to create a credential for the mapped entry. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.NoKeyStoreRefValue=SECJ7426E: No reference id was specified for the audit key store. Must specify a valid reference id for the audit key store Supply a reference id for the audit key store security.registry.getgrpsforuser.error=SECJ0344E: Could not get the groups that the user {0} belongs to because of the following exception {1}. Internal Error. Make sure that the user is valid. Contact your service representative if the problem persists. security.admintask.InvalidUserRegType=SECJ7320E: Invalid user registry type Valid user registry types are: LDAPUserRegistry, LocalOSUserRegistry, CustomUserRegistry, WIMUserRegistry Ensure user registry type is a valid type security.admintask.badUserOrPassword.SECJ7715E=SECJ7715E: Unknown user name or bad password. User name or password are unable to authenticate to the user registry. Ensure a valid user name and password are specified. security.saml.element.id.notavailable.SECJ8040E=SECJ8040E: {0} {1} is already defined in the SAML TAI configuration. The given parameter value has been defined in the SAML TAI configuration. Verify the SAML TAI properties and specify a value that is not already used. If you do not use this option, a value is automatically selected. security.jaas.duplicate.config=SECJ4046E: Duplicate login config name {0}. Will over write. Duplicate login configuration name was specified in the configuration data. Check the configuration data. security.secsrv.find.reg=SECJ0275E: Error trying to find user registry. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.CreateKeyStoreFileFailure=SECJ7416E: Failure creating the audit keystore Failed to create the audit keystore None security.audit.service.secure.redirect.audit=SECJ6106I: The request is redirected to {0} because the requested resource must be accessed via HTTPS. The requested resource has a Data Constraint and requires SSL connection to it. No action is required. security.sap.error.securityname.not.found.in.hashtable=SECJ5006E: Cannot create WSCredential without a valid com.ibm.wsspi.security.cred.securityName property value. The com.ibm.wsspi.security.cred.securityName property has not been found during a properties login attempt. Ensure that the java.util.Hashtable used for a properties login contains a valid property value for com.ibm.wsspi.security.cred.securityName. security.configrpt.core.searchTimeout=SECJ7223I: Search timeout None None security.audit.signing.init.error=SECJ6041E: Failure to initialize Audit signing algorithm. Exception = {0}. An error occurred during the initialization of the Audit signing algorithm. Examine the exception for the cause of the problem. security.admintask.InvalidMonitorName=SECJ7375E: Non valid name for Audit Notification Monitor. Non valid name for audit notification monitor specified. Verify that a valid name has been specified for the audit notification monitor security.admintask.cannotCreateDomain.SECJ7811E=SECJ7811E: Can not create a security domain named {0}. The name is reserved for a special case security domain. The security domain name being used is reserved for a special case securty domain and can not be created with the command. Endure another security domain name is used when running the command. security.zos.trusted.apps.disabled=SECJ6208I: Authorized credential management is disabled. Applications running in this server are not considered "trusted". Since applications are not trusted, the security infrastructure has disallowed the creation of MVS credentials without a password, passticket, or certificate as an authenticator. Trusted applications must be enabled in order to use the LTPA authentication mechanism, identity assertion, or a Trust Association Interceptor with a "Local OS" user registry on z/OS. Trusted applications must also be enabled to use SAF authorization. No user action is required. security.ssl.initial_ssl.missing=SECJ0146I: ${WAS_HOME}/properties/initial_ssl.properties was not found This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.layers=SECJ7052I: Layers None None security.init.nullprocesstype=SECJ0366E: Cannot obtain the WebSphere Application Server process type during initialization. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.wsSchedule=SECJ7212I: Schedules None None security.configrpt.core.krb5Keytab=SECJ7237I: Kerberos keytab file None None security.audit.encryption.data.error=SECJ6044E: Data that is not valid was passed into the encryption algorithm. A data stream that is not valid was passed into the encryption algorithm. Verify that a non-null byte stream of data is being passed in. security.policy.ramodule.path=SECJ0181W: An exception was caught while trying to get the resource adaptor module {1} absolute filepath. The exception is {0}. Could not get the resource adaptor module's absolute filepath. It could be caused by incorrect data in resources.xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.web.authAlreadyEstablished=SECJ0431E: Authentication had been already established. Authentication had been already established. If you want to login with another user, you need to logout first. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.j2c.initFailureRecovery=SECJ4059W: WSDefaultPrincipalMapping Initialization failed. Fall back to use WSMappingCallbackHandler. WSDefaultPrincipalMapping initialization failed. The JCA container managed principal/credential mapping most likely will not work properly. Examine the cause of the exception and correct the problem. The most likely cause for this error is that the WSMappingCallbackHandlerFactory implementation class was not configured properly. security.admintask.noRealm.SECJ7733E=SECJ7733E: Realm {0} does not exist. The specified realm does not exist. Run the command with a realm that exists. security.configrpt.Console.User=SECJ7106I: Administrative User Roles None None security.policy.app.ioexception=SECJ0188E: Caught IOException while creating template for Application Policy {0}. The exception is {1}. IOException occurred when creating the application policy template in the hashmap of all the templates. Check the specified policy file. security.config.missingAttributeCertFilter=SECJ0322W: Missing attribute in Security Configuration. Required attribute CertificateFilter is missing. Certificate Filter is required when CertificateMapMode is CERTIFICATE_FILTER. Set CertificateFilter in the advanced LDAP settings. security.admintask.missingParameter.userRegistry.SECJ7770E=SECJ7770E: The {0} is missing in the active user registry object. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Naming.Console.Name=SECJ7112I: CORBA Naming Console Name None None security.policy.ratemplate.ioexception=SECJ0192E: Caught IOException while creating template for resource adaptor(read from WCCM) {1}. The exception is {0}. IOException occurred when creating the resource adaptor template in the hashmap of all the templates. Check the specified ra.xml file's permission specification. security.rolebauthz.authzfail.checkTrustedAppsProfileAuthzFailure=SECJ0433I: If the authorization failure is not expected, ensure that the profile for the J2EE role in the EJBROLE class has been configured correctly, as well as the BBO.TRUSTEDAPPS profile in the FACILITY class. The role of the J2EE application must be defined as a profile in the EJBROLE class. Additionally, through the use of the FACILITY class and BBO.TRUSTEDAPPS class profile, trusted application, as a general rule, are needed when you plan to use SAF authorization. You must ensure the requesting user or group has READ access to the role in the EJBROLE class. You must enable the trusted applications by ensuring that the WebSphere Application Server has SAF access of READ to the FACILITY class and profile of BBO.TRUSTEDAPP.<cell short name>.<cluster short name>. security.registry.ldap.mapcredentialNamingEx=SECJ0149E: Cannot map the credential of the given credential token for certificate subject DN {0} with filter {1} into LDAP because a NamingException occurred when searching LDAP. The NamingException is {2} A naming exception occurred when searching LDAP. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.beancache.adminperms.init=SECJ0095E: Exception while initializing admin permissions This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.ltpa.badtype=SECJ0374E: The accessID in the token contains the wrong type. It should be either user or group. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.zos.saf.idprop.mapping.failed=SECJ6232E: The distributed user could not be mapped to a SAF user, most likely because there was no match in the SAF database filters. The distributed user name is: {0}. The distributed realm name is: {1}. The distributed user could not be mapped to a SAF user, most likely because there was no match for the distributed user name and realm name in the RACMAP profiles of the SAF database. Verify that a RACMAP profile exists in the SAF database for the distributed user name and realm name. security.configrpt.core.supportedAuthMechList=SECJ7257I: Supported message layer authentication mechanisms None None security.admintask.CannotDeleteEncryptionKeyStore=SECJ7437E: Empty value specified for keystore. Cannot delete the encryption keystore when encryption is enabled or being enabled. Encryption is enabled or is being enabled. The encryption keystore is in use and cannot be deleted Disable encryption before deleting the encryption keystore. security.jaas.getORBInstanceReturnsNull=SECJ4011E: com.ibm.ejs.oa.EJSORB.getORBInstance() returns null com.ibm.ejs.oa.EJSORB.getORBInstance() returns null Make sure that the ORB is initialized correctly in the user application. security.audit.csi.cert.parse.audit=SECJ6133I: Parsing client certificate failed. Access to the resource is denied because the user or the groups the user is in does not have any of the required security role. No action required. security.configrpt.core.stateful=SECJ7051I: Stateful sessions None None security.registry.getgroups.error=SECJ0342E: Could not get the groups matching the pattern {0} because of the following exception {1}. Internal Error. Make sure that the groups matching the pattern exist in the registry. Contact your service representative if the problem persists. security.admintask.PasswordNotConfirmed=SECJ7399E: Audit encryption key store password does not match verify password. Encryption key store password and the confirm password values do not match. Confirm the audit encryption key store password security.registry.entry.findererror.privid=SECJ0073E: Error finding registry entry for privilege id {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.registry.uniqueid.notfound=SECJ0359E: Could not get the uniqueId for {0} because of the following exception {1}. An exception occurred when getting the uniqueId of a user or group. Make sure that the user or group is valid in the registry. If the active user registry is a custom registry, make sure a uniqueIds exist for the user or group. security.configrpt.core.sslEnabled=SECJ7224I: SSL enabled None None security.configrpt.core.trustFileFormat=SECJ7075I: Trust file format None None security.configrpt.core.isCredentialForwardable=SECJ7267I: Is Credential Forwardable None None security.jaas.parser.URL=SECJ4039E: {0} :ERROR: A file parser exception occurred with file : {1}. The exception is {2} IOException occurred trying to connect the specified URL. Investigate the exception. Check the specified URL. security.policy.filtered.permission=SECJ0318I: The permission {0} specified in the application policy file({1}) were filtered out. The permission specified in the application policy was removed because filer.policy has the same entry. none. This is an informational message. security.sa.set.props=SECJ0294E: Error setting properties to file ({0}). The exception is {1}. An IOException occurred when setting properties to the specified file. Verify that the property file exists, that it has read permission and is writable. security.encoding.notsupp=SECJ0065E: Unsupported encoding This is an internal error. An UnsupportedEncodingException occurred when the LTPAServer tried to encode the token value. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.j2c.calbackHandlerFactoryUndefined=SECJ4057I: WSMappingCallbackHandlerFactory implementation class {0} not defined. WSMappingCallbackHandlerFactory implementation class might be defined in security.xml to customize Mapping CallbackHandler. This is not an error condition. When the implementation class is not defined, a default WebSphere implementation will be used. No action is required unless one wants to override the WebSphere default WSMappingCallbackHandlerFactory implementation. security.servcomp.init=SECJ0288E: Error during security initialization. An unexpected exception occurred when updating the authorization table. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.zos.threadid.app.denied=SECJ6210W: Application thread identity synchronization has been disabled by the z/OS security product. The server has been configured to perform J2EE and operating system thread identity synchronization for applications that request it but the security product has not authorized the use of this support. Contact your security product administrator to request authorization to use thread identity synchronization. security.admintask.InvalidMonitorRef=SECJ7382E: Non valid reference for Audit Notification Monitor. Non valid reference for audit notification monitor specified. Verify that a valid reference has been specified for the audit notification monitor security.registry.ldap.mapcredentialNotFound=SECJ0150E: Cannot map the credential of the given credential token for certificate subject DN {0} with filter {1} into LDAP because no entry in LDAP matches the DN or filter No entry in LDAP can be found with the subject DN in the certificate or found with the filter. This might be the expected result depending on the subject DN in the certificate and filter. If the response is unexpected, review the certificate mapping filter defined in the LDAP advanced properties in the Security Center. security.sas.orbssl.init.exception=SECJ0248I: Caught unexpected exception in retrieving ORB SSL initialization. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.naming.invalidAccessIdFormat.SECJ7812E=SECJ7812E: AccessId is not formatted correctly. It should bin the form: user:<RealmName>/<uniqueId> or group:<RealmName>/<uniqueId>. The AccessId of needs to be in the form of user: or group: followed by the realm name slash uniqueId. Endure the AccessId is in the correct format. security.configrpt.Environment=SECJ7126I: Environment None None security.role.config.get=SECJ0267E: Failed to get RoleBasedConfigurator. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.sasconfig.filenotexist=SECJ0107W: The {0} file does not exist This exception is unexpected. The cause is not immediately known. If this message is from a warning, then it is a temporary problem which is usually recovered from automatically. If it is not a warning, then check the file permissions for the file to ensure that they are readable. If the file is missing, restore it. security.configrpt.No.Admin.Role.User=SECJ7099I: No Administrator User None None security.jaas.call.convertMapToString=SECJ4036E: {0} : Error: An exception occurred when trying to reflect on or invoke convertMapToString(). The exception is {1} Exception occurred trying to reflect on or invoke convertMapToString(). Investigate the exception. Check class path. security.jaas.priv.exception=SECJ4051E: PrivilegedActionException is caught while serialized Subject is being restored. The exception is {0}. PrivilegedActionException occurred while restoring the credential. This exception is a wrapper of the exception created in doPrivileged block. Investigate the real source of the exception. Contact your service representative if the problem persist. security.configrpt.core.authenticationLayerRetryCount=SECJ7065I: Authentication Layer Retry Count None None security.configrpt.core.external=SECJ7274I: External None None security.audit.service.event.exception.error=SECJ6017E: Unexpected Exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.CannotConfigSigning=SECJ7431E: Cannot configure signing when enable value is false. Signing for audit cannot be configured when the enable value is false. Either use true for enable or, if the intention is to disable/delete signing, use the appropriate disable/delete tasks. Specify true as the enable value if the intention is to configure signing for audit. security.admintask.safkeyring.cert.SECJ7822E=SECJ7822E: The certificate with the {0} alias cannot be used because it is not connected to both the servant and control region key rings. To use the certificate, it must be connected to both the servant and control region key rings. Ensure that the certificate is connected to both the servant and control region key rings. security.core.notauthzt=SECJ0112W: Authorization Table Not defined for Application {0} No security constraints or roles have been defined for this application. If security is not necessary for this application, ignore this message. Otherwise, review the security requirements of this application. security.admintask.WorkSpaceFailAddUsertoAdminAuthz=SECJ7310E: Workspace exception while adding user to admin-authz.xml An error occuring accessing the Workspace None security.sas.cleanup.repository=SECJ0249E: Failed to cleanup. The exception is {0}. An unexpected exception occurred during the cleanup of the specified repository. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.PasswordMissing=SECJ7398E: Missing password for the audit encryption key store. No password was supplied for the audit encryption key store. Supply a password for the audit encryption key store security.scanner.risk.ldaplink.ok.unused=SECJ7537I: User registry being used is not LDAP User registry being used is not LDAP None security.configrpt.core.Ext.authorizationProviders=SECJ7138I: External authorization providers None None security.admintask.naming.invalid.users.groups.remove.SECJ7759E=SECJ7759E: The following users or groups or special subjects {0} cannot be removed from role {1}. The users or groups are not assigned to this role and hence cannot be removed. Run the command by correcting the user, group or specialSubject list. security.configrpt.core.enableReplayDetection=SECJ7273I: Enable replay detection None None security.jacc.server.task.information=SECJ0400I: Successfully updated the application {0} with the appContextIDForSecurity information. Information only. Information only. security.audit.service.context.error=SECJ6023E: Auditing is enabled but could not get a handle to the audit context objects. Could not obtain a handle to the Audit context objects in order to be able to populate with event data. Examine the exception for the cause of the problem. security.audit.message.digest.error=SECJ6043E: Message digest data not valid Message digest is null or not valid. Verify that the message digest is not null or not valid. security.jacc.install.task.error=SECJ0396E: Error updating information to the JACC provider for application {0}. The exception is {1}. Cannot provide the security policy information to the JACC provider because of the exception. Without this information the authorization decisions, cannot be made correctly when security is enabled. Make sure that the JACC provider is properly configured and can be accessed. After the problem is fixed, either re-install the application or run the propagatePolicyToJACCProvider tool to propagate the policy information to the JACC provider. For more information about this tool, search for propagatePolicyToJaccProvider in the information center documentation. security.admintask.authMechanismNotValid.SECJ7721E=SECJ7721E: The authentication mechanism is not valid. The authentication mechanism type is not valid it should be LTPA or KRB5. Ensure the authentication mechanism type is valid. security.configrpt.core.requiresEJBArgumentsPolicyContextHandler=SECJ7038I: Requires the EJB arguments policy context handler for access decisions None None security.init.nullsecobject=SECJ0365E: Cannot create security object during initialization. The security object cannot be created from the repository. This is an internal error. The security.xml might be corrupted or missing. Contact your service representative. security.policy.parser.cannotcreateclass=SECJ0227E: An exception occurred when creating class of type {0}. The exception is {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.adminApp.installation.failed=SECJ0138E: Failed to install the admin Application - This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.enabled=SECJ7008I: Administrative security None None security.admintask.CannotDeleteNotification=SECJ7438E: Empty value specified for notification reference. Cannot delete the audit notification when audit notification is enabled or is being enabled. Audit notification is enabled or is being enabled. The notification reference may be in use and cannot be deleted. Disable audit notification before deleteing the audit notification reference. security.rolebauthz.nocred2=SECJ0326E: No received or invocation credential exist on the thread. The Role based authorization check will not have an accessId of the caller to check. The parameters are: role name {0}. The stack trace is {1}. No invocation or received credentials were established on this thread. This might cause the role based authorization check to fail. The stack trace is obtained by a local throw catch block that might be useful for debugging the problem. security.admintask.naming.invalid.roleName.SECJ7760E=SECJ7760E: The role name {0} does not exist. The role name is not a valid role. Use a valid role. security.saml.invalid.key.format.SECJ8050W=SECJ8050W: The {0} key format has the wrong format for SAML TAI custom property key. The key format should be sso_<ID>.idp_<ID>.* or sso_<ID>.sp.* . The SAML TAI custom property key format is invalid. Verify the SAML TAI custom property key format. security.audit.report.Record.name=SECJ7444I: Record Number None None security.admintask.AdminNotFoundInReg=SECJ7333E: Could not find admin name in the specified user registry Admin name does not exist in the specified user registry Ensure that the admin name exists in the user registry prior to executing command security.audit.build.event.object.error=SECJ6040E: Unexpected exception while creating the audit record object. Exception = {0}. An error occurred while building the auditable record data. Examine the exception for the cause of the problem. security.sa.chk.password.unknown=SECJ0298E: Error checking password for user :{0}. The exception is {1}. Unknown exception occurred when checking the password for specified user. Verify that the password for the specified user. security.jaas.SystemInputError=SECJ4025E: unable to get system input stream {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.password=SECJ7018I: Password None None security.admintask.InvalidScopeName=SECJ7441E: Empty or non valid value specified for scope name. Non valid value was specified for the scope name. An empty value is not valid. Specify a valid value for the scope name security.admintask.NotificationConfigured=SECJ7386E: Audit notification already configured. Audit notification already exists. None security.sas.decode.error=SECJ0105E: An unexpected exception occurred when decoding the value [{0}] for password [{1}] in the security configured URL The encoded password cannot be decoded because it is missing or malformed. Verify that the passwords in the security configuration URL are not corrupted or missing. Reset the affected password through the WebSphere Admin console if possible. If all else fails, reset the password to its plain text value in the security configuration URL (which is usually sas.server.props). security.admintask.KeyStoreException=SECJ7462E: Exception was raised while trying to get an instance of the keystore with the specified keystore type and provider type. An instance of the keystore could not be obtained. Verify that the encryption keystore does exist. security.configrpt.core.authenticationStrategy=SECJ7045I: Authentication strategy None None security.audit.mapping.success.audit=SECJ6149I: Principal/Credential mapping succeeded. The J2EE Connection principal/credential mapping was successful. No action is required. security.jacc.init.error=SECJ0391E: Error when setting the Policy object to the provider''s policy implementation {0}. The exception is {1}. The provider's policy implementation cannot be loaded because of the exception. Make sure that the JACC provider properties are set correctly and the provider classes are in the class path. If problem persists, contact your service representative. security.jaas.nullCreds=SECJ4002E: No CORBA Credentials for {0}/{1} Authentication failure occurred while invoking login() of realm/user since there is no CORBA credential. Confirm if the user information(realm name, user name password) is valid. security.jacc.initialize.error=SECJ0412E: An Error occured when initializing the initialization class {0} of the JACC provider. The exception or the error code is {1}. The initialization implementation of the provider failed with an exception or a non-zero error code. Verify that the JACC provider properties are correctly set and that the initialization classes are in the class path. Check the provider implementation for problems. An error code of zero (0) indicates success. security.configrpt.core.supportedQOP=SECJ7053I: Supported ciphers None None security.policy.invalid.permission=SECJ0315W: The permission {0} specified in the application policy file:{1} does not exist. The permission class specified in the application policy file(was.policy or app.policy) does not exist. Fix the specified application policy file. security.configrpt.core.ejbAuth=SECJ7134I: RMI/IIOP security None None security.configrpt.Configurator.Role.Group=SECJ7111I: Configurator Group None None security.audit.service.mapping.default.audit=SECJ6019I: AuditEventType = {0}, AuditOutcome = {1}, AuditOutcomeReason = {2}, unique Event ID = {3}, Cell Name = {4}, Node Name = {5}, Server Name = {6}, Component Name = {7}, App Name = {8}, Provider Name = {9}, Provider Successful = {10}, Original Realm = {11}, Original User Name = {12}, Mapped Realm = {13}, Mapped User Name = {14}, Exception = {15}. This message is intended to be used by the defaultAuditEventFactoryImpl sendMappingAuditEvent method only. No action required. security.registry.userdisplayname.error=SECJ0349E: Could not get the display name of the user {0} because of the following exception {1}. Internal Error. Make sure that the user is valid and has a display name. Contact your service representative if the problem persists. security.web.authz.checkdataconstraint.failed=SECJ0392E: Error when checking the dataconstraint requirement for the contextID {0}. The exception is {1}. Could not determine the dataconstraint requirements for this resource. The request will be denied. Make sure that the dataconstraint requirements are correctly configured in the deployment descriptor. security.audit.keystore.open.error=SECJ6026E: Exception while opening up audit keystore file. Exception = {0}. Could not open the audit keystore. Examine the exception for the cause of the problem. Ensure that the audit keystore exists. security.admintask.FailedAutogenServerId=SECJ7332E: Failed to auto-generate the Server Id Could not auto-generate a Server Id None security.invalid.creds=SECJ0010E: Invalid credential This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.saml.invalid.id.map.SECJ8058E=SECJ8058E: Invalid SAML idMap value {0}. The valid value are idAssertion, localRealm, or localRealmThenIdAssertion. The value of idMap is invalid. Specify a valid idMap value. security.web.form.noWebAppInfo=SECJ0119E: Error getting the web app information for form login. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.OutputLocationNotHTML=SECJ7460E: The output file location specified is not an HTML file. The output log for the read audit records must be in HTML format. The output file specified was not in HTML format. Specify an HTML file as the output file location. security.ltpa.exportkeys=SECJ0377E: Error exporting LTPA keys. The exception is {0}. Cannot export LTPA keys. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.scope.not.in.domain.SECJ7719E=SECJ7719E: {0} is not mapped to the {1} security configuration. The scope is not mapped to the security configuration. Rerun the command using a scope that is mapped to the security configuration. security.audit.sso.validate.audit=SECJ6110I: SSO token {0} was validated successfully. Authentication was successful. No action is required. security.admintask.noTrustAssociation.SECJ7730E=SECJ7730E: No trust association was found. An LTPA auth mechanism must contain a trust association. Ensure that an LTPA auth mechanism contains a trust association. security.registry.getusrsforgrp.error=SECJ0345E: Could not get the users in the group {0} because of the following exception {1}. Internal Error. Make sure that the group is valid. Contact your service representative if the problem persists. security.swam.callback.ex=SECJ0259E: IOException from CallbackHandler. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jacc.tools.earfile.error=SECJ0406E: Cannot obtain the earFile for application {0}. The earFile is required to get the security policy information for the application. The configuration repository might be corrupted. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.saml.idp.signing.cert.notexistent.SECJ8060W=SECJ8060W: There is no signing certificate in the IdP metadata file {0}. The signing certificate is missing from the IdP metadata file. Verify the IdP metadata file. security.jacc.tools.object.error=SECJ0405E: The {0} object cannot be obtained because of the following error {1}. Could not get the object required for security policy propagation. Make sure that the JACC provider properties are set correctly in the JACC configuration. Also make sure that all the provider classes are in the class path of all the servers. security.admintask.globalfedoption.globalfedchange.SECJ7828W=SECJ7828W: Altering the existing federated repository configured at the global security domain may affect any application security domains configured to use the global federated repository option. Changing the federated repository configuration at the global security domain may affect any application security domain configured with the global federated repository option. Ensure that changing the existing federated repository configuration at the global security domain does not affect an application security domain configured to use the global federated repository option. security.admintask.modeNotValid.SECJ7734E=SECJ7734E: Certificate mode type is not valid. Valid certificate mode types are: EXACT_DN or CERTIFICATE_FILTER. Ensure that the certificate mode type is a valid type. security.jacc.tools.pcf.null=SECJ0403E: The PolicyConfiguration object for the contextID {0} is null. Could not get the JACC provider PolicyConfiguration object. This object is required to propagate the security constraints information to the provider. Make sure that the JACC provider property javax.security.jacc.PolicyConfigurationFactory.provider is set correctly to the PolicyConfigurationFactory implementation class. The preferred way to set this property is to use the JACC configuration properties panel or wsadmin tool. Also make sure that the provider classes are in the class path of all the servers. security.configrpt.Admin.Role.User=SECJ7098I: Administrator User None None security.admintask.NoCertKeyFileNameValue=SECJ7405E: No value was specified for the key file name for the certificate to import When selecting to import an existing certificate, a key file name for the certificate must be entered. Supply a key file name for the certificate to import security.manager.install=SECJ0308I: Java2 security is installed. JAVA2 security is enabled. None, informational only. security.admintask.noAuthDataEntry.SECJ7732E=SECJ7732E: The specified auth data entry does not exist. The specified auth data entry does not exist. Either create the auth data entry, or specify a different auth data entry which does exist. security.configrpt.core.limit=SECJ7268I: Limit None None security.zos.threadid.skip.surrogate.enabled=SECJ6213I: Thread identity synchronization will not subject to SURROGAT authorization. WebSphere will not perform SURROGAT class authorization checks prior to creating native security environments. No user action is required. security.init.roleauthz=SECJ0204I: Rolebased authorizer initialized successfully The Rolebased authorizer initialized successfully None. Informational only. security.admintask.noCertAlias.SECJ7745E=SECJ7745E: A certificate alias must be provided when a key store is provided. When a key store object is provided a certificate alias must be provided. Run the command providing a certificate alias. security.admintask.ExceptionSetGlobalSec=SECJ7338E: Exception raised while setting Global Security setting Caught exception while setting Global Security setting None security.configrpt.core.name=SECJ7036I: Name None None security.configrpt.core.maxKeyReferences=SECJ7198I: Maximum key references None None security.configrpt.core.trustManagerClass=SECJ7178I: Class name None None security.configrpt.core.Auth.Config=SECJ7031I: Authorization configuration None None security.j2c.initFailure=SECJ4058E: WSDefaultPrincipalMapping Initialization failed. The exception is {0}. WSDefaultPrincipalMapping initialization failed. The JCA container managed principal/credential mapping most likely will not work properly. Examine the cause of the exception and correct the problem. The most likely cause for this error is that the WSMappingCallbackHandlerFactory implementation class was not configured properly. security.configrpt.core.isStateful=SECJ7271I: Stateful sessions None None security.sap.warning.serializing.custom.objects.from.subject=SECJ5002W: An error occurred while serializing the custom object {0} from the current Subject. This does not cause the request to fail but this custom object will not get propagated. The object mentioned above probably does not implement the java.io.Serializable interface. Ensure that the object implements the java.io.Serializable interface to ensure it gets propagated downstream. security.configrpt.core.isKeyPair=SECJ7196I: Specifies a key pair instead of a key None None security.multidomain.runtime.SECJ7807W=SECJ7807W: The cell resource {0} is specified in the domain-security-map.xml file during addNode. This resource is converted to the server resource {1}. If a federated node contains a domain associated with the cell scope, it will be changed to the server scope for that node during the addNode operation so that current cell configuration is not impacted. If the cell scope needs to be configured in the domain-security-map.xml file, you need to associate the cell resource after the node has been federated. security.saml.file.missing.SECJ8055E=SECJ8055E: You must specify a fully qualified path for the {0} file. The given parameter file name is not a fully qualified pathname or null. Specify a fully qualified pathname for the file in the given parameter. security.configrpt.core.DomainSecurity=SECJ7258I: Security domains None None security.configrpt.core.Security.systemLogin=SECJ7093I: System logins None None security.admintask.ClassNotDefaultEmitter=SECJ7433E: Cannot change the default audit service provider implementation classname. The classname specified does not match the default audit service provider implementation classname. Ensure that when specifying class name on the modify command and the implementation is the default audit service provider implementation, that it matches the default classname. security.scanner.risk.admin.role.ok=SECJ7522I: Multiple Administrative User Roles are configured. A number of administrative roles are defined to provide degrees of authority that are needed to perform certain administrative functions from either the Web-based administrative console or the system management scripting interface. The authorization policy is only enforced when administrative security is enabled. Multiple Administrative User Roles are configured. A number of administrative roles are defined to provide degrees of authority that are needed to perform certain administrative functions from either the Web-based administrative console or the system management scripting interface. The authorization policy is only enforced when administrative security is enabled. None security.configrpt.core.trustManager=SECJ7145I: Trust managers None None security.jaas.IdentityAssertion.state=SECJ4064E: Trust state information missing in shared state, unable to perform identity assertion. A Custom Login module must be provided and configured prior to this login module in the JAAS Login Configuration and should have provided trust information in shared state. Check a Custom Login Module is provided and configured prior to this login module in the JAAS Login Configuration and make sure that the shared state information is set correctly based on the requirement. security.audit.cert.mapping.audit=SECJ6119I: Authentication failed becasue the client certicate user name cannot be mapped to WebSphere Application Server user. The authentication failed because the client certificate user name cannot be mapped to a valid WebSphere Application Server user. The user might not be defined in the registry. Otherwise, verify the registry and mapping configuration. security.audit.service.provider.default.audit=SECJ6020I: AuditEvent = {0} AuditEventFactory Name = {1}. This message is intended to be used by the defaultAuditServiceProviderImpl sendEvent method only. No action required. security.admintask.NoKeyStore=SECJ7423E: No keystore found matching the supplied unique name or reference id. Cannot find a keystore with the supplied unique name or reference id. None security.configrpt.Naming.Role.Value=SECJ7114I: CORBA Naming Role Value None None security.scanner.risk.app.security.improve=SECJ7527W: Application security is disabled. Application security enables security for the applications in your environment. This type of security provides application isolation and requirements for authenticating application users. Application security is disabled. Application security enables security for the applications in your environment. This type of security provides application isolation and requirements for authenticating application users. Enable application security if applicable. security.authn.failed.user=SECJ0335E: Authentication failed for user {0}. The registry failed to return a user after authentication. This would happen if the authentication was not successful and the custom registry did not throw exceptions to indicate this. Make sure you are entering a current userID and password for authentication. This problem might have preceeded by other problems. Looking at those problems might narrow the problem down. security.audit.emitter.config.error=SECJ6039E: Configuration error: no audit service providers are defined. No Audit Service Providerimplementations are found in the configuration. Ensure that there is at least one audit service provider configured. security.configrpt.core.nlsRangeKey=SECJ7184I: NLS Range Key None None security.multidomain.runtime.SECJ7806E=SECJ7806E: The LTPA token validation fails because the current realm {0} does not match or trust the realm in the token {1}. LTPA validation checks to make sure that the current realm matches the realm in the token for validation to work. For successful validation make sure that the realm in the token is configured in the trusted inbound realms list for the current realm. security.secsrv.ltpaconfigerr=SECJ0238E: An unexpected exception occurred when trying to create the initial LTPAServerObject. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.required=SECJ7085I: Required None None security.configrpt.core.cacheTimeout=SECJ7006I: Authentication cache timeout None None security.admintask.oldResourceCluster.SECJ7776E=SECJ7776E: The cluster has one or more members that is not version 7.0 or greater. One of the members is {0} in node {1} that is not version 7.0 or greater. The server must be running a 7.0 or greater version to be mapped to a domain. Ensure that servers are at the correct level. security.scanner.risk.corba.ok=SECJ7528I: CORBA Naming roles are configured CORBA Naming roles are configured None security.policy.ratemplate.parser=SECJ0200E: Caught a ParserException while adding the grant entry {1} to the policy template of the resource adaptor {0}. The exception is {2}. A ParserException occurred while adding the grant entry to the policy template of the resource adaptor. Check the syntax of permission specification in the specified ra.xml security.multidomain.runtime.SECJ7805I=SECJ7805I: The resource is not being accessed using secure HTTPS protocol. This message is for informational purposes only. It indicates that the security HTTPS protocol is not used when accessing the resource. If the resource is implemented to be accessed using the non-secure HTTP protocol, no action is required. If this resource should only be accessed using HTTPS change the deployment descriptor to add appropriate data-constraints. security.admintask.verifyUserRegistry.SECJ7724E=SECJ7724E: Error in the user registry configuration unable to verify access to the user registry. An error occurred trying to access the user registry. Unable to verify the registry is configured properly. Ensure the user registry is configured correctly. security.configrpt.Certificate.Expiry=SECJ7132I: Certificate Expiry None None security.registry.initerr=SECJ0331E: The registry implementation file {0} cannot be initialized because of the following exception {1} The specified custom registry implementation cannot be initialized. Make sure all of the properties required for the custom registry initialization are passed through the GUI or scripting (whichever is being used). If this happens for WebSphere Application Server provided registries, contact your service representative if the problem persists. security.ErrorCreatingLTPAKeys=SECJ0040E: Error occurred while generating new LTPA keys. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.policy.module.path=SECJ0311W: An exception was caught while trying to get the module {1} absolute filepath. The exception is {0}. Could not get the module's absolute filepath. Check the filepath given to load the module. security.admintask.loginDoesNotExist.SECJ7735E=SECJ7735E: The login object does not exist. The login object does not exist in the configuration. Ensure that the login object exists. security.configrpt.core.AuthMechanism=SECJ7135I: Authentication mechanisms and expiration None None security.admintask.SPNEGOFilterInvalid=SECJ7741E: Filter is malformed, verify syntax of the specified filter rules. The specified filter rules are not valid. Verify the filter rules conform to the syntax supported by the default HTTPHeaderFilter class. security.configrpt.core.deleteOldKeys=SECJ7195I: Delete key references that are beyond the maximum number of keys None None security.admintask.InvalidTimeStamp=SECJ7458E: Non valid timestamp specified. Timestamp must be in "MMddhhmmyyyy" format. A non valid value was specified for timestamp of audit records to report Specify a non-empty or valid value for the timestamp. security.audit.form.login.failed.audit=SECJ6117I: Authentication failed due to missing or incorrect user name and/or password. Redirect to {0}. Form based Authentication failed due to missing or incorrect user id or password. Typically a web user will be redirect to a login page to retry. No action is required. security.multidomain.runtime.SECJ7804I=SECJ7804I: The following security configuration {0} is configured at the security domain {1}. This message is for informational purposes only. It will list some of the security properties that are configured at the security domain level. No action is required. security.configrpt.core.tokenExpiration=SECJ7245I: Token timeout None None security.configrpt.core.additionalTrustManagerAttrs=SECJ7179I: Additional Trust Manager attributes None None security.configrpt.core.domainName=SECJ7025I: Domain name None None security.jsecman.debugnorethrow=SECJ0381I: Warning, the com.ibm.websphere.java2secman.norethrow property is true. The WebSphere Java 2 Security Manager is not rethrowing AccessControl exceptions. This debug setting should not be used in a production environment. See the InfoCenter for Java 2 Security debugging features. The com.ibm.websphere.java2secman.norethrow property, when it has a true value, instructs the Java 2 Security Manager to NOT rethrow AccessControl exceptions. This property is intented to assist developers when they are preparing their applications for Java 2 Security. When this property value is true, the Security Manager reports the AccessControl exception but does not rethrow or propagate the exception up the call stack. This might permit applications to access resources that would they would otherwise not have access to. This property should not be specified in a production environment, only in a debug or application development environment. If this message is unexpected or the application is running in a production environment, remove the com.ibm.ws.java2secman.norethrow property setting unless you understand the consequences. security.audit.authz.role.failure.audit=SECJ6151I: The user does not have the required roles {0}. The user has not been granted any one of the required roles. No action is required. security.admintask.NoKeyStoreTypeValue=SECJ7412E: No key store type was specified for the audit key store. Must specify a key store type for the audit key store Supply a key store type for the audit key store security.sasconfig.currenterror=SECJ0051E: IOException when determining whether configuration is current with property file {0} or {1} A loadProperties() operation probably failed. Verify that the file associated with security configuration URL property file (typically sas.server.props) has read permission and is writable. security.audit.sharedkey.generation.error=SECJ6025E: Failure generated a shared key. Exception = {0}. A failure occurred during shared key generation. Examine the exception for the cause of the problem. security.admintask.InvalidOutcome=SECJ7368E: Non valid or no reference specified for the audit outcome. The outcome field is required. Verify that a valid reference has been specified for the audit outcome security.multidomain.runtime.SECJ7803I=SECJ7803I: Application security is disabled in security domain {0}. This message is for informational purposes only. No action is required. security.jaas.invalid.cred2.exception=SECJ4055E: InvalidCredential exception is caught while serialized Subject is being restored. The exception is {0}. InvalidCredentialType exception occurred while restoring the credential. Investigate the SAS problem. Contact your service representative if the problem persist. security.audit.service.authn.default.audit=SECJ6016I: AuditEventType = {0}, AuditOutcome = {1}, AuditOutcomeReason = {2}, unique Event ID = {3}, Cell Name = {4}, Node Name = {5}, Server Name = {6}, Component Name = {7}, App Name = {8}, Session ID = {9}, Resource Name = {10}, Resource Type = {11}, Realm = {12}, Authn Mechanism = {13}, Authn Method = {14}, User Name = {15}, Provider Name = {16}, Provider Successful = {17}, Subject = {18}, Caller List = {19}, Remote Addr = {20}, Remote Host = {21}, Remote Port = {22}, Exception = {23}. This message is intended to be used by the defaultAuditEventFactoryImpl sendAuthnAuditEvent method only. No action required. security.configrpt.core.useLocalSecurityServer=SECJ7013I: Use the local security server None None security.configrpt.core.sessionGCIdleTime=SECJ7063I: Session GC Idle Time None None security.configrpt.core.Http.Only=SECJ7277I: HttpOnly custom property None None security.admintask.InvalidEmailList=SECJ7394E: Non valid email list specified. The email list specified is not valid, null or empty. Supply a valid email list security.servcomp.init.warning=SECJ0286W: Error during security initialization. Unexpected exception occurred when initializing security server component. None. This is warning. security.multidomain.runtime.SECJ7802I=SECJ7802I: Application security is enabled in security domain {0}. This message is for informational purposes only. No action is required. security.configrpt.core.claims=SECJ7050I: Claims None None security.jaas.invalid.cred.exception=SECJ4053E: InvalidCredential exception is caught while serialized Subject is being restored. The exception is {0}. InvalidCredentialType exception occurred while restoring the credential. Investigate the SAS problem. Contact your service representative if the problem persist. security.admintask.FailedAutogenLTPA=SECJ7331E: Failed to auto-generate the LTPA password Could not auto-generate an LTPA password None security.configrpt.core.clientAuthentication=SECJ7069I: Client authentication None None security.admintask.noUserRegistry.SECJ7723E=SECJ7723E: {0} is not configured unable to set it to the active user registry. Unable to set the active user registry because the user registry provide is not configured. Ensure the user registry is configured before setting it to the active user registry. security.configrpt.core.authConfig=SECJ7015I: Authentication configuration None None security.jaas.invaldCredType=SECJ4006E: Invalid Credential Type {0} Getting the JAAS subject from CORBA credential failed with exception. Contact your service representative with exception stack trace information present in the error log. security.sambean.urerr=SECJ0232E: An unexpected exception occurred when trying to get the User Registry from the Security Server. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.multidomain.runtime.SECJ7801I=SECJ7801I: Java 2 security is enabled in security domain {0}. This message is for informational purposes only. No action is required. security.configrpt.domain.User.Registry=SECJ7261I: User Realm None None security.admintask.multidomain.clusterMapping.SECJ7786E=SECJ7786E: The {0} member cannot be added to the {1} cluster since the cluster is associated with a security domain. A server from previous releases cannot be added to a cluster when the cluster is associated with a security domain either directly or indirectly. Mixed clusters are not supported with security domains. security.configrpt.core.fileBased=SECJ7163I: File-based key store None None security.registry.ldap.mapcredential=SECJ0067E: Cannot map the credential of the given credential token for subject DN {0} into LDAP because of an LDAP filter mapping exception. The credential mapping can fail for a number of reasons: The credential token is not an instance of a supported CredentialToken type for a mapping. The principal identified in the credential cannot be mapped to an entry or found in the user registry. A user registry exception occurs or if the user registry has been stopped. Verify that the user registry is operational. Also verify that the principal exists in the target user registry if appropriate. The exception reported with this error message might help to diagnose the problem. security.jacc.tools.rcf=SECJ0402E: Error getting the RoleConfiguration object for the contextID {0}. The exception is {1}. Could not get the JACC provider RoleConfiguration object. This object is required to propagate the authorizationTable information to the provider. If the authorizationTable information is required by the provider, make sure that the JACC provider properties related to the RoleConfigurationFactoryImplClass is set correctly. Also make sure that the implementation classes are in the class path of all the servers. security.sa.no.registry=SECJ0293E: No registry. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.multidomain.runtime.SECJ7800I=SECJ7800I: The following login configurations {0} are available for security domain {1}. This message is for informational purposes only. No action is required. security.jacc.install.task=SECJ0409E: An exception occurred when propagating the security policy information for application {0} to the JACC provider. The exception is {1}. Because of an exception, the security policy information might not have been propapated to the provider during the application installation. Make sure that the provider is up and running and the JACC configuration is correct. Once the problem is fixed, one can also use the wsadmin tool to manually propagate the security policy information to the provider instead of reinstalling the application. See the information center documentation for more details on running this tool. If problem persists, contact your service representative. security.admintask.nonceValue.SECJ7746E=SECJ7746E: The nonce cache timeout value must be greater than the token timeout value. If the nonce cache timeout is less than the token timeout, then the token could be used multiple times since the nonce value would have expired prior to the token becoming not valid. Run the command specifying a nonce value greater than the token expiration. security.jaas.removeCORBACredException=SECJ4018E: Removing CORBA Credential during cleanup {0} Exception occurred while removing CORBA credential. Contact your service representative with exception stack trace information present in the error log. security.admintask.noRealm.SECJ7725E=SECJ7725E: The user registry has no realm name defined. Unable to make this user registry the active user registry because it does not have realm name defined. Ensure the user registry has a realm name. security.admintask.ExceptionGettingWizardSettings=SECJ7335E: Exception raised while getting wizard security settings Caught exception while getting wizard security settings None security.policy.parser.malformedurlexception=SECJ0301W: Failed to convert a file path {0} to CodeSource. The exception is {1} MalformedURLException occurred when trying to convert the specified path to URL. Verify that the policy files, xml files(resource.xml) to confirm the class path specified in them are correct. security.admintask.oldResource.SECJ7775E=SECJ7775E: Resource {0} cannot be part of any security domain becuase, its product version is not 7.0 or greater. Check the corresponding node''s product version. The server must be running a 7.0 or greater version to be mapped to a domain. Ensure that servers are at the correct level. security.configrpt.No.Moderator.Role.User=SECJ7103I: No Moderator user or group None None security.bind.server.error=SECJ0256E: Error binding SecurityServer to naming. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.InvalidEmailFormat=SECJ7385E: Non valid email format specified. Must either specify "html" or "text". Supply a valid email format security.configrpt.core.sessionGCInterval=SECJ7064I: Session GC Interval None None security.admintask.NotBinaryImpl=SECJ7392E: The audit service provider referenced is not an IBM Binary service provider implementation. The referenced service provider is not the default IBM Binary service provider implementation. Enter a valid reference to a IBM Binary service provider implementation security.authn.failed.nouser=SECJ0361E: Authentication failed for {0} because user is not found in the registry. Authentication failed because the user does not exist. Make sure that the user is valid in the registry. Also, when using LDAP, make sure that the user is searchable. The admin id in some LDAP servers might not be searchable. security.web.ta.intsig=SECJ0122I: Trust Association Init Interceptor signature: {0} Reports the signature of the Trust Association interceptor. None, informational only. security.admintask.missingParameter.krb5Config.SECJ7772E=SECJ7772E: The {0} is missing in the Kerberos configuration file {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Configurator.Role.User=SECJ7104I: Configurator User None None security.audit.service.no.context.audit=SECJ6101I: Web access security context not found. A web request is rejected because no web access security context is configured. The cause might be a simple user error or an indication of potential threat where malicious users explore the weakness of web applications. You might perform a correlation analysis of security auditing events. security.web.form.createWebAttr=SECJ0266E: Failed to create a new web attribute. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.send.mail.error=SECJ6048E: Failure sending audit notification. An error occurred while sending an audit notification. Examine the error logs for the cause of the problem. security.admintask.noLoginModulNamed.SECJ7774E=SECJ7774E: Login module cannot be created using the name of the login module proxy class {0}. The login module proxy class name cannot be used when creating a new login module. Ensure the login module proxy class is not used when creating a login module. security.sas.futureconfigurl.error=SECJ0048E: Error updating or loading future security configuration URL specified by property {0} The path or file specified in the property might be not valid or there could be a file permission problem. Verify that the path and file specified by the property is valid and the file has read permission. security.configrpt.core.sso.ssl.required=SECJ7281I: Single signon requires SSL None None security.jaas.IdentityAssertion.context=SECJ4065W: Principal and X509Certificate provided in the trust information, using the principal. Both a principal and X509Certificate are provided in the trust information, the principal has priority and will be used for the login. If login with the X509Certificate is desired then the principal should not be passed in the trust information. security.admintask.MissingDeleteParms=SECJ7379E: No attributes specified on the delete command. No attributes were specified on the delete command. Supply attribute(s) to delete the specified object security.admintask.noIdentity.SECJ7743E=SECJ7743E: When useServerIdentity is false then a trusted identity should be provided. When a user specifies useServerIdentity is false then a trusted identity should be provided. Run the command specifying a trusted id. security.configrpt.core.daysBeforeNotification=SECJ7209I: Expiration notification threshold None None security.admintask.mechanismNotValid.SECJ7710E=SECJ7710E: Authentication mechanism is not valid. Valid authentication mechanisms are: KRB5, LTPA, Custom, BasicAuth. Ensure that the authentication mechanisms is valid. security.init.adminapp=SECJ0202I: Admin application initialized successfully The Admin application initialized successfully None. Informational only. security.jsecman.installed=SECJ0132I: Java 2 Security is enabled Java 2 Security Manager is installed. None, informational only. security.policy.sysext.parserexception=SECJ0187E: Caught ParserException while creating template for System Extension Policy of type {1} The exception is.{0} ParserException occurred when creating the system extension template in the hashmap of all the templates. Check the ParserException data. Check the specified policy file. security.sa.get.props=SECJ0295E: Error getting properties to file ({0}). The exception is {1}. An IOException occurred when getting properties from the specified file. Verify that the property file exists, and that it has read permission. security.SecurityContext.getActualCreds=SECJ0270E: Failed to get actual credentials. The exception is {0}. Unexpected exception occurred when trying to run getActualCredential() method. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.merge.notadded=SECJ0382I: The alias {0} from the server level security has not been updated to the cell. Informational. During the server and the cell security object merging, if a same alias name exists in both, the alias is not copied to the cell configuration. This is as designed. Normally, this should not happen since the alias names are unique. However, if a removeNode operation has been performed prior to the addNode operation, you might see this message since the removeNode does not remove the existing aliases. Also, if the alias names in the security.xml file were manually changed, then this message appears if the aliases match. security.admintask.noActiveUserRegistsry.SECJ7720E=SECJ7720E: Unable to enable security when there is no active user registry. There is an attempt to enable global security when there is no active user registry defined. Ensure an user registry is defined when enabling global security. security.zos.saf.authz.allFailed=SECJ6237E: Authorization failed. The SAF user {0} does not have {1} access to any of the following SAF profiles in the EJBROLE class: {2}. Authorization failed for the user. Consult with the SAF administrator for granting the necessary access in the SAF database. security.jaas.get.initCtx=SECJ4056E: Error getting initial context. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.scopeNotValid.SECJ7718E=SECJ7718E: {0} is not a valid resource name. The resource name provided is not valid. Ensure a valid resource name is provided. security.authtbl.relhome=SECJ0093E: Relation home not found This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.NoCertKeyFilePathValue=SECJ7406E: No value was specified for the key file path for the certificate to import When selecting to import an existing certificate, a key file path for the certificate must be entered. Supply a key file path for the certificate to import security.configrpt.core.Security.property.name=SECJ7091I: Name None None security.configrpt.core.reuseConnection=SECJ7222I: Reuse connection None None security.admintask.certNotInKS.SECJ7750E=SECJ7750E: Certificate {0} is not in key store {1}. The certificate alias provided is not in the key store. Run the command providing a certificate alias that is in the key store. security.zos.saf.threadid.sync.ipt.warning=SECJ6226W: Thread identity synchronization of user "{0}" is not allowed on the "initial pthread task." The BPX1TLS service does cannot be called from the initial pthread task (IPT). If this service is called on the IPT, future calls to perform connection management or application thread identity synchronization will fail. No action is required. security.admintask.CannotDeleteCertAlias=SECJ7439E: Empty value specified for the certAlias. Cannot delete the certificate alias when audit encryption is enabled or is being enabled. Audit encryption is enabled or is being enabled. The certificate alias is in use and cannot be deleted. Disable audit encryption before deleteing the certificate alias. security.zos.threadid.app.enabled=SECJ6209I: Application thread identity synchronization is enabled. The server has been configured to perform J2EE and operating system thread identity synchronization for applications that request it. No user action is required. security.configrpt.core.keyManagerClass=SECJ7186I: Class name None None security.find.server.error=SECJ0257E: Failed to find security server in name space. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.spnego.errorDeleteLastFilter.SECJ7798E=SECJ7798E: Can not delete the last SPNEGO filter because SPNEGO Web authentication is enabled. The SPNEGO Web authentication is enabled, it requires at least one SPNEGO filter. Disable SPNEGO Web authentication before delete the last SPNEGO filter. security.configrpt.core.keyReference=SECJ7199I: Key reference None None security.sap.warning.propagation.token.exists=SECJ5004W: Trying to add propagation token name {0} and version {1} that already exists on the thread. The existing PropagationToken is returned and will not be overwritten. Cannot overwrite an existing PropagationToken. The existing one is returned, so use it to set new attributes given the proper permission. Check the addPropagationToken SPI for the value returned. A null value indicates this is the first time the token is added. A non-null value indicates you are setting the token again which is not allowed. Use the returned value to add new attributes. security.admintask.FoundOtherWIMFlavors=SECJ7305E: Found other virtual member manager repository configurations. Only the built-in virtual member manager file-based repository is supported through the wizard Found other virtual member manager repository configurations but only file-based is supported in the wizard None security.audit.auditorId.change.error=SECJ6051E: User name specified as the auditor ID does not have auditor privileges. Cannot assign a user who does not have the auditor role as the primary auditor. Ensure the user specified is given the auditor role or select a user who already has the auditor role. security.jaas.callBackHandlerException=SECJ4014E: Login Module {0} detected unsupported {1} callback in CallbackHandler {2} Unsupported Exception occurred while processing callbacks Check the application. Contact your service representative with exception stack trace information present in the error log if the problem persists. security.policy.sysext.param=SECJ0176E: An exception was caught while getting the policy template of type {1}. The exception is {0}. Could not retrieve the policy template of the above type. This is an internal error. However, it could be caused by an incorrect xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.configrpt.core.SingleSignon=SECJ7143I: Single signon (SSO) None None security.policy.parser.decodeexception=SECJ0299E: An exception was caught while decoding the file path: {0}. The exception is {1}. Failed to decode the specified file. The details is shown in the exception. Verify that the policy files, xml files(resource.xml) to confirm the class path specified in them are correct. security.jaasconfig.helper.baddata=SECJ4032E: Method {0} detected missing or malformed data when trying to perform conversion. The data item name is {1} and value is {2}. Internal problem related to malformed or corrupted data storage. Contact your service representative with exception stack trace information present in the error log. security.init.wccmjaas.init=SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class. The WCCM JAAS login configuration information was pushed to the JAAS configuration object. None. Informational only. security.zOS.SecurityManager.PermissionFailure2.warning=SECJ6206W: The current Java 2 Security policy report a potential violation of a Java 2 Security Permission. Stack Trace:{0} The Java Security Manager checkPermission() threw a SecurityException. A caller on the call stack does not have the required permission. Verify that the attempted operation is permitted by examining all Java 2 security files and application code. Additional permissions might be required. security.admintask.InvalidSequenceSet=SECJ7450E: Non valid sequence set specified. Either a single sequence record number can be specified or a group of sequence records may be specified as begin:end. A non valid value was specified for the sequence set of audit records to report Specify a non-empty or valid value for the sequence set. security.jaas.LoginException=SECJ4000E: JAAS Login Exception occurred at {0}. JAAS Login exception occurred while refreshing the credential. Confirm user id, password and realm information are correct. If you still see the problem, contact your service representative with exception stack trace information present in the error log. security.jaas.tokenloginvaldationfailure=SECJ4034I: Token Login failed. If the failure is due to an expiring token, verify the system date and time of the WebSphere nodes are synchronized or consider increasing the token timeout value. Authentication mechanism {0} and exception is {1} Token Authentication failure might be caused by an expired token, token that is not valid, or a date or time synchronization problem between WebSphere nodes. Web browsers often cache WebSphere SSO cookies which contain the token to validate. These tokens do expire. Token validation failures are not always unexpected given that tokens can expire. might consider increasing timeout value or verifying that the system date and time between WebSphere nodes is synchronized. security.jacc.tools.appname.error=SECJ0407E: Cannot obtain the application name for propagating the security constraints to the provider. The appname is required to propagate the security policy information to the provider. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.csi.session.authztoken.audit=SECJ6139I: The authorization token is invalid. Parsing the client authorization token failed. Need to determine if this is caused by programming error. security.disabled.during.login=SECJ0429W: A login has occurred while admin security is disabled. An UNAUTHENTICATED Subject will be returned since most security subsystems are unavailable. When admin security is disabled we do not initialize user registry or other services needed to properly authenticate. Therfore, we will return an UNAUTHENTICATED Subject to ensure the runtime continues to operate. If an authenticated JAAS Subject is desired, you must enable at least administrative security in the security configuration. security.configrpt.core.webAuthAttrs=SECJ7153I: Web Authentication None None security.zos.saf.delegation.enabled=SECJ6216I: SAF delegation is enabled. The APPLDATA associated with the profile representing the J2EE role will be used to determine the id of a user that is in the role. An invocation Subject will be built with a credential for that user. No user action is required. security.admintask.jaspi.provider.exists.SECJ8009E=SECJ8009E: Authentication provider {0} is already defined in domain {1}. The name of each authentication provider must be unique. Specify a unique name for the authentication provider. security.authz.noowncreds=SECJ0054E: No own credentials This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.sso.exception.audit=SECJ6111I: SSO token {0} failed validation with an Exception. Authentication failed due to internal failure. Examine the cause of the exception and correct the problem. If the problem persists, contact your service representative. security.admintask.authCacheTimeout.SECJ8022E=SECJ8022E: Authentication cache timoue value invalid. Timeout must be less than or equal to the LTPA token timeout value. The authentication cache timeout value must be less than or equal to the LTPA token timeout value. Specify a timeout value that is less than or equal to the LTPA token timeout value. security.admintask.NoCertAliasToImport=SECJ7409E: No name was specified for the certificate alias to import When selecting to import an existing certificate, a certificate aliase for the certificate must be entered. Supply a certificate alias name for the certificate to import security.configrpt.core.useNativeAuthorization=SECJ7269I: Use native authorization None None security.configrpt.Naming=SECJ7127I: Naming None None security.zos.saf.idprop.distributedRealm.null=SECJ6229E: The distributed realm name is null. The distributed realm name is null and will not be mapped not a SAF user. Specify a valid distributed realm name. security.web.ta.userex=SECJ0127E: Unable to find a valid user for Trust Association When the WebAuthenticator invoked an interceptor to return the authenticate user name, no such user name was returned. Verify that the reverse proxy server is inserting the correct user name in the HTTP request before it sends the request to WebSphere. security.admintask.UserNotInRole=SECJ7469E: The user has not been included in the required role of "{0}". The user must be included in all the required roles needed to run the task. Ensure the acting user has been given the proper role(s). security.adminApp.installation=SECJ0137E: Could not get EnterpriseAppHome This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.SecurityContext.restoreCreds=SECJ0271E: Error restoring original credentials. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.registryDoesNotExist.SECJ7704E=SECJ7704E: User registry does not exist in the security configuration. The user registry specified does not exist in the configuration. Rerun the command using a user registry that exist in the configuration. security.web.cred.getAttrFail=SECJ0114W: Unable to extract the security attributes from the credential The credential might be malformed or corrupted. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.domain.application.jaas=SECJ7263I: JAAS Application Logins None None security.ltpa.validate.verifytoken.failed=SECJ0372E: Validation of the inbound LTPA token failed. The configured LTPA keys are probably not the ones that generated the token signature. The LTPA keys might not be the correct ones needed to verify the signature of the token. This error occurs if the keys used to encrypt the token are not the same as the keys used to decrypt. If a new set of keys has been generated, this is an expected error. Any tokens signed using the old keys will no longer work. Contact your service representative if the problem persists. security.configrpt.core.useDomainQualifiedUserNames=SECJ7012I: Use realm-qualified user names None None security.jaas.call.convertMapToString2=SECJ4045E: {0} : Error: An exception occurred when trying to reflect on or invoke convertMapToString(). The exception is {1} Exception occurred trying to reflect on or invoke convertMapToString(). Investigate the exception. Check class path. security.admintask.NotificationInUse=SECJ7387E: Audit notification is in use. Audit notification is in use and cannot be deleted. None security.swam.remove.cred.ex=SECJ0263E: Exception occurred when removing WSCredential during cleanup. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.integrity=SECJ7059I: Integrity None None security.audit.report.Outcome.name=SECJ7446I: Outcome None None security.configrpt.core.registryClassName=SECJ7174I: Custom registry class name None None security.audit.basic.exception.audit=SECJ6127I: Basic authentication failed due to internal error. Basic Authentication failed and a runtime exception was caught. Report this problem to IBM. security.configrpt.core.serverPassword=SECJ7030I: Server user password None None security.ejb.beanperm.matchmetherr=SECJ0221E: An unexpected exception occurred in findMatchingMethod for method {0} and bean {1}, the exception is {2} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.type=SECJ7168I: Type None None security.domain.app.deploy.error.SECJ7782E=SECJ7782E: You cannot install an application across multiple security domains. Make sure that all the deployment targets belong to the same security domain. Application cannot be installed accross multiple security domains. Verify that user is not installing this application accorss multiple security domains. security.scanner.risk.admin.role.every.all.improve=SECJ7541W: Special subject "{0}" is configured for the Administrator role. It is not recommended to have Everyone and AllAuthenticatedUsers specified for the Administrator role. A special subject is configured for the Administrator role. It is not recommended to have Everyone and AllAuthenticatedUsers specified for the Administrator role. refer to the infoCenter to determine if a more secure configuration is more suitable. security.configrpt.core.allowLTPAFallback=SECJ7235I: Allow fallback to LTPA None None security.admintask.notServerType.SECJ7797E=SECJ7797E: The resource must be a single server resource in order for it to be converted to a security domain. The resource provided is not a single server resource. Ensure the resource provided is a single server resource. security.ltpa.importkeys=SECJ0376E: Error importing LTPA keys. The exception is {0}. Cannot import LTPA keys. This error occurs when the password used to import the keys does not match the password that encrypted the keys. Make sure that the password is the same. If the problem persists, contact your service representative. security.admintask.createDummyDomain.SECJ7808I=SECJ7808I: The domain {0} has been created because a cell wide domain exists in a mixed version setup. This special domain is created to associate previous version servers, clusters and SIBuses to this domain. If any of the old servers, clusters and SIBuses need to use the cell wide domain instead of the special domain, they need to be removed from this special domain. This might impact the security configuration of the resources deployed in these processes based on the cell wide domain security configuration. security.configrpt.core.deleteOld=SECJ7210I: Delete old certificate after replacement None None security.configrpt.Deployer.Role.Group=SECJ7229I: Moderator Group None None security.wsaccessmanager.classnotfound=SECJ0159E: Cannot find class {0} The Vendor specified Authorization Table class could not be found in the CLASSPATH. Make sure that the vendor's implementation of Authorization Table as specified in the sas.server.props file is in the CLASSPATH. security.policy.appparser.expandperm=SECJ0165W: Expand exception occurred. Skip the permission entry in app.policy file. The exception is {0}. An expand exception occurred while expanding the permission in the application policy file. Check the permission entry syntax in the application policy file (app.policy or was.policy). To identify which policy file has a problem, enable security trace for the component com.ibm.ws.security.policy.*. The trace.log file will contain the policy name. security.zos.saf.role.mapper.exception=SECJ6225E: Unable to load the custom SAF role to profile mapper "{0}" due to the following exception: {1} WebSphere was unable to load and and instantiate the configured class. This is generally due to an incorrect class name. Verify that the specified class name is correct and that it can be loaded by the WebSphere class loader. security.policy.filterparser.expandperm=SECJ0167W: Expand exception occurred. Skip the permission entry in filter.policy file. The exception is {0}. While expanding the permission entry in filter.policy file, caught an expand exception Check the permission entry syntax in filter policy file. security.merge.proceeding=SECJ0383I: Proceeding with merging the server's security configuration with the cell's for this Application Server. Informational. This message appears when the Application Server contains its own security configuration that must be merged with cell level configuration. security.admintask.null.krbRealm.SECJ7769E=SECJ7769E: The Kerberos realm name is null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.sasconfig.shutdown.error=SECJ0050E: Error encountered while shutting down the server An unexpected RemoteException, OpException or IOException occurred during server shutdown. There could be problems with loading or writing of security configuration URL property files. Verify that the file associated with security configuration URL property file (typically sas.server.props) has read permission and is writable. security.admintask.jaspi.provider.exists.SECJ8000E=SECJ8000E: Authentication provider {0} is already defined in the cell. The name of each authentication provider must be unique. Specify a unique name for the authentication provider. security.domain.app.deploy.warning.SECJ7783W=SECJ7783W: The application is being installed across deployment targets that use different security domains. Depending on the security attributes defined in the security domains this can cause security problems. The application is being installed across deployment targets that use different security domains. Depending on the security attributes defined in the security domains this can cause security problems. Refer to the information center documentation for more information before you proceed with this installation to make sure that you would not run into any security related issues. security.fips.enabled=SECJ0417I: FIPS is enabled. The server is running in FIPS mode, using the IBMJCEFIPS provider. No user action is required. security.configrpt.core.version=SECJ7201I: Version None None security.jaas.NoUtil=SECJ4019E: Not supposed to construct Util object Util object instance should not be constructed. Check the user application. Util should not be directly constructed. security.admintask.InvalidAuditorPwd=SECJ7359E: Non valid or no value specified for auditor password. The auditor password is a required field. Verify that a value has been specified for the auditor password security.roleauthz.appnoload=SECJ0219E: Unable to obtain or use a role-based authorizer because application {0} has not been loaded. The application must be loaded for the role base authorizer can be used to enforce authorization. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.create.remote.server.error=SECJ0255E: Error creating security server/ The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.enableCryptoHardwareSupport=SECJ7070I: Cryptographic token None None security.configrpt.Naming.None=SECJ7121I: No roles defined None None security.configrpt.No.Configurator.Role.User=SECJ7105I: No Configurator user or group None None security.registry.nullrealm=SECJ0356E: Could not get the realm for the registry in windows. Not able to get the host name of the Windows machine or the domain controller. Make sure that the user who is running WebSphere Application Server has administrative and "act as part of operating system" privileges on the Windows machine and is also an administrator in the domain machine. Contact your service representative if the problem persists. security.audit.csi.authn.success.audit=SECJ6148I: Authentication succeeded. The authentication was successful. No action is required. security.registry.usersecurityname.error=SECJ0354E: Could not get the name of the user whose uniqueId is {0} because of the following exception {1}. Internal Error. Make sure that the user is valid. Contact your service representative if the problem persists. security.policy.appparser.expandgrant=SECJ0166W: Expand exception occurred. Skip the grant entry in app.policy file. The exception is {0}. An expand exception occurred while expanding the grant entry in the pplication policy file. Check the grant entry syntax in your application policy file (app.policy or was.policy). To identify which policy file has a problem, enable security trace for the component com.ibm.ws.security.policy.*. The trace.log file will contain the policy name. security.configrpt.Naming.Console.Path=SECJ7115I: CORBA Naming Console Path None None security.audit.logout.success.audit=SECJ6152I: Form Logout. The HTTP session is cleaned up after form logout. No action is required. security.checkProviderList.warning=SECJ0414W: FIPS is enabled but the IBMJCEFIPS provider is not active in the java.security file. To ensure FIPS algorithms usage for all WebSphere Application Server process types, uncomment the IBMJCEFIPS provider in the java.security file, ahead of the IBMJCE, and renumber the provider list in sequential order. When the server is running in FIPS mode the IBMJCEFIPS provider should be in the java.security file. The java.security file needs to be changed to include the IBMJCEFIPS provider in the provider list before the IBMJCE provider. security.audit.basic.missing.audit=SECJ6124I: Basic authentication data is missing. Send out 401 challenge. The authentication failed because there is no user id and password information in the HTTP header. WebSphere Application Server will send a 401 challenge to the web client. No action is required. security.policy.parser.filenotexist=SECJ0300W: The file or directory ( {0} ) does not exist. The specified file or directory does not exist. Verify that the policy files, xml files(resource.xml) to confirm the class path specified in them are correct. security.audit.csi.session.nocred.audit=SECJ6137I: ASSOC_ACCEPT message is illegal at the target. The client might not be using correct configuration. The message type ASSOC_ACCEPT should not be received at the target server. This might occur due to an exception that occurred on the client which caused a mixup. Check the client configuration to ensure that there's nothing out of the ordinary that might be causing an exception to occur. security.manager.disabled=SECJ0309I: Java 2 Security is disabled. Java 2 Security Manager is NOT installed. None, informational only. security.j2c.unexpectedExceptionNewURL=SECJ4028E: Unexpected Exception caught in new URL {0} : Exception is {1} Unexpected exception occurred while creating a new URL. Check the specified URL. Contact your service representative with exception stack trace information present in the error log. security.configrpt.No.Operator.Role.User=SECJ7101I: No Operator user or group None None security.admintask.checkHostPort.SECJ7825E=SECJ7825E: The number of LDAP hosts in the ldapHost parameter needs to equal the number of port numbers in the ldapPort parameter. When configuring multiple LDAP hosts there needs to be a port number provided for each hostname in the list of LDAP hosts. Ensure there is a port for each LDAP host in the list of LDAP hosts. security.servcomp.remove.DenyAllRole=SECJ0290W: All subjects assigned to Special role DenyAllRole for application {0} are removed. All subjects assigned to Special role DenyAllRole for the specified application are removed. None. This is a warning. security.admintask.CannotConfigEncryption=SECJ7430E: Cannot configure encryption when enable value is false. Encryption for audit cannot be configured when the enable value is false. Either use true for enable or, if the intention is to disable/delete encryption, use the appropriate disable/delete tasks. Specify true as the enable value if the intention is to configure encryption for audit. security.admintask.LogNotEncrypted=SECJ7455I: The Binary Audit Log specified is not encrypted. The Binary Audit Log specified has not been encrypted. none security.profiletask.FailedAddAdminId=SECJ7355E: Failed to add the adminID to the user registry object Failed to add the adminID to the user registry object None security.audit.csi.gss.format.audit=SECJ6140I: Invalid GSS security token format. GSS security context token contains OID number that is not valid or authentication mechanism that is not valid. No action required. security.admintask.identitySpecified.SECJ7712E=SECJ7712E: Either use the server identity or specify a trusted identity not both. If user server identity is enabled a trusted identity and password should not be specified. Specify either a trusted identity or enable user server identity. security.audit.event.factory.config.error=SECJ6037E: Configuration error: no audit event factories are defined. No Audit Event Factory implementations are found in the configuration. Ensure that there is at least one audit event factory configured. security.audit.notify.config.error=SECJ6049E: Error in the audit notification configuration. Audit system failure policy set to WARN or FATAL, but notification configuration is not properly configured. Ensure audit notification is configured. security.admintask.FilterNotConfigured=SECJ7393E: Audit specification not configured. The referenced audit specification does not exist in the audit.xml. None security.admintask.InvalidUniqueName=SECJ7361E: Non valid or no reference specified to uniquely identify this implementation. The uniqueName reference is a required field. Verify that a valid reference has been specified for the uniqueName security.sa.chk.password=SECJ0296E: Error checking password for user :{0}. The exception is {1}. com.ibm.websphere.security.PasswordCheckFailedException occurred when checking the password for specified user. Verify that the password for the specified user. security.configrpt.core.CertExpMonitor=SECJ7152I: Manage certificate expiration None None security.admintask.multidomain.globalSecurity.SECJ7787I=SECJ7787I: The {0} member is being associated with the global security configuration. This message is for informational purposes only. No action is required. security.configrpt.Console.Role.Name=SECJ7096I: Administrative Role Name None None security.jaas.missingToken=SECJ4010E: Credential Token is null or empty array Credential token is missing. Confirm that the necessary authentication data is passed. security.admintask.invalid.serviceName=SECJ7546E: The service name {0} is not valid. It contains a slash character (/). This exception is unexpected. The cause is not immediately known. The service name contains the slash character. The service name is the first component of the Kerberos service principal name. security.admintask.InvalidActionType=SECJ7356E: Unsupported audit system failure action type The audit system failure action type provided is not supported. Supported types are: WARN, NOWARN, and FATAL Verify the audit system failure action type is correctly specified security.admintask.CannotRemoveAuditorPwd=SECJ7436E: Empty value specified for auditorPwd. Cannot delete the auditorPwd when auditing is enabled. Auditing is enabled and requires an auditorId and auditorPwd. Disable auditing before deleting the auditorPwd security.policy.filter.parserexception=SECJ0195E: Caught ParserException while adding permission to the set of filtered permissions. The exception is {0}. ParserException occurred when adding permission to the set of filtered permissions. Check the ParserException data. security.admintask.InvalidEventFactory=SECJ7371E: Non valid or no reference specified for the audit event factory implementation. The eventFactory field is required. Verify that a valid reference has been specified for the audit event factory implementation security.policy.perminstance.targetexception=SECJ0197E: Caught Invocation TargetException while constructing the permission object. This exception might be due to syntax error in the policy file. The exception is {0}. Invocation TargetException occurred while constructing the permission object. Check the exception. security.web.loginFail=SECJ0117E: Form login failed for user {0} The user could not be authenticated by the FormLogin Servlet. The user id or password might have been entered incorrectly. The user might not exist in the user registry that WebSphere is configured to authenticate to. Verify that the user id and password are entered correctly. Consult with the administrator of the user registry if the problem persists. security.zos.saf.idprop.enabled.info=SECJ6234I: The SAF feature for distributed identity mapping is in effect. The SAF feature for distributed identity mapping is in effect. Distributed users will be mapped to SAF users using the filters defined in the SAF RACMAP profiles. No user action is required. security.configrpt.core.interceptors=SECJ7022I: Interceptors None None security.jaas.noCORBAToken=SECJ4005E: No CORBA Credentials for credential token JAAS Login returned null credential while invoking login() with token. There is no CORBA Credential. login returned null Credential. Check the user application how it authenticate. Enabling security debug trace will provide the details.(com.ibm.ws.security.auth.* ) security.init.wccmjaas.setcfgerror=SECJ0216E: An exception occurred when setting JAAS login provider configuration class to {0}. The exception is {1}. WebSphere provides an implementation of the javax.security.auth.login.Configuration class. This class could not be set at server startup. Configuration.class might not be present. This is an internal error. security.audit.service.optional.audit=SECJ6012I: Security Auditing is optional. This audit message indicates that security auditing records are optional. No action is required if this is the desired setting. Note that the intention of this auditing policy is not to suspend a business transaction when security auditing records cannot be saved. security.policy.sysextparser.ignoreperm=SECJ0174W: Permission entry {0} is being ignored In the system extension policy files, the permission entries with signatures are not supported in the current version. Remove the signature values from the permission entry in the system extension policy file. (spi.policy or library.policy) security.j2c.unexpectedExceptionOpenURL=SECJ4029E: Unexpected Exception caught in openStream URL {0} : Exception is {1} Unexpected Exception occurred while opening an URL. Check the specified URL. Contact your service representative with exception stack trace information present in the error log. security.SecurityContext.setCreds=SECJ0272E: Error setting to system credentials. An unexpected exception occurred while restoring the original credentials. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.Security.Settings=SECJ7002I: Security Settings None None security.jaas.LoginFailure=SECJ4001E: Login failed for {0}/{1} {2} Authentication can fail for many reasons. The user or password might not have been entered correctly, misspelled for instance. The user account might not exist, might have expired, or be disabled. The password might have expired or require a change at first logon. If WebSphere security is configured to use LDAP as the user registry, the WebSphere security LDAP user and group search filter configuration might not match what the LDAP directory expects. Confirm that the user information (realm name, user name, password) is valid. Try authenticating the user directly to the configured user registry outside of WebSphere authentication to verify that the user and password are valid in the user registry. The WebSphere information center documents additional user account requirements for specific user registries. security.audit.service.required.audit=SECJ6001I: Security Auditing is required. This audit message indicates that security auditing records are required. No action is required if this is the desired setting. Note that the intention of this auditing policy is not to commit a business transaction unless the required security auditing records can be saved. security.web.ta.genexc=SECJ0128E: An unexpected exception occurred during Trust Association. The exception is {0}. This refers to all other exceptions that can be possibly created by an interceptor, when validating trust with the reverse proxy server and when getting the authenticated user name, aside from WebTrustAssociationFailedException and WebTrustAssociationUserException. Debug the problem from the stack trace that is printed together with this error message. You can also turn on the debug trace to get more information about the nature of the exception. security.configrpt.core.AuthMechanism.Expiration=SECJ7136I: Authentication expiration None None security.web.internalservererror=SECJ0087E: Internal Server Error The HttpServletResponse indicates an Internal Server Error has occurred. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.ExceptionLDAPConnect=SECJ7340E: Exception raised trying to connect to LDAP server Exception raised connecting to the LDAP server Verify input parameters are correct security.configrpt.core.requiresSSL=SECJ7026I: Requires SSL None None security.audit.service.bad.uri.denied.audit=SECJ6100I: Invalid URI. A web request is rejected because it contains a URI name that is not valid. Incorrect URI might be a simple user error or an indication of potential threat where malicious users explore the weakness of web applications. You might perform a correlation analysis of security auditing events. security.configrpt.Certificate.Management=SECJ7133I: Certificate Management None None security.admintask.sslConfigNotValid.SECJ7711E=SECJ7711E: SSL configuration is not valid. Valid ssl configuration not supplied. Ensure that the ssl configuration is exists. security.authz.failed.invalidcreds=SECJ0052E: Authorization failed while invoking ({0}){1} {2} - invalid credentials This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.hoverHelpKey=SECJ7182I: Hover help key None None security.getting.remote.server.error=SECJ0252E: Error getting remote security server. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.j2c.missingParameter=SECJ4060W: Cannot find parameter {0} that might be needed by Mapping LoginModules. Either the custom properties HashMap or the authentication data alias was not defined. This might not be a problem depending on the particilar mapping LoginModules. security.audit.csi.session.expired.audit=SECJ6136I: Session or token expired. The security token in the security context has expired. Typically token has a finite expiration time and this condition might be normal. security.audit.emitter.binary.log.error=SECJ6032E: Failure writing audit record out to the binary log. Exception = {0}. IO error writing the audit record to the binary log. Verify the log exists. Examine the exception for the cause of the problem. security.admintask.globalfedoption.globalnonfedappset.SECJ7829E=SECJ7829E: Cannot set the user registry of an application security domain to use the federated repository when the global federated repository option is enabled and the global security domain is not using the federated repository. The global federated repository option has been enabled in the application security domain. The global security domain must be configured with a federated repository as the active user registry in order to make the federated repository the active repository of the application security domain. Either the global security domain should be configured with a federated repository as the active user registry or the application security domain should elect not to use the global federated repository option. This should be done before attempting to set the active user registry to use the federated repository in the application security domain. security.registry.unsupportedclass=SECJ0329E: The registry implementation file {0} is not a instance of the supported user registries. This can happen when using custom registries and if they are not instances of UserRegistry or CustomRegistry. Make sure you implement the UserRegistry interface for your custom registry. security.policy.wccm.custom.permission=SECJ0196W: Custom permission {0} is being used in an application policy file {1} Custom permission is being used in an application policy file. Make sure that it is all right to use a custom permission in an application policy file. security.wsaccessmanager.instantiationerror=SECJ0160E: Can not instantiate class {0} The vendor specified Authorization Table class could not be instantiated. Make sure that the vendor's implementation of Authorization Table as specified in the sas.server.props file could be loaded and instantiated. security.init.mbeanerror=SECJ0206E: Error creating or registering {0} mBean. The exception is {1} An unexpected exception occurred when trying to create or register an mBean. There might be a problem with the configuration. The exception might include details. security.admintask.cannotRemoveDomain.SECJ7809E=SECJ7809E: The {0} domain can not be delete because a the cell is a mixed version setup. The cell is in mixed version setup. The special security domain can not be removed. This operation can not be performed in the current configuration. security.configrpt.minutes=SECJ7171I: minutes None None security.audit.service.event.default.audit=SECJ6015I: AuditEvent = {0}, AuditEventFactory Name = {1}. This message is intended to be used by the defaultAuditServiceProviderImpl sendEvent method only. No action required. security.audit.csi.idassertion.failure.audit=SECJ6143I: Authentication failed. Could not validate Client Authentication Token or Client Certificates during Identity Assertion. No action is required. security.configrpt.core.Cookie.Protection=SECJ7275I: Cookie Protection None None security.web.ta.loadclasserr=SECJ0125E: Trust Association Init Unable to load Trust Association class {0}. A ClassNotFoundException occurred when trying to load the subject class. Verify that the appropriate Trust Association classes are installed and the class path is correct. security.audit.retrieve.signer.error=SECJ6027E: Exception while retrieving the signer information from the audit signer certificate. Exception = {0}. A failure occurred while retrieving the audit signer certificate. Examine the exception for the cause of the problem. Ensure that the signer certificate exists. security.configrpt.core.nonceCacheTimeout=SECJ7244I: Nonce cache timeout None None security.sambean.noltpaserver=SECJ0379E: Cannot get LTPAServer in the security MBean. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.cert.encode.error=SECJ6028E: Exception retrieving a certificates''s encoded bytes UTF-8 format. Exception = {0}. Certificate encoding error. Examine the exception for the cause of the problem. security.admintask.unsetActiveUserRegistry.SECJ7727E=SECJ7727E: Unable to unset the activeUserRegistry attribute when global security is enabled. The activeUserRegistry attribute must point to a user registry object when global security is enabled. Ensure global security is not enables when changing unsetting the activeUserRegistry. security.audit.csi.session.conflict.audit=SECJ6135I: Session does not exist on server. The client context id is inconsistent with session state. This problem should be analyzed to determine whether it was due to program or operational error or due to spoofing attempt. security.registry.impl.stopped=SECJ0066E: registry impl object has been stopped This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.NoCertKeyFileTypeValue=SECJ7407E: No value was specified for the key file type for the certificate to import When selecting to import an existing certificate, a key file type for the certificate must be entered. Supply a key file type for the certificate to import security.registry.loadclass=SECJ0330E: The registry implementation file {0} cannot be loaded because of the following exception {1} This can happen when the specified custom registry cannot be loaded. The custom registry implementation file should be in the class path as mentioned in the custom user registry section in the information center documentation. If this happens for WebSphere Application Server provided registries contact your service representative if the problem persists. security.get.initCtx=SECJ0274E: Error getting Initial Naming Context. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Naming.Delete.Name=SECJ7125I: Delete None None security.admintask.SPNEGOFilterExists=SECJ7739E: Filter object already exists. The specified object already exists. Unable to create another one. Create the object with a unique name. security.policy.was.key=SECJ0312W: {$Application} phrase should not include ${was.module.path} keyword. Syntax error in the policy file. ${Application} phrase should not include ${was.module.path} keyword. This entry is ignored. Check the application policy file. security.configrpt.core.keySetGroup=SECJ7148I: Key set groups None None security.sap.error.creating.opaque.token=SECJ5000E: The following exception occurred while creating the attribute propagation token: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jacc.updated.task=SECJ0410E: An exception occurred when updating the security policy information for application {0} to the JACC provider. The exception is {1}. Because of an exception, the security policy information might not have been updated to the provider during the application update. Make sure that the provider is up and running and the JACC configuration is correct. Once the problem is fixed, one can also use the wsadmin tool to manually propagate the security policy information to the provider instead of reinstalling the application. See the information center documentation for more details on running this tool. If problem persists, contact your service representative. security.zos.saf.idprop.distributedUser.null=SECJ6228E: The distributed user name is null and will not be mapped not a SAF user. The distributed user name is null and will not be mapped not a SAF user. Specify a valid distributed user name. security.configrpt.core.realm=SECJ7028I: Realm None None security.configrpt.Moderator.Role.Group=SECJ7110I: Moderator Group None None security.zos.saf.idprop.distributedUser.tooLong=SECJ6230E: The distributed user name exceeds the maximum length of {1}. The distributed user, {0}, will not be mapped to a SAF user. The distributed user name exceeds the maximum allowable length. Specify a valid distributed user name. security.registry.loadproperr=SECJ0327E: Problem loading the registry properties file. The exception is {0}. Unexpected exception occurred when loading registry properties file. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Certificate.Console.Name=SECJ7129I: Console Name for Certificate Management None None security.admintask.spnego.noFilter.SECJ7781E=SECJ7781E: Cannot enable SPNEGO Web authentication without defining any SPNEGO Web authentication filters. Cannot enable SPNEGO Web authentication without defined any SPNEGO Web authentication filter. Create at least one SPNEGO Web authentication filter before enabled the SPENGO Web Authentication. security.admintask.SPNEGOFilterInvalidURL=SECJ7740E: The URLs specified is malformed. A MalformedURLException was encountered parsing one of the specified URLs. Verify the URL syntax is correct. security.configrpt.core.enableProtection=SECJ7058I: Enable Protection None None security.configrpt.Console.Group=SECJ7107I: Administrative Group Roles None None security.configrpt.No.Deployer.Role.User=SECJ7228I: No Deployer user or group None None security.registry.unsupported.entrytype=SECJ0075E: Unsupported entry type {0} This is an internal error. A registry of the specified type could not be looked up. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.saml.tai.notexist.SECJ8044E=SECJ8044E: SAML TAI configuration is not found. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.dupType.SECJ7761E=SECJ7761E: Only specify one parameter, securityDomainName, resourceName, or securityRealmName. Only one parameter can be used at time either securityDomainName, resourceName, or securityRealmName. Run the command and specify either securityDomainName, resourceName, or securityRealmName, security.configrpt.core.keyFileFormat=SECJ7071I: Key file format None None security.registry.isvalidgroup.error=SECJ0355E: Validating the group {0} throws the following exception {1}. Internal Error. Make sure that the group is valid. Contact your service representative if the problem persists. security.ssl.decode.error=SECJ0145E: An unexpected exception occurred when decoding password in initial_ssl.properties This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.saml.unsupport.version.SECJ8053E=SECJ8053E: The SAML TAI version in the IdP partner metadata file is not supported. It supports SAML version 2.0 only. The SAML TAI version in the IdP partner metadata file is not supported. Use SAML version 2.0 in the IdP partner metadata file. security.configrpt.Naming.Server=SECJ7118I: ServerId None None security.configrpt.core.appEnabled=SECJ7137I: Application security None None security.sa.chk.password.custom=SECJ0297E: Error checking password for user :{0}. The exception is {1}. com.ibm.websphere.security.CustomRegitryException exception occurred when checking the password for specified user. Verify that the password for the specified user. security.admintask.resourceRemovedFromSecurityDomain.SECJ7818I=SECJ7818I: The resource {0} has been removed from the security domain {1} since the resource no longer exists. Once a resource is removed from the system, its association with any domain will also be removed. No action is required. security.admintask.strategyTypeNotValid.SECJ7706E=SECJ7706E: Authentication strategy type is not valid. Valid authentication strategy types are: REQUIRED, REQUISITE, SUFFICIENT, OTPIONAL. Ensure that the authentication strategy type is a valid type. security.scanner.risk.app.security.ok=SECJ7526I: Application security is enabled. Application security enables security for the applications in your environment. This type of security provides application isolation and requirements for authenticating application users. Application security is enabled. Application security enables security for the applications in your environment. This type of security provides application isolation and requirements for authenticating application users. None security.wccmjaas.no.alias=SECJ0302W: No alias name for {0}. This configuration does not have any alias name. No action is required. This is a warning message. security.admintask.InvalidBinaryRef=SECJ7373E: Non valid reference to Binary File audit service provider implementation. Reference must be to a Binary File audit service provider implementation. Verify that a valid reference has been specified to a Binary File implementation security.authn.failed.multiusers=SECJ0360E: Authentication failed for {0} because multiple users matched the user. Authentication failed because multiple users were found in the registry with the same name. When using LDAP, make sure that the user shortname is unique. For example, if "uid" is used as the shortname, make sure that the uid is unique in the registry. security.ltpa.credmap.failed.nullaccessid=SECJ0063E: Credential mapping failed due to invalid access ID This is an internal error. Cannot get accessID from credential. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.tai.mapping.audit=SECJ6116I: Authentication failed becasue Trust Accosication Interceptor user name cannot be mapped to WebSphere Application Server user. The authentication via the specified Trust Association Interceptor failed because the asserted user name cannot be mapped to a valid WebSphere Application Server user. If this problem persists, the mapping problem is likely to be caused either by incorrect TAI configuration or by TAI implementation. security.configrpt.core.autoReplace=SECJ7208I: Automatically replace expiring self-signed certificates None None security.ltpa.factory.init.error=SECJ5014E: Could not find the factory class {0} specified for this token. The exception is {1}. The LTPA TokenFactory implementation is likely not present in the class path. Ensure that the LTPA TokenFactory implementation is located in the WebSphere class path. Typically these implementations are put in the ${WAS_INSTALL_ROOT}/classes directory. security.scanner.risk.java2.ok=SECJ7534I: Java 2 security is enabled. Java 2 security provides a policy-based, fine-grain access control mechanism that increases overall system integrity by checking for permissions before allowing access to certain protected system resources. Java 2 security guards access to system resources such as file I/O, sockets, and properties. Java 2 security is enabled. Java 2 security provides a policy-based, fine-grain access control mechanism that increases overall system integrity by checking for permissions before allowing access to certain protected system resources. Java 2 security guards access to system resources such as file I/O, sockets, and properties. None security.secsrv.basic.destroy=SECJ0276E: BasicAuthData credential is already destroyed. The exception is {0}. CredentialDestroyedException occurred while trying to get BasicAuthData. The credential was already destroyed. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.mg.finderr.key=SECJ0099E: Error finding method group for id {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.init.roleauthz.geterr=SECJ0218E: An exception was caught retrieving RoleBasedAuthorizer. The exception is {0}. The Rolebased authorizer could not be retrieved due to an exception. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wsaccessmanage.get.reg=SECJ0304E: Cannot get user registry. The exception is {0}. Unexpected exception occurred when getting user registry. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.activeAuthMechanism=SECJ7003I: Active authentication mechanism None None security.sasconfig.registryattrs=SECJ0108E: Unexpected exception occurred when getting user registry or registry attributes. This exception is unexpected. The cause is not immediately known. Verify that the user registry has been configured in WebSphere properly. security.admintask.NoCertAliasValue=SECJ7404E: Missing value for new certificate alias name. No value was specified for the new certificate alias name. Supply a value for the certificate alias name. security.admintask.SequenceSetOutOfOrder=SECJ7452E: Non valid sequence set specified: the beginning sequence number is greater than the ending sequence number. A non valid value was specified for the sequence set of audit records to report Make sure that the starting sequence number is less than the ending sequence number. security.registry.userdisplayname.notfound=SECJ0348E: Could not get the display name of the user {0}. Internal Error. Make sure that the user is valid and has a display name. Contact your service representative if the problem persists. security.registry.ldap.invalidID=SECJ0323E: Invalid LDAP user/group ID Using invalid user/group ID or the user/group ID is not a directory entry. The directory administration ID (root DN) is not a directory entry on most LDAP servers. Verify that the user/group ID is a valid directory entry. security.audit.csi.authn.failure.audit=SECJ6147I: Authentication failed. Examine the exception for reason of failure. No action is required. security.registry.ldap.connect.audit=SECJ0418I: Cannot connect to the LDAP server {0}. Security is unable to connect to some target Lightweight Directory Access Protocol (LDAP) servers, which might prevent future failover. If you need to bring up additional servers for failover, verify that the required LDAP server is running. security.admintask.authLevelNotValid.SECJ7709E=SECJ7709E: Authentication level is not valid. Valid authentication levels are: Never, Supported, Required. Ensure that the authentication level is valid. security.configrpt.core.enableTrust=SECJ7021I: Enable trust association None None security.web.ta.loadint=SECJ0120I: Trust Association Init loaded {0} interceptor(s) Reports the number of Trust Association interceptors that have been added. None, informational only. security.wsaccessmanager.classloading=SECJ0268E: Problem loading class {0}, using default authorization table provided by WebSphere The Vendor specified Authorization Table could not be loaded successfully. Therefore, using WebSphere provided authorization table. Check to make sure that the Vendor's implementation of Authorization Table is in the CLASSPATH and could be loaded. security.web.ta.classloaderr=SECJ0123E: Trust Association Init Error retrieving class loader. Trust Association cannot be enabled. getClassLoader() operation returned null. Verify that the appropriate Trust Association classes are installed and the class path is correct. security.scanner.risk.adminid.improve=SECJ7521W: Multiple Administrative user IDs are not configured. When WebSphere Application Server security is enabled, a single security ID the Administrator role is initially configured as the Security Server ID. Configuring multiple administrative user ids as Administrator can protect this server ID and enable more effective audit logging Multiple Administrative user IDs are not configured. When WebSphere Application Server security is enabled, a single security ID the Administrator role is initially configured as the Security Server ID. Configuring multiple administrative user ids as Administrator can protect this server ID and enable more effective audit logging None security.j2c.mappingUnsuccessful=SECJ4062W: Cannot find the credential information. WebSphere default principal/credential mapping function could not find the specified credential information. This is most likely caused by incorrect authentication data configuration. security.secsrv.bind.registry=SECJ0283E: Error binding User Registry. The exception is {0}. javax.naming.NamingException occurred while rebinding the user registry. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.keyManager=SECJ7146I: Key managers None None security.audit.service.no.webattrs.audit=SECJ6102I: Access to a web resource is allowed because no access control is required. Access to a web resource does not require access control because there is no servlet mapping. The URI is not protected. No action is required is this is the desired configuration. Otherwise, proper security constraint should be added to the web application. security.NullLTPAConfig=SECJ0041E: Can't set Authentication Mechanism to LTPA when LTPAConfig is null This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.scanner.risk.admin.security.improve=SECJ7525W: Administrative Security is disabled. Only users with specific rights can use the WebSphere Application Server administrative tools to perform any administrative operation. Note that other important security features listed might be reported as enabled, but they will not take effect until administrative security is activated. The settings include the authentication of users, the use of Secure Sockets Layer (SSL), and the choice of user account repository. In particular, application security, including authentication and role-based authorization, is not enforced unless administrative security is active. Administrative Security is disabled. Note that other important security features listed might be reported as enabled, but they will not take effect until administrative security is activated. The settings include the authentication of users, the use of Secure Sockets Layer (SSL), and the choice of user account repository. In particular, application security, including authentication and role-based authorization, is not enforced unless administrative security is active. None security.configrpt.core.establishTrustInClient=SECJ7055I: Establish trust in client None None security.configrpt.core.keyFilePassword=SECJ7073I: Key file password None None security.configrpt.core.libraryFile=SECJ7079I: Library file None None security.admintask.EmitterExists=SECJ7390E: An audit service provider implementation with this unique name is already configured. Cannot configure an audit service provider implementation with the same unique name as one that is already configured. Specify a unique name for the new audit service provider implementation security.configrpt.core.requiredQOP=SECJ7056I: Required Quality of protection (QoP) settings None None security.configrpt.core.singleSignon=SECJ7024I: Single signon (SSO) None None security.configrpt.core.serverId=SECJ7029I: Server user ID None None security.init.ltpawithoutsso=SECJ0367W: Warning, LTPA is configured as the authentication mechanism but SSO is disabled. Web applications that use FormBased Login, including the WebSphere web based admin console, might not work correctly. SSO is required for FormBased logon to work in Web applications when LTPA is the authentication mechanism. If this is the intended configuration then ignore this warning. If this is not the intended configuration, then the enabled attribute of Single Sign-on element in the security.xml must be set to the true value. security.jaas.LoginModuleCommitError=SECJ4015E: An unexpected exception occurred during the JAAS login commit action in Login Module {0}. The exception is {1}. Exception occurred while committing LoginModule Check the application. Contact your service representative with exception stack trace information present in the error log if the problem persists. security.init.namingapp=SECJ0203I: Naming application initialized successfully The Naming application initialized successfully None. Informational only. security.configrpt.core.enforceJava2Security=SECJ7010I: Java 2 security None None security.configrpt.core.krb5Realm=SECJ7238I: Kerberos realm name None None security.configrpt.core.location=SECJ7166I: Path None None security.configrpt.core.simpleAuthConfig=SECJ7019I: Simple authentication config None None security.jaas.create.credential=SECJ4049E: Error creating credential from registry object. The exception is {0}. Unexpected exception occurred while creating and initializing the user registry. Check the application and the registry set up. Contact your service representative if the problem persist. security.configrpt.core.sslProtocol=SECJ7162I: SSL Protocol None None security.swam.find.registry=SECJ0258E: Cannot find user registry. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.basic.error.audit=SECJ6125I: Basic authentication failed due to incorrect user id and/or password Will send a 401 challenge. The authentication failed because there the user id and password information in the HTTP header was incorrect. WebSphere Application Server will send a 401 challenge to the web client. No action is required. security.configrpt.core.enabledGssCredDelegate=SECJ7249I: Enable delegation of Kerberos credentials None None security.zos.saf.delegation.service.error=SECJ6217E: Unable to create a SAF delegation credential for the SAF profile named "{0}" in application "{1}". The native service results information are: {2}. The security service was unable to create a delegation credential. This failure is usually due to incorrect or missing APPLDATA associated with the EJBROLE profile associated with the application role. Verify that the EJBROLE profile exists and is defined correctly. If the profile is correct, use the information about the SAF service, and SAF service return codes to determine the cause of the failure. If the problem persists, contact the IBM support center. security.configrpt.core.policyConfigurationFactoryImplClassName=SECJ7037I: Policy configuration factory class name None None security.getting.namingctx.error=SECJ0251E: Error getting Initial Naming Context. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.scanner.risk.samples.ok=SECJ7539I: WebSphere Application Server Sample Applications are not installed. WebSphere Application Server ships with examples to demonstrate various parts of WebSphere Application Server. These samples might be installed by default and are not intended for use in a production environment. Some of these samples can provide an intruder with information about your system. WebSphere Application Server Sample Applications are not installed. WebSphere Application Server ships with examples to demonstrate various parts of WebSphere Application Server. These samples might be installed by default and are not intended for use in a production environment. Some of these samples can provide an intruder with information about your system. None security.jacc.secpolicy.removed=SECJ0416I: The security policy for application {0} is successfully removed from the JACC provider. This message is provided for information purposes only. No user action is required. security.saml.at.global.security.SECJ8057W=SECJ8057W: SAML TAI should be configured at the security domain level instead of global security. There is a security domain, but SAML TAI is configured at the global level. Configure the SAML TAI at the domain level. security.jacc.tools.object.null=SECJ0404E: The {0} object is null. Could not get the object required for security policy propagation. Make sure that the JACC provider properties are set correctly in the JACC configuration. Also make sure that all the provider classes are in the class path of all the servers. security.configrpt.core.roleConfigurationFactoryImplClassName=SECJ7039I: Role configuration factory class name None None security.jaas.removePrinException=SECJ4016E: An unexpected exception occurred in Login Module {0} when removing principal {1} during cleanup. The exception is {2} Exception occurred while removing the principal. Contact your service representative with exception stack trace information present in the error log. security.zos.saf.authen.kerb.map.failed.warning=SECJ6227W: Authentication failed for kerberos principal {0}. The native service results related to the authentication failure are: {1}. WebSphere was unable to map the kerberos prinicpal that was presented to a valid RACF user. Verify that the kerberos principal is set to the KERBNAME value in the KERB segment of a valid RACF user. security.registry.groupsecurityname.error=SECJ0346E: Could not get the name of the group whose uniqueId is {0} because of the following exception {1}. Internal Error. Make sure that the group is valid. Contact your service representative if the problem persists. security.init.wccmjaas.error=SECJ0209E: An unexpected exception occurred when attempting to update the JAAS login configuration with WCCM JAAS configuration information. The exception is {0} The WCCM JAAS login configuration information could not be pushed to the JAAS configuration object. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.Value=SECJ7001I: Value None None security.admintask.doesNotMatchGlobalValues.SECJ7817I=SECJ7817I: The parameter values entered do not match the values at the global security configuration (security.xml) for this registry. These values have been ignored and replaced with the values {0}, {1}, {2} from the global security configuration (security.xml) for this registry. Since the registry configuration should be consistent across all security configurations the values from the global security configuration are copied to the configuration. No action is required. security.admintask.doesNotMatchGlobalValues.SECJ7816I=SECJ7816I: The parameter values entered do not match the values at the global security configuration (security.xml) for this registry. These values have been ignored and replaced with the values from the global security configuration (security.xml) for this registry. Since the registry configuration should be consistent across all security configurations the values from the global security configuration are copied to the configuration. No action is required. security.audit.unsupported.encode.error=SECJ6029E: Unsupported encoding exception raised. Exception = {0}. Encoding error. Examine the exception for the cause of the problem. security.admintask.IOErrorBinaryLog=SECJ7447E: Failure while reading the specified Binary Audit Log. Either a pathname that is not valid was specified or the file is corrupted. Could not open or read the Binary Audit Log. Check the pathname specified for the location of the Binary Audit Log. security.configrpt.core.Security=SECJ7088I: Security None None security.registry.mapcertificate.notsupported=SECJ0337E: The mapCertificate method is not supported. Internal Error. Information purposes only. security.audit.service.factory.error=SECJ6009E: AuditEventFactory number {0} getActive() malfunction, Provider Exception = {1}. The getActive method in the spcified AuditEventFactory implementation failed. Examine the exception for the cause of the problem. If the problem was not related to incorrect configuration, then you need to consult with the vendor of the AuditEventFactory implementation. security.configrpt.core.autoGenerate=SECJ7191I: Automatically generate keys None None security.scanner.risk.other.role.all.improve=SECJ7543W: Special subject "{0}" is configured for one of the administrative roles. It is not recommended to have AllAuthenticatedUsers specified for any of the administrative user roles. A special subject is configured for one of the administrative roles. It is not recommended to have AllAuthenticatedUsers specified for any of the administrative user roles. Remove the AllAuthenticatedUsers subject from any of the administrative user roles if applicable. security.configrpt.core.useClaim=SECJ7270I: Use claim None None security.admintask.doesNotMatchGlobalValues.SECJ7815E=SECJ7815E: The parameter values entered do not match the values at the global security configuration (security.xml) for this registry. Make sure the values match since this registry configuration should be consistent in all security configurations in the cell. The Federated Repository registry configuration should be consistent across all the security domains and should match the values at the global security configuration (security.xml). Make sure that the parameter values for this task match the values at the global security configuration for this registry. security.jacc.uninstall.task.warning=SECJ0397W: Error removing information from the JACC provider for application {0}. The exception is {1}. Cannot delete the security policy information from the JACC provider because of the exception. This problem creates redundant information in the JACC provider. Make sure that the JACC provider is properly configured and can be accessed. The JACC provider might have tools to remove this information. security.admintask.InvalidCustomProperty=SECJ7391E: The custom properties have been invalidly specified. Custom properties must be specified as name-value pairs, separated by a comma, semicolon or space. Enter a valid syntax for the custom properties security.admintask.spnego.errorDeleteAllFiters.SECJ7799E=SECJ7799E: Can not delete all SPNEGO filters because SPNEGO Web authentication is enabled. The SPNEGO Web authentication is enabled, it requires at least one SPNEGO filter. Disable SPNEGO Web authentication before delete all SPNEGO filters. security.jaas.invalidToken=SECJ4004E: Login failed for credential token {0} JAAS Login failure occurred while invoking login() with token. Check the user authenticate data is correct. Enabling security debug trace will provide the details.(com.ibm.ws.security.auth.* ) security.admintask.MissingModifyParms=SECJ7378E: No attributes specified on the modify command. No attributes were specified on the modify command. Supply attribute(s) to modify on the audit object security.admintask.InvalidReportMode=SECJ7449E: Non valid or empty value specified for the report mode. Valid values are basic, complete or custom. The default mode is basic. A non valid value was specified for the report mode. Specify a non-empty or valid value for the report mode. security.audit.cert.success.audit=SECJ6118I: Authentication failed becasue Trust the client certificate cannot be mapped to WebSphere Application Server user. The authentication based on the X509 client certificate failed because the certificate user name cannot be mapped to a valid WebSphere Application Server user. No action is required. security.ltpa.realm_mismatch=SECJ0375E: Mismatch of realms during token validation. The realm in the token does not match the current realm. This error can occur when a token is passed between one cell and another cell, and the realms do not match in these cells. If you are using LDAP, make sure that both cells use the same host name and port number. security.admintask.scopeMapped.SECJ7717E=SECJ7717E: One or more resources are still mapped to the security configuration. Not able to delete the security configuration at this time. At least one resource is still mapped to the security configuration. The security configuration cannot be removed until there are no scopes mapped to it. Ensure that there no now scopes mapped to the security configuration before deleting it. security.configrpt.core.moduleClassName=SECJ7046I: Module class name None None security.registry.nosecurityname=SECJ0069E: Problem getting Security Name for privilege id: {0}. The exception is {1}. Cannot find a name for the specified SID in the Windows user registry.This can occur if a network time-out prevents the function from finding the name. It also occurs for SIDs that have no corresponding account name, such as a logon SID that identifies a logon session WebSphere might still have a reference to the user in the authorization table but, that user might have been removed from the Windows user registry. If you know the user, remove it from any resource protection permissions in WebSphere. If the user is still valid, then it needs to be recreated in the Windows user registry and then reassigned to proper resource permissions in WebSphere. security.saml.sso.is.null.SECJ8048E=SECJ8048E: More than one SSO entry. You must specify the ssoId parameter. You must specify the ssoId because the SAML TAI attributes have more than one SSO entry. Specify a ssoId number that exists. security.audit.csi.failure.audit=SECJ6141I: Authentication failed due to internal error. Authentication failed due to internal error. No action required. security.configrpt.Naming.Read.Name=SECJ7116I: Read None None security.registry.isvaliduser.error=SECJ0358E: Validating the user {0} throws the following exception {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.missingParameter.krb5ConfigAndSecurity.SECJ7785E=SECJ7785E: The {0} is missing in the Kerberos configuration file {1} and the Kerberos authentication mechanism object. The entry is not found in the Kerberos configuration file and the Kerberos authentication object. Add the entry in the Kerberos configuration file or specify this entry. security.registryimpl.initerr=SECJ0156E: Unable to initialize user registry class {0} for type {1} due to exception: {2} The WebSphere security code couldn't find, load, or had problems loading the user registry class. The exception mentioned in the message should provide additional clues including the class or file that could not be found or loaded. Verify that the mentioned file exists in the correct directory and PATH. security.jaas.duplicateCORBAAttribute=SECJ4021E: CORBA: Duplicate Attribute Type: {0} {1} CORBA credential has duplicate attributes. Contact your service representative with exception stack trace information present in the error log. security.configrpt.core.bindPassword=SECJ7221I: Bind password None None security.jsecman.debugflagmsg=SECJ0313I: Java 2 Security Manager debug message flags are initialized: TrDebug: {0}, Access: {1}, Stack: {2}, Failure: {3}, Rethrow {4} This message provides the current value of the java.security.debug property which is used to enable various debug information related to Java 2 Security. None, this is informational only. security.rolebauthz.authzfail=SECJ0305I: The role-based authorization check failed for {0} operation {1}:{2}. The user {3} (unique ID: {4}) was not granted any of the following required roles: {5}. The caller does not have the necessary permission, this problem can occur because no credential is found on the thread, the caller is not authenticated, or the accessId might be null. If the failure is unexpected, verify that the caller has been granted the required role. security.audit.sso.expired.audit=SECJ6112I: SSO token {0} is expired and failed validation. Authentication failed because the SSO token has expired. No action is required. security.configrpt.seconds=SECJ7170I: seconds None None security.configrpt.core.clientKeyAlias=SECJ7175I: Default client certificate alias None None security.configrpt.core.provider=SECJ7167I: Provider None None security.configrpt.core.Authentication.Mechanisms=SECJ7014I: Authentication mechanisms and expiration None None security.secsrv.token.destroy=SECJ0278E: TokenData credential is already destroyed. The exception is {0}. CredentialDestroyedException occurred while trying to get credential token. The credential was already destroyed. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.registry.noclassname=SECJ0328E: Registry implementation file is missing. Cannot locate the registry implementation file. If you are using a Custom Registry make sure that your provide the registry implementation file in the GUI or in the scripting (whichever is being used). If you are using WebSphere Application Server supplied registries contact your service representative if the problem persists. security.init.secstatus=SECJ0210I: Security enabled {0} Reports current security enabled or disabled status. None. Informational only security.configrpt.core.User.Registry=SECJ7027I: User Registry None None security.configrpt.core.internalServerId=SECJ7154I: Internal server ID None None security.native.error=SECJ0164E: Error number {0} while calling the operating system API {1} An error was returned by the operating system API Depending on the API being called, check the operating system specific documentation security.web.cache.initerror=SECJ0083E: Error initializing web cache on admin server This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.sas.orbssl.config.error=SECJ0247I: ORB SSL Key File or Passwords settings were missing in server-cfg.xml ORB SSL Key File or Passwords settings were missing in server-cfg.xml Verify that the server-cfg.xml file. security.zos.saf.authz.failed=SECJ6236E: Authorization failed; the exception is {0}. Authorization failed for the user. The exception has information on why the authorization failed. Examine the message in the exception for more information. security.audit.csi.message.failure.audit=SECJ6146I: Message type was not supported. Message type is not EstablishContext and stateful=false. No action is required. security.configrpt.core.nextStartDate=SECJ7205I: Next start date None None security.registry.TAM.initialize=SECJ0386I: Initializing registry to use Tivoli Access Manager for authentication. Authenticaton will be perfomed using Tivoli Access Manager. This requires that WebSphere is configured to use an external Tivoli Access Manager server. None, informational only. security.rolebauthz.iscallerinrolefail=SECJ0321E: Role based authorization is caller in role failed for security name {0}, accessId {1}, and role name {2}. The caller does not have the necessary permission, there was no credential on the thread, the caller is not authenticated, or the accessId could be null. If the failure is unexpected, verify the caller has been granted the required role. security.ltpa.noalgorithm=SECJ0368E: No such LTPA Algorithm. The exception is {0}. This is an internal error. A NoSuchAlgorithmException occurred when the LTPAServer tried to sign the token. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.scanner.risk.ldaplink.ok.used=SECJ7536I: User Registry is LDAP. SSL between WebSphere Application Server and LDAP is enabled. This ensures that the communication between WebSphere Application Server and LDAP is encrypted User Registry is LDAP. SSL between WebSphere Application Server and LDAP is enabled. This ensures that the communication between WebSphere Application Server and LDAP is encrypted None security.zos.saf.idprop.distributedRealm.tooLong=SECJ6231E: The distributed realm name exceeds the maximum length of {1}. The distributed realm name is {0}. The distributed user will not be mapped to a SAF user. The distributed realm name exceeds the maximum allowable length. Specify a valid distributed realm name. security.audit.service.init.error=SECJ6036E: AuditService not initialized. Audit service was not initialized, which occurred most likely due to incorrect class definition, incorrect class path, or missing class files. Examine the exception for the cause of the problem. security.authn.cache.maxsize.reached=SECJ0430W: The authentication cache currently has {0} entries which has exceeded the maximum size of {1}. The cache cleanup algorithm will remove some entries. Consider increasing the maximum cache size. When the authentication cache maximum size is reached, some entries from the cache are evicted. This will cause some users to go back through the login modules which is a slower process. To increase the max cache size for the authentication cache, set the following System property (com.ibm.websphere.security.util.authCacheMaxSize) for each process that needs it. The property default is 25000 entries. security.configrpt.secure.communications.fips=SECJ7226I: Use the United States Federal Information Processing Standard (FIPS) algorithms None None security.admintask.FilePathException=SECJ7397E: Exception validating existance of audit log filepath. An exception occurred validating or creating the file path location for the audit logs. None security.sas.prop.updated=SECJ0046I: SAS Property:{0} has been updated Informational. A security configuration change has caused a SAS Property to be updated. security.admintask.missingParameter.krb5Auth.SECJ7771E=SECJ7771E: The {0} is missing in the Kerberos authentication mechanism object. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Operator.Role.User=SECJ7100I: Operator User None None security.policy.fileToURL=SECJ0183W: An exception was caught while trying to convert the filepath {1} to URL. The exception is {0}. Could not convert the specified filepath to URL. Check the specified filepath. It could be caused by incorrect data in xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.admintask.FailedCheckPassword=SECJ7342E: Failed to validate user/password Failed to validate user password in federated respositories None security.admintask.CertNotInKeyStore=SECJ7428E: Could not find certificate alias in the referenced keystore. Certificate alias does not exist in the referenced keystore. Make sure to specify a certificate alias that does exist in the referenced keystore. security.zos.saf.delegation.using.caller.warning=SECJ6218W: The SAF delegation implementation was unable to create a subject in the role named "{0}" in application "{1}" for role delegation. The current subject will be used. An earlier error prevented WebSphere from creating a subject that was in the required role. The target method will be dispatched without a change the current security environment. This might result in authorization errors as the caller might not be in the required role. Examine the previous messages to determine the initial cause of th error. security.jaspi.configuration.factory.invalid.SECJ8028E=SECJ8028E: AuthConfigFactory is null, JASPI bindings cannot be registered. JASPI bindings cannot be registered because a JASPI factory implementation is not defined. Verify the fully qualified class name of the default JASPI factory implementation class is defined using the property authconfigprovider.factory in java.security. security.secsrv.basic.expired=SECJ0277E: BasicAuthData credential is already expired. The exception is {0}. javax.security.auth.login.CredentialExpiredException occurred while trying to get BasicAuthData. refresh the credential. security.configrpt.core.allowBasicAuth=SECJ7234I: Allow basic authentication None None security.jacc.tools.pcf=SECJ0387E: Error getting the PolicyConfiguration object for the contextID {0}. The exception is {1}. Could not get the JACC provider PolicyConfiguration object. This object is required to propagate the security constraints information to the provider. Make sure that the JACC provider property javax.security.jacc.PolicyConfigurationFactory.provider is set correctly to the PolicyConfigurationFactory implementation class. The preferred way to set this property is to use the JACC configuration properties panel or wsadmin tool. Also make sure that the provider classes are in the class path of all the servers. security.configrpt.core.usage=SECJ7256I: Usage None None security.native.audit=SECJ0201I: Error number {0} while calling the operating system API {1} The above error number was returned by the above API. Depending on the API being called, check the operating system documentation for the API. security.configrpt.days=SECJ7214I: days None None security.configrpt.core.setting=SECJ7068I: SSL settings None None security.iscallerinrole.error=SECJ0390E: Error when caling isCallerInRole for role {0}. The exception is {1}. Cannot determine the isCallerInRole because of the exception. Default is to return false. Make sure that the security role-ref information is correct. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.Application.Login.Config=SECJ7041I: Application login configuration None None security.configrpt.core.securityLevel=SECJ7074I: Security level None None security.jacc.tools.uninstall=SECJ0408E: An exception occurred when removing the security policy information from the provider for application {0} during uninstall. The exception is {1}. Because of an exception, the security policy information might not have been removed completely from the provider during the application uninstallation. Make sure that the provider is up and running and the JACC configuration is correct. One can use the tools provided by the provider to remove the security policy information manully from the provider's repository. security.configrpt.Naming.Write.Name=SECJ7123I: Write None None security.admintask.CheckKeyStore=SECJ7400E: Key store file did not verify, make sure the file exists, check key store type and password. When creating a key store object with an existing key store file the file must exist and a valid password and key store type must be supplied. Make sure the key store file exists with a valid password and key store type. Then rerun the command. security.registry.groupdisplayname.error=SECJ0338E: The following error occurs when getting the display name of the group {0}, {1}. Error getting display name of a group. Make sure that the group is valid and has a display name. security.audit.authz.disabled.audit=SECJ6129I: Access is allowed because security is disabled. Access to the resource is allowed because WebSphere Application Server global security eas not enabled. No action required if this is the configured behavior. security.configrpt.core.initializeJACCProviderClassName=SECJ7034I: Provider initialization class name None None security.admintask.EncryptionNotEnabled=SECJ7425E: Cannot specify keystore for encryption: encryption not enabled. When encryption is not enabled, cannot configure the encryption keystore. Enable encryption before setting the encryption keystore. security.admintask.InvalidTimeStampRange=SECJ7456E: Non valid timestamp range specified. Either a single timestamp can be specified or a group of timestamp records may be specified as begin:end. A non valid value was specified for the timestamp set of audit records to report Specify a non-empty or valid value for the timestap set. security.ltpa.authenticate=SECJ0369E: Authentication failed when using LTPA. The exception is {0}. Authentication has failed when using LTPA. There could be multiple reasons why this might have occurred. Most of the time this should have preceeded with other exceptions that will indicate what the exact problem is. This might occur if the userName, password or both are incorrect, if the setup of the registry is not valid. If problems persist contact your service representative. security.configrpt.core.hostName=SECJ7252I: Host name None None security.configrpt.core.tokenType=SECJ7080I: Token Type None None security.admintask.unknown.hostname.SECJ7819E=SECJ7819E: Unknown host name {0} The host name is unknown. Ensure that a valid host name is specified. security.zos.threadid.connmgmt.enabled=SECJ6211I: Connection management thread identity synchronization is enabled. The server has been configured to perform J2EE and operating system thread identity synchronization for connectors that are able to exploit it. No user action is required. security.admintask.NoCertKeyFilePasswordValue=SECJ7408E: No value was specified for the key file password for the certificate to import When selecting to import an existing certificate, a key file password for the certificate must be entered. Supply a key file password for the certificate to import security.sap.warning.deserializing.custom.objects.from.subject=SECJ5003W: An error occurred while de-serializing a custom object from the inbound authorization token. This does not cause the request to fail but this custom object will not get restored in the inbound Subject. The object failed to de-serialize at the target server. The likely cause is the implementation class is not present on the target server or the Java class version between the sending server and target server is different. Ensure that the correct java class exists at the target server. security.configrpt.core.webAuth=SECJ7140I: Web security None None security.configrpt.core.scopeName=SECJ7189I: Scope Name None None security.merge.cell.signer.not.exchanged=SECJ0423I: During addNode from node "{0}" the default cell certificate did not exchange its signer with the node default truststore. This might cause a handshake failure when the node agent starts up. Manual signer exchange might need to occur. It's likely the TrustStore named NodeDefaultTrustStore or KeyStore named CellDefaultKeyStore does not exist in the configuration. The cell's signer certificates need to be added to the node's truststores. security.configrpt.core.defaultSSLSettings=SECJ7007I: Default SSL settings None None security.scanner.risk.drs.ok.used=SECJ7531I: Encryption is enabled on Distributed Replication Service(DRS). This ensures that the data shared among WebSphere Application servers is encrypted. Encryption is enabled on Distributed Replication Service(DRS). This ensures that the data shared among WebSphere Application servers is encrypted. None security.admintask.loginModuleDoesNotExist.SECJ7708E=SECJ7708E: The {0} does not exist. The login module specified does not exist. Ensure that the login module exists. security.sap.error.creating.token.holder.list=SECJ5001E: The following exception occurred while creating the attribute propagation token holder list from the authorization token: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.init.svcstartfail=SECJ0244I: Security service failed to start successfully Security service started. None. Informational only security.admintask.NotificationMonitorConfigured=SECJ7374E: Audit Notification Monitor already configured. Audit Notification Monitor has already been configured. None security.sas.orbssl.setting.exception=SECJ0246E: Caught unexpected exception in retrieving ORB SSL settings {0} An unexpected exception occurred retrieving the ORB SSL settings. Verify that the property file, usually sas.server.props contents. Contact your service representative if the problem persists. security.web.adminwebcache.initerror=SECJ0085E: Error initializing admin web cache This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.authz.failed.foruser=SECJ0053E: Authorization failed for {0} while invoking ({1}){2} {3} {4} The user does not have the necessary permission to access the resource. This failure might be expected if the user should not be granted access. If this error is unexpected, then there are several possible causes. The user has not been mapped to one the roles protecting the resource if the user requires access to the protected resource. The user is not a member of one of the groups that might have been mapped to one of the roles. If WebSphere security is configured to use LDAP as the user registry, the WebSphere security LDAP user and group search filter configuration might not match what the LDAP directory expects. If the authorization failure is unexpected, verify the user, or a group that the user is a member of, is mapped to the role protecting the resource. Verify that the WebSphere security LDAP user and group filters configuration match what the LDAP directory expects. security.configrpt.core.filterClass=SECJ7250I: SPNEGO Filter class None None security.configrpt.Admin.Role.Group=SECJ7108I: Administrator Group None None security.saml.element.id.notexistent.SECJ8041E=SECJ8041E: {0} {1} is not defined in the SAML TAI configuration. The given parameter value is not defined in the SAML TAI configuration. Verify the SAML TAI properties and specify a value that exists. security.configrpt.core.dynamicallyUpdateSSLConfig=SECJ7172I: Dynamically update run time when SSL configuration changes occur None None security.configrpt.core.SecureEndpoint=SECJ7139I: Manage endpoint security configurations None None security.webatts.exception=SECJ0224E: An unexpected exception occurred when trying to configure the security related web attributes for web applications {0}. The exception is {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.scanner.risk.other.role.every.improve=SECJ7542W: Special subject "{0}" is configured for one of the administrative roles. It is not recommended to have Everyone specified for any of the administrative user roles. A special subject is configured for one of the administrative roles. It is not recommended to have Everyone specified for any of the administrative user roles. Remove the Everyone subject from any of the administrative user roles if applicable. security.registry.createerror=SECJ0074E: Error creation user registry. The exception is {0} An unexpected exception occurred when trying to load or create the user registry. Verify that the CLASSPATH used to start WebSphere is correct and that the jar files have at least the read permission and exist. security.adminapp.cmd.error.SECJ8023E=SECJ8023E: An unexpected exception occurred processing Jaspi bindings during application deployment. Failed command: {0}, exception: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.ConfigurationError=SECJ7357E: Configuration error detected in the audit configuration Error detected in the audit configuration Verify that the audit configuration is correctly specified in the audit.xml security.jacc.initialized=SECJ0413I: The JACC provider is successfully initialized with the following setup. The policy class name is {0}. The PolicyConfigurationFactory class name is {1}. The optional RoleConfigurationFactory call name is {2}. The optional initialization class name is {3}. This message is provided for information purposes only. No user action is required. security.admintask.Kerb.cannotUseInternalServerId=SECJ7742E: InternalServerId cannot be used with Kerberos authentication mechanism. Modify the dmgr security configuration to use the serverID/passwd before configure Kerberos authentication mechanism. Modify the dmgr security configuration to use the serverID/password with Kerberos authentication mechanism. The Kerberos authentication cannot be configured with InternalServerId. security.configrpt.core.trustedPassword=SECJ7157I: Password None None security.configrpt.core.displayNameKey=SECJ7180I: Key file name None None security.zOS.SecurityManager.PermissionFailure1.warning=SECJ6205W: The current Java 2 Security policy reported a potential violation of a Java 2 Security Permission. Refer to the InfoCenter for further information.{0}Permission:{1}Code:{2}Code Base Location:{3} The Java Security Manager checkPermission() threw a SecurityException on the subject Permission. A caller on the call stack does not have the required permission. This might not be a problem if the caller properly handles this exception. Verify that the attempted operation is permitted by examining all Java 2 security policy files and application code. Additional permissions might be required, an AccessController.doPrivileged call might be needed in some code on the call stack, or the Security Manager has properly prevented access to a resource that a caller does not have permission to access. security.policy.parser.methodisnull=SECJ0229E: Method {0} of object of {1} type is null. Method returned by reflection is null. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.init.startfail=SECJ0241I: Security service initialization completed successfully Security service initialization started. None. Informational only security.admintask.globalfedoption.noglobalfed.SECJ7827E=SECJ7827E: Cannot configure an application security domain to use the global federated repository option when the global security domain does not have a federated repository as the active user registry. The global security domain must be configured with a federated repository as the active user registry in order for any application security domain to be configured with the global federated repository option. Either the global security domain should be configured with a federated repository as the active user registry or the application security domain should elect not to use the global federated repository option. security.configrpt.core.Servers=SECJ7278I: Servers None None security.jaas.create.URL=SECJ4038E: {0} :ERROR: Could not create URL: {1}. The exception is {2} IOException occurred trying to connect the specified URL. Investigate the exception. Check the specified URL. security.admintask.jaspi.classname.invalid.SECJ8008E=SECJ8008E: The {0} class name is not valid: {1}. Specify a valid class name. The class name of an authentication provider or module must not be empty. Specify a non-empty class name for the authentication provider or module. security.admintask.authFailed.SECJ7778I=SECJ7778I: Password check for {0} in {1} failed. A test to check the users password on a particular realm was failed. none. security.policy.parser.objectisnull=SECJ0228E: Object of type {0} is null. Object created by reflection is null. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.sso.invalid.audit=SECJ6113I: SSO token {0} is invalid and failed validation. Authentication failed because the SSO token was not valid. No action is required. security.roleref.configerror=SECJ0155E: Deployment descriptor configuration error. security-role-ref {0} in ejb-jar.xml is not mapped to any security role in bean {1}, module {2}, application {3}. A security role reference in the specified EJB's ejb-jar.xml file has not been mapped to a security role. This is a configuration error. The security-role-ref in the EJB's ejb-jar.xml deployment descriptor should be mapped to a security role. security.sap.warning.realm.does.not.match.current.realm=SECJ5008W: The realm specified in com.ibm.wsspi.security.cred.realm ({0}) does not match the current realm ({1}). This could cause problems when trying to make a downstream request. The realm specified does not match the current security realm of this server. This could cause problems when trying to go downstream to another server on the same current realm. If a different realm is desired, set the supportedTargetRealms field to include the new realm you are specifying in order to go outbound to servers in the current realm. security.saml.idp.missing.element.SECJ8045W=SECJ8045W: {0} is missing from IdP metadata file {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.csi.session.success.audit=SECJ6138I: Security context setup successfully. The client security context was re-established successfully using the client session context identifier. The message type ASSOC_ACCEPT should not be received at the target server. No action is required. security.jacc.provider.inservice=SECJ0388E: Problem getting the PolicyConfiguration inService status. The exception is {1}. The policy configuration object status could not be determined. Access will not be granted to this module. The module in question might be in the process of being deleted. If the problem persists, contact your service representative. security.configrpt.core.Security.jaasAuth=SECJ7092I: Java Authentication and Authorization Service None None security.audit.keystore.not.found.error=SECJ6038E: Audit keystore not found. Cannot find keystore created by the Auditor. Ensure that the keystore has been created containing the certificate generated by the Auditor. security.saml.can.not.delete.certificate.SECJ8051W=SECJ8051W: You cannot remove the certificate from the trust store because more than one IdP or SP reference this certificate in the SAML TAI. The certificate is used by other IdP or SP. Verify the certificate is not used by any other IdP or SP. security.configrpt.core.trimUserName=SECJ7241I: Trim Kerberos realm from principal name None None security.registry.uniqueusrid.notfound=SECJ0350E: Could not get the uniqueId of the user {0}. Internal Error. Make sure that the user is valid. Contact your service representative if the problem persists. security.configrpt.Deployer.Role.User=SECJ7227I: Deployer User None None security.admintask.MustSpecifyCertGenMethod=SECJ7403E: Must specify only one option for either autogenerating or importing a certificate. The values for auto-generating a certificate and importing a certificate matched. Must specify true for one or the other. Specify either auto-generating a certificate or importing a certificate. security.swam.unsupport.callback=SECJ0260E: Unsupported {0} callback in CallbackHandler. The exception is {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.policy.was.ioexception=SECJ0190E: Caught IOException while creating template for was.policy {0}. The exception is {1}. IOException occurred when putting the was.policy template in the hashmap of all the templates. Check the specified was.policy file. security.configrpt.core.entries=SECJ7042I: Entries None None security.init.secidautherror=SECJ0208E: An unexpected exception occurred when attempting to authenticate the server''s id during security initialization. The exception is {0}. The userId and password specified for the server's identity when configuring global security could not be used to authenticate the server. Verify that the userId and password are valid and meet the requirements for the user registry or authentication mechanism. security.secsrv.token.expired=SECJ0279E: TokenData credential is already expired. The exception is {0}. javax.security.auth.login.CredentialExpiredException occurred while trying to get token. refresh the credential. security.admintask.jaspi.version.warning.SECJ8026W=SECJ8026W: JASPI authentication can only be enabled on version 8 and higher nodes. JASPI authentication only functions on version 8 and higher nodes. Only use JASPI authentication on version 8 and higher nodes. security.audit.service.logout.default.audit=SECJ6021I: AuditEventType = {0}, AuditOutcome = {1}, AuditOutcomeReason = {2}, unique Event ID = {3}, Cell Name = {4}, Node Name = {5}, Server Name = {6}, Component Name = {7}, App Name = {8}, Session ID = {9}, Realm = {10}, User Name = {11}, Provider Name = {12}, Provider Successful = {13}, Subject = {14}, Caller List = {15}, Remote Addr = {16}, Remote Host = {17}, Remote Port = {18}, Exception = {19}. This message is intended to be used by the defaultAuditEventFactoryImpl sendLogoutAuditEvent method only. No action required. security.audit.decryption.data.error=SECJ6046E: Data that is not valid was passed into the decryption algorithm. A data stream that is not valid was passed into the decryption algorithm. Verify that a non-null byte stream of data is being passed in. security.admintask.MissingEmailList=SECJ7384E: Must enter an email list when send email is true. Must enter an email list when send email is true. Supply an email list security.web.authz.failed.foruser=SECJ0129E: Authorization failed for user {0} while invoking {1} on {2}, {3} The user does not have the necessary permission to access the resource. Contact your WebSphere security administrator if this is unexpected. Your user must be mapped to one the roles protecting the resource if access to the protected resource is required. security.configrpt.core.spnegoNotSupportedPage=SECJ7254I: SPNEGO not supported page URL None None security.configrpt.core.trustFilePassword=SECJ7077I: Trust file password None None security.admintask.RSATrustStore.SECJ7748E=SECJ7748E: {0} is not a RSA token trust store. A RSA trust store must be used on a RSA authorization mechanism. Run the command specifying a RSA trust store. security.ltpa.validate.createcredential.failed=SECJ0373E: Cannot create credential for the user {0} due to failed validation of the LTPA token. The exception is {1}. This is an internal Error. Cannot create a credential after the token is validated. This error usually occurs due to an expired token or a token created with different LTPA keys.If the token is expired, you might need to increase the LTPA timeout. If the keys are not the same, make sure that one set of LTPA keys are used. security.saml.parameter.is.null.SECJ8047E=SECJ8047E: {0} is null. Specify the given parameter. Specify a valid parameter value. security.configrpt.core.AdminSecurity=SECJ7086I: Global security None None security.configrpt.core.adminCertificateTrustStore=SECJ7243I: Trusted signers keystore None None security.saml.idp.entity.id.notexistent.SECJ8061W=SECJ8061W: There is no entityID in the IdP metadata file {0}. The entityID is missing from the IdP metadata file. Verify the IdP metadata file. security.admintask.DataPointsContainsSpecial=SECJ7454E: The specified data points for the custom report contain one or more of the following: event type, sequence number or outcome type. These cannot be specified as values for this parameter. They will always be provided by default. Event type, sequence number, and outcome may not be specified under the -dataPoints parameter. All three of these pieces of data will always be reported. Do not specify event type, sequence number and outcome as values for the -dataPoints parameter. security.init.svcstartcomplete=SECJ0243I: Security service started successfully Security service started. None. Informational only security.admintask.ImportCertFailure=SECJ7418E: Failure importing the self signed certificate for audit encryption Failed to import the self signed certificate for audit encryption None security.audit.authz.denied.verbose.audit=SECJ6132I: Access is denied, Reason: {0}. Access to the resource is denied because the user or the groups the user is in does not have any of the required security role. No action required if this is the desired behavior. security.configrpt.Naming.AllAuthenticated=SECJ7119I: All Authenticated Users and Groups None None security.registry.usertype.notsupp=SECJ0079E: User type not supported in the user registry This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.jaspi.module.exists.SECJ8021E=SECJ8021E: Security domain {0} is not defined. The existing domains include: {1}. A security domain with the specified name does not exist. Specify the name of an existing security domain. security.audit.service.authz.default.audit=SECJ6018I: AuditEventType = {0}, AuditOutcome = {1}, AuditOutcomeReason = {2}, unique Event ID = {3}, Cell Name = {4}, Node Name = {5}, Server Name = {6}, Component Name = {7}, App Name = {8}, Session ID = {9}, Resource Name = {10}, Resource Type = {11}, Method Name = {12}, Provider Name = {13}, Provider Successful = {14}, Subject = {15}, Exception = {16}. This message is intended to be used by the defaultAuditEventFactoryImpl sendAuthzAuditEvent method only. No action required. security.secsrv.get.RoleBasedAuthorizer=SECJ0285E: Failed to retrieve RoleBasedAuthorizer. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.Naming.UserId=SECJ7120I: Specific User Ids None None security.scanner.risk.java2.improve=SECJ7535W: Java 2 security is disabled. Java 2 security provides a policy-based, fine-grain access control mechanism that increases overall system integrity by checking for permissions before allowing access to certain protected system resources. Java 2 security guards access to system resources such as file I/O, sockets, and properties. Java 2 security is disabled. Java 2 security provides a policy-based, fine-grain access control mechanism that increases overall system integrity by checking for permissions before allowing access to certain protected system resources. Java 2 security guards access to system resources such as file I/O, sockets, and properties. Enable Java 2 security if applicable. security.scanner.risk.corba.improve.everyone=SECJ7530W: The CORBA Namespace can be modified by Everyone. Anyone can alter the JNDI namespace. The default naming security policy is to grant all users read access to the CosNaming space and to grant any authenticated user the privilege to modify the contents of the CosNaming space. You can restrict user access to the CosNaming space. The CORBA Namespace can be modified by Everyone. Anyone can alter the JNDI namespace. The default naming security policy is to grant all users read access to the CosNaming space and to grant any authenticated user the privilege to modify the contents of the CosNaming space. You can restrict user access to the CosNaming space. Restrict user access to the CosNaming space if applicable. security.configrpt.core.performs=SECJ7062I: performs None None security.audit.service.unsupported.auth.mechanism.audit=SECJ6107I: The request is denied because the {0} login method was not supported. WebSphee Application Server does not support the configured login method. Modify the deployment descriptor to choose a supported login method. You might explore the Trust Association Interface and the UserRegistry interface and plug in your custom implementation to support the DIGEST login method. security.configrpt.core.properties=SECJ7081I: Custom properties None None security.init.startcomplete=SECJ0240I: Security service initialization completed successfully Security service initialization started. None. Informational only security.configrpt.core.bindDN=SECJ7220I: Bind distinguished name None None security.configrpt.core.emailList=SECJ7206I: List of e-mail addresses None None security.saml.no.sp.SECJ8056E=SECJ8056E: No service provider (SP) custom properties found for {0}. There are no SP custom properties found for the given SSO in the SAML TAI. Configure the SP custom properties for the given SAML TAI SSO before you export it. security.configrpt.core.description=SECJ7255I: Description None None security.configrpt.core.security.enablePluggableAuthentication=SECJ7084I: Enable pluggable authentication None None security.admintask.noUserReg.SECJ7763E=SECJ7763E: A filter must be specified when certificateMapMode is set to CERTIFICATE_FILTER. When the certificateMapMode is set to CERTIFICATE_FILTER a filter must be provided. Ensure a filter is provided when certificateMapMode is set to CERTIFICATE_FILTER. security.configrpt.core.direction=SECJ7188I: Direction None None security.admintask.InvalidMaxSizeValue=SECJ7396E: Non valid value for maximum size of each audit log was specified. The maximum size of and audit log needs to a value greater than 0. Supply a valid value for maximum number of audit logs security.authn.error.foruser=SECJ0118E: Authentication error during authentication for user {0} An authentication error occurred during authentication. This could be due to a user name and password that is not valid. Verify that the user name and password specified are valid. security.configrpt.core.sslConfig=SECJ7061I: SSL configurations None None security.configrpt.core.authorizationProviders=SECJ7033I: Authorization providers None None security.admintask.noUserReg.SECJ7762E=SECJ7762E: Unable to find the registry object. The registry object matching the domain, resource, or realm provide does not exist. Run the command with a domain, resource, or realm that has a user registry associated with it. security.configrpt.core.adminPreferredAuthMech=SECJ7233I: Primary Authentication Method for Administrative Actions None None security.configrpt.core.frequency=SECJ7203I: Frequency None None security.configrpt.core.CSI=SECJ7049I: CSI None None security.audit.logger.init.error=SECJ6034E: Exception raised trying to create the Audit log. Exception = {0}. Failed to create the output Audit log. Examine the exception for the cause of the problem. security.saml.sso.with.no.sp.SECJ8049E=SECJ8049E: You must configure a service provider (SP) for {0} before adding an IdP partner. The SSO entry has no SP information. Configure a service provider for this SSO before adding an IdP partner. security.secsvr.nameerror=SECJ0211E: Failed to lookup or rebind security server with name {0}. The exception is {1}. An unexpected error occurred. It could be that the Cell Manager or Node Agent are not started. If a remote security server was specified when enabling global security, verify that the Node Agent and Cell Manager are running. security.admintask.noAuthMechanismObj.SECJ7722E=SECJ7722E: The authentication mechanism is not configured. Unable to find the authentication mechanism in the user registry. Ensure a authentication mechanism is configured. security.zos.saf.threadid.sync.not.allowed.info=SECJ6222I: Thread identity synchronization of user "{0}" was not authorized by the z/OS security product. The z/OS security product did not authorize the creation of a security environment for the specified user. The security environment associated with the current address space will be used. Contact your security product administrator to authorize the creation of a security environment for the specified user if required by your application. security.audit.tai.challenge.invalid.audit=SECJ6114I: Trust Accosication Interceptor challenges the web client for authentication information. Status code = {0}. A Trust Association Interceptor engages in the authentication protocol and needs authentication information from the web client. No action is required. security.audit.authz.denied.audit=SECJ6131I: Access is denied. Access to the resource is denied because the user or the groups the user is in does not have any of the required security role. No action required if this is the desired behavior. security.jacc.modify.task.error=SECJ0398E: Error updating information to the JACC provider for application {0}. The exception is {1}. Cannot provide the security policy information to the JACC provider because of the exception. Without this information, the authorization decisions cannot be made correctly when security is enabled. Make sure that the JACC provider is properly configured and can be accessed. After the problem is fixed, one can either re-install the application or run the propagatePolicyToJACCProvider tool to propagate the policy information to the JACC provider. For more information about this tool, search for propagatePolicyToJaccProvider in the information center documentation. If the modification involved removing any modules, you can delete the information in the JACC provider to avoid redundant data. security.jaas.open.URL=SECJ4037E: {0} :ERROR: Could not open URL: {1}. The exception is {2} MalformedURLException occurred trying to connect the specified URL. Investigate the exception. Check the specified URL. security.mg.createexcp=SECJ0096E: Error creating method group {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.scanner.risk.corba.improve.all.auth=SECJ7529W: The CORBA Namespace can be modified by All Authenticated users. Any authenticated user can alter the JNDI namespace. The default naming security policy is to grant all users read access to the CosNaming space and to grant any authenticated user the privilege to modify the contents of the CosNaming space. You can restrict user access to the CosNaming space. The CORBA Namespace can be modified by All Authenticated users. Any authenticated user can alter the JNDI namespace. The default naming security policy is to grant all users read access to the CosNaming space and to grant any authenticated user the privilege to modify the contents of the CosNaming space. You can restrict user access to the CosNaming space. Restrict user access to the CosNaming space if applicable. security.multidomain.runtime.SECJ7794I=SECJ7794I: No User registry is defined at the domain level of the server. The global security registry will be used. This message is for informational purposes only. No action is required. security.authn.failed=SECJ0056E: Authentication failed for reason {0} Authentication failed with the specified reason. Verify that the user id and password are entered correctly. Consult with the administrator of the user registry if the problem persist. security.configrpt.domain.system.jaas=SECJ7264I: JAAS System Logins None None security.registry.ldap.invalidUserID=SECJ0153E: Invalid LDAP user ID Using user ID that is not valid or the user ID is not a directory entry. The directory administration ID (root DN) is not a directory entry on most LDAP servers. Verify that the user ID is a valid directory entry. security.multidomain.runtime.SECJ7793I=SECJ7793I: A User registry of type {0} is defined at the domain level for the server. This will override use of the global security registry. This message is for informational purposes only. No action is required. security.configrpt.core.activeUserRegistry=SECJ7005I: User account repository None None security.admintask.noLTPAAuthMechanism.SECJ7729E=SECJ7729E: No LTPA auth mechanism was found. An LTPA auth mechanism must be defined. Ensure that an LTPA auth mechanism is defined. security.policy.sysextparser.ignoregrant=SECJ0173W: Grant entry with codebase {0} and signedby {1} is being ignored In the system extension policy files, the grant entries should not specify codebase and signedby values Remove the codebase and signedby values from the grant entry in the system extension policy file. (spi.policy or library.policy) security.configrpt.core.keySets=SECJ7149I: Key sets None None security.multidomain.runtime.SECJ7792I=SECJ7792I: Outbound trusted foreign realms are defined. The following is a the list of such realms {0}. This message is for informational purposes only. No action is required. security.jaas.nosubect=SECJ4033E: The LoginContext does not contain a Subject after authenticating user {0} with LoginModule alias {1}. The LoginModule did not create a Subject. There is a problem with the LoginModule This problem could be due to a configuration error in security.xml or an internal error. security.audit.invalid.shared.key.error=SECJ6045E: Shared key that is not valid has been encountered. A shared key that is not valid was detected. Verify that a valid key is being used. Check the error logs for further information. security.registry.createcredential.nouser=SECJ0362E: Cannot create credential for the user {0}. A user cannot be found to create the credential. Make sure that the user is valid in the registry. Contact your service representative if the problem persists. security.sambean.getusrerr=SECJ0233E: An unexpected exception occurred when trying to get users from the User Registry with pattern {0} and limit {1}. The exception is {2}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.NoSuchAlgorithmException=SECJ7466E: Exception was raised while loading the keystore. A particular crypto algorithm was requested by is not available. The crypto algorithm associated with this keystore is not available. Ensure the crypto algorithm is available. security.admintask.noInterceptor.SECJ7731E=SECJ7731E: The specified interceptor does not exist. The specified interceptor does not exist. Either create the interceptor, or specify a different interceptor class name. security.web.compmetadata.error=SECJ0401E: Error getting the WebModuleMetaData or missing metadata for context root {0}. The exception is {1}. This is an internal error. Without the meta data, the moduleName and applicationName cannot be obtained for access decisions. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.InvalidSequenceNumber=SECJ7459E: Non valid sequence number specified. Sequence numbers begin at 0 and have integer values. A non valid value was specified for the sequence number associated with an audit records to report Specify a non-empty or valid value for the sequence number. security.multidomain.runtime.SECJ7791I=SECJ7791I: Inbound trusted foreign realms are defined. The following is the list of such realms {0}. This message is for informational purposes only. No action is required. security.configrpt.core.WSNotification=SECJ7151I: Notifications None None security.configrpt.milliseconds=SECJ7169I: milliseconds None None security.ltpaserver.notexist=SECJ0058E: LTPAServer does not exist This is an internal error probably due to LTPAServer initialization problems. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.filters=SECJ7248I: SPNEGO Filters None None security.authn.error.owncred=SECJ0131E: Authentication failed. Unable to get the mapped credential for SecOwnCredentials. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.keyGenerationClass=SECJ7197I: Key generation class None None security.policy.sysext.ioexception=SECJ0186E: Caught IOException while creating template for System Extension Policy of type {1} The exception is {0} IOException occurred when creating the system extension template in the hashmap of all the templates. Check the IOException to see the cause for not being able to create the system extension template in the hashmap. security.configrpt.core.isEnabled=SECJ7211I: Enable checking None None security.jaas.app.parse=SECJ4048E: ParserException occurred during parsing jaas application configuration. The exception is {0} ParserException occurred during parsing jaas application configuration. Investigate the exception. It has the information of syntax error in the configuration file. security.servcomp.get.resource=SECJ0291E: Failed to retrieve the information of Resource Adapter for provider ( {0} ) to call setupPolicy(). This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jaas.app.parseIO=SECJ4047E: IOException occurred during parsing jaas application configuration. The exception is {0} IOException occurred during parsing jaas application configuration. Check the configuration file. Investigate the exception. security.sambean.nullsecserver=SECJ0378E: Cannot get SecurityServer in the security MBean. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.scanner.risk.ldaplink.improve=SECJ7538W: User Registry is LDAP. SSL between WebSphere Application Server and LDAP is disabled. The communication between WebSphere Application Server and LDAP is not encrypted User Registry is LDAP. SSL between WebSphere Application Server and LDAP server is disabled. The communication between WebSphere Application Server and LDAP is not encrypted Enable SSL between the WebSphere Application Server and LDAP server if needed. security.multidomain.runtime.SECJ7790I=SECJ7790I: In addition to global security, this server process is associated with a domain security configuration. The domain name of this server is: {0}. This message is for informational purposes only. No action is required. security.admintask.AliasNotPersonalCert=SECJ7420E: Alias is not a personal certificate in key store. The alias is either not in the key store or it is not a personal certificate in the key store. Rerun the command with a personal certificate that is located in the key store. security.jaas.NoCredentialsHelper=SECJ4022E: CORBA: Not suppose to construct CredentialsHelper object CredentialsHelper object instance should not be constructed. Check the user application. CredentialsHelper should not be directly constructed. security.admintask.InvalidKeystoreRef=SECJ7360E: Non valid or no reference specified for the keystore. The keystore reference is a required field. Verify that a valid reference has been specified for the keystore security.configrpt.core.jsseProvider=SECJ7160I: JSSE Provider None None security.sap.error.credential.not.mapped=SECJ5009E: Could not create a WSCredential given the information provided during a propagation login. The following exception occurred: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.certificateAlias=SECJ7187I: Certificate alias None None security.registryimpl.notfound=SECJ0077E: Registry impl class {0} not found for type {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.inclusive=SECJ7183I: Inclusive None None security.configrpt.core.authValidationConfig=SECJ7017I: Authentication validation config None None security.sap.error.authorization.token.not.mapped=SECJ5011E: Could not create default AuthorizationToken during propagation login. The following exception occurred: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.noServerID.SECJ7714E=SECJ7714E: When automatic generation of the server identity is enabled then server id and password should not be specified. When automatic generation of the server id is enable then no server id and password should be provided. Ensure no server id and password is provided when automatic generation of server id is enabled. security.configrpt.domain.AuthMechanism=SECJ7260I: LTPA Timeout None None security.admintask.invalidCommoType.SECJ7752E=SECJ7752E: Communication type is not valid, specify inbound or outbound. The communication type specified is not valid. Either inbound or outbound needs to be specified. Run the command specifying the correct communication type. security.jaas.missingUserRealmOrPwd=SECJ4009E: Either user name, realm or password data is missing. User name, realm name or password is missing. Confirm that the necessary authentication data is passed. Enabling security debug trace for component com.ibm.ws.security.auth.* might yield additional information. security.admintask.NotThirdPartyImpl=SECJ7434E: The audit service provider referenced is not a third party provider implementation. The referenced service provider is not a third party service provider implementation. Enter a valid reference to a third party service provider implementation security.wsaccessmanager.VendorAuthTableSpecificError=SECJ0162E: Vendor''s specific exception. The exception is {0} . This indicates the vendor's specific error. Example:- Server not started, Network failure, Server failed. Depends on the error. security.jsecman.illexit=SECJ0135W: Illegal System.exit() attempted Only the main thread is allowed to exit the Java VM Verify that the code attempting the system exit is not trying to subvert the WebSphere security manager. security.sap.error.propagation.token.not.mapped=SECJ5013E: Could not create default SingleSignonToken during propagation login. The following exception occurred: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.encryption.init.error=SECJ6033E: Failure to initialize Audit encryption algorithm. Exception = {0}. Initialization failure of encryption algorithm. Examine the exception for the cause of the problem. security.merge.custom.property.notadded=SECJ0425I: The custom property {0} from the Node security.xml already exists in the Cell security.xml and will not overwrite the Cell value. Informational. No user action is required. During the server and the cell security object merging, if a custom property with the same name exists in both, the property will not be copied to the cell configuration. It is normal for the cell to have custom properties that match the server. security.jaas.invalidType2.cred.exception=SECJ4054E: InvalidCredentialType exception is caught while serialized Subject is being restored. The exception is {0}. InvalidCredentialType exception occurred while restoring the credential. Investigate the SAS problem. Contact your service representative if the problem persist. security.configrpt.core.options=SECJ7047I: Custom properties None None security.configrpt.Certificate.Console.Path=SECJ7130I: Console Path for Certificate Management None None security.admintask.ErrorLoadingKeystore=SECJ7468E: Error loading the keystore. The password may have been incorrectly specified. Could not open the keystore. Verify that the password was correctly specified and verify the keystore exists. security.configrpt.domain.Auth.Config=SECJ7262I: Authorization Provider None None security.profiletask.failAddingAdminToWim=SECJ7300E: Failed in attempt to add administrative user to virtual member manager Admin user id could not be added to virtual member manager file-based registry Validate virtual member manager has been configured security.admintask.CannotDeleteSigningKeyStore=SECJ7440E: Empty value specified for keystore. Cannot delete the signing keystore when signing is enabled or being enabled. Signing is enabled or is being enabled. The signing keystore is in use and cannot be deleted Disable encryption before deleting the signing keystore. security.audit.service.disabled.audit=SECJ6004I: Security Auditing is disabled. This audit message indicates that the WebSphere Application Server Security Auditing service is disabled. No action is required if this is the desired setting. security.admintask.noSingleSignon.SECJ7728E=SECJ7728E: No singleSignon attribute was found. The LTPA authMechanism must contain a singleSignon attribute. Ensure that the security.xml file contains an LTPA authMechanism with a singleSignon attribute. security.mg.finderr=SECJ0097E: Error finding method groups This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.scopeType=SECJ7190I: Scope Type None None security.admintask.InvalidOutputLocation=SECJ7451E: Non valid or no value specified for the fully qualified path for the location of the output html report. The expected fully qualified file location for the output html report was specified incorrectly. Specify a non-empty valid name for the file location of the output html report. security.jaas.restore.exception=SECJ4050E: An unexpected exception is caught: {0}. Unexpected exception occurred while restoring the credential. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.secure.communications=SECJ7128I: SSL certificate and key management None None security.j2c.unrecognizedCallbackIndex=SECJ4030E: Unrecognizable Callback index = {0} {1} Unrecognizable Callback is passed. Contact your service representative with information present in the error log. security.audit.cert.default.audit=SECJ6122I: Client certificate Authentication failed due to internal error. Will try Basec authentication which is permitted by the web application configuration. The authentication failed due to an unexpected runtime exception. The web application configuration allows authentication using user id and password. Will try to see if there is user id and password information in the HTTP header. No action is required. security.registry.checkpass.failed=SECJ0332E: The checkPassword method failed for user {0}. The checkPassword method failed to return a user. If you are using WebSphere Application Server provided registries, this problem should have been preceeded by other authentication related exception(s). Refere to those exceptions to fix the actual authentication problem. If a custom registry is used, make sure to return a valid userId after authentication is successful. security.admintask.mismatch.krbKeytab.SECJ7780E=SECJ7780E: Mismatch Kerberos keytab file. The keytab file for Kerberos authentication mechanism is {0} but the keytab file for SPNEGO Web authentication is {1} The Kerberos keytab for Kerberos authentication mechanism is not the same with the SPNEGO Web authentication. Verify the Kerberos keytab file for Kerberos authentication and SPNEGO Web authentication are the same one. security.audit.encryption.error=SECJ6030E: Failure to encrypt the audit record. Exception = {0}. Encryption error generated while trying to encrypt the audit record. Examine the exception for the cause of the problem. security.swam.commit.ex=SECJ0261E: Something wrong during LoginModule commit. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.value=SECJ7048I: Value None None security.audit.signing.data.error=SECJ6042E: Data that is not valid was passed into the signing algorithm. A data stream that was not valid was passed in to the signing algorithm. Verify that a non-null byte stream of data is being passed in. security.core.norunasmap=SECJ0111W: RunAsMap Not defined properly for Application {0} The run-as-bindings size is zero for this application. Verify that the run-as bindings are specified for the application if necessary. security.jaas.callBackHandlerIOException=SECJ4013E: An unexpected IOexception occurred in Login Module {0} CallbackHandler. The exception is {1} Exception occurred while processing callbacks Contact your service representative with exception stack trace information present in the error log. security.scanner.risk.drs.improve=SECJ7533W: Encryption is disabled on Distributed Replication Service(DRS). The data shared among WebSphere Application servers is not encrypted. Encryption is disabled on Distributed Replication Service(DRS). The data shared among WebSphere Application servers is not encrypted. Enable Distributed Replication Service encryption if needed. security.zos.saf.role.mapper.loaded=SECJ6224I: The custom SAF role to profile mapper "{0}" has been initialized. A custom SAF role to profile mapper has been configured, loaded, and initialized. No user action is required. security.audit.service.provider.error=SECJ6022E: AuditServiceProvider malfunction when security auditing is required, Provider Exception = {0}. The configured AuditServiceProvider did not run the method in a reasonable time period while security auditing function is required. Examine the exception for the cause of the problem. Typically the business transactions should have been aborted because no security auditing record can be logged. security.audit.csi.unauthn.cred.audit=SECJ6145I: Authenticate to unauthenticated credentials. Setting the credentials to unauthenticated because there is no valid identity token. No action is required. security.admintask.UnsupportedFilterOp=SECJ7377E: Unsupported operation: cannot delete a subset of a multi-set defined filter. Admin task does not support deletion of a subset of a multi-set defined filter. None security.configrpt.core.adminCertificate=SECJ7242I: Personal certificate for encryption None None security.audit.service.invalid.error=SECJ6005E: Invalid configuration {0} = name {1} and class name {2}. The provider configuration in global security custom properties was incorrect. Check the specified properties and in particular the first missing parameter in the error message. security.init.secidequalsrealm=SECJ0226E: The LocalOS server ID ({0}) should not be the same value as the LocalOS realm ({1}) in the security.xml. When the LocalOS server ID is equal to the LocalOS realm, the access ID returned by the operating system is the machine ID not the server ID. Make sure that the server ID is different from the machine ID. security.web.ta.initerr=SECJ0384E: Trust Association Init Error. The Trust Association interceptor implementation {0} initialization failed. The error status/exception is {1}. If you receive this error message in association with a trust association interceptor that you are not using, you can ignore this message. The initialization of this Trust Association implementation failed. Verify that the appropriate Trust Association properties required for the initialization are set up correctly. If you are using your own implementation, check your initilization method for any problems. If a single Trust Association implementation is used, this indicates that the Trust Association is not in effect. However, if multiple TrustAssociation implementations are used, Trust Association can be in effect if one of the implementations is successful. If you receive this error message in association with a trust association interceptor that you are not using, you can ignore this message. security.policy.invalid.filter.permission=SECJ0316W: The permission {0} specified in the filter policy file(filter.policy) does not exist. The permission class specified in the filter policy file does not exist. Fix the filter policy file. security.admintask.TimeStampRangeOutOfOrder=SECJ7457E: Non valid timestamp range specified: the beginning timestamp is greater than the ending timestamp. A non valid value was specified for the timestamps of audit records to report Make sure that the starting timestamp is less than the ending timestamp. security.admintask.authPassed.SECJ7777I=SECJ7777I: Password check for {0} in {1} succeeded. A test to check the users password on a particular realm was sucessful. none. security.configrpt.core.ignoreCase=SECJ7173I: Ignore case for authorization None None security.registry.createcredential.error=SECJ0363E: Cannot create credential for the user {0} because of the following exception {1}. Cannot create credential. Make sure that the user is valid in the registry. If this error is preceeded by other exceptions, check those also. Contact your service representative if the problem persists. security.registry.groupsecurityname.notfound=SECJ0347E: Could not get the name of the group whose uniqueId is {0}. Internal Error. Make sure that the group is valid. Contact your service representative if the problem persists. security.saml.tai.no.custom.property.SECJ8059E=SECJ8059E: There is no {0} custom property. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.csi.ittprincipal.audit=SECJ6142I: Cannot obtain the identity of the ITTPrincipalName. The Identity token is not valid. No action is required. security.scanner.risk.drs.ok.unused=SECJ7532I: Data Replication Service(DRS) is not being used to exchange data among WebSphere Application servers Data Replication Service(DRS) is not being used to exchange data among WebSphere Application servers None security.admintask.InvalidEventType=SECJ7367E: Non valid or no reference specified for the event type. The eventType field is required. Verify that a valid reference has been specified for the event type security.audit.service.sendevent.error=SECJ6024E: AuditServiceProvider failure logging audit event, Exception = {0}. A failure occurred in the auditing subsystem, preventing the event from being processed/logged. Examine the exception for the cause of the problem. security.configrpt.core.Security.Console.Path.Name=SECJ7090I: Console Path Name None None security.sap.error.longsecurityname.not.found.in.hashtable=SECJ5007E: Cannot create WSCredential without a valid com.ibm.wsspi.security.cred.longSecurityName property value. The com.ibm.wsspi.security.cred.longSecurityName property has not been found during a properties login attempt. Ensure that the java.util.Hashtable used for a properties login contains a valid property value for com.ibm.wsspi.security.cred.longSecurityName. security.configrpt.core.Security.applicationLogin=SECJ7094I: Application logins None None security.admintask.InvalidAuditFilters=SECJ7365E: Non valid or no reference specified for the audit filters. The auditFilters reference is a required field. Verify that a valid reference has been specified for the auditFilters security.sasconfig.recoverurl=SECJ0109W: Recovering ({0}) from ({1}) The security configuration URL is being recovered from the future version. This might happen if the security configuration URL is missing or has been deleted. None security.audit.enforcing.nowrap.error=SECJ6053E: The audit log wrapping behavior is set to NOWRAP and the maximum number of audit logs has been reached. Quiescing the server. The server is in a quiesced state. The maximum number of audit logs has been reached and the wrapping behavior is set to not wrap the oldest log. Determine whether the maximum number of audit logs needs to be increased. To get the audit service and server running again, archive all the audit logs to a safe repository, and restart the server. security.jaas.noConfig=SECJ4024W: {0} :Warning: getAppConfigurationEntry() was called with no configuration name. getAppConfigurationEntry() was called with null string. Check the parameter if it is called from user application. If not, Contact your service representative. security.registry.ldap.mapcredentialAmbiguous=SECJ0148E: Cannot create a credential map given credential token certificate subject DN {0} with filter {1} into LDAP because multiple entries match the filter. This ambiguous condition is not supported. More than one user entry in LDAP matched the certificate mapping filter specified in the global security settings. It is not possible to map a subjectDN in a certificate to more than one user in an LDAP user registry. The mapping filter results in an ambiguous condition that cannot be supported. Specify a certificate mapping filter in the LDAP Advanced properties in the Security Center. security.audit.form.login.success.audit=SECJ6154I: Form based authentication was successful. Form based authentication was successful. No action is required. security.registryentry.createerror=SECJ0076E: Error creating registry entry home This is an internal error. Unable to create the home for the registry. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.registry.uniquegrpid.notfound=SECJ0340E: Could not get the uniqueId for the group {0}. Problem getting uniqueId of a group. Make sure that the group is valid in the registry and if it is a custom registry make sure it also has an uniqueId. security.admintask.ExceptionValidAdminName=SECJ7339E: Exception raised while validating admin name Caught exception while validating admin name None security.admintask.FailAddUsertoAdminAuthz=SECJ7311E: Failed to add user to admin-authz.xml Error occurred updating the admin-authz.xml file with the new admin user None security.admintask.CSIDoesNotExist.SECJ7738E=SECJ7738E: The CSI object does not exist. The CSI object does not exist in the configuration. Ensure that the CSI object exists. security.j2c.invalidWSDefaultPrincipalMapping=SECJ4026W: WSDefaultPrincipalMapping() should not be invoked. WSDefaultPrincipalMapping() should not be invoked. This is warning. Check the user application. WSDefaultPrincipalMappingshould not be directly constructed. security.configrpt.core.supportsDynamicModuleUpdates=SECJ7040I: Supports dynamic module updates None None security.zos.saf.authz.enabled=SECJ6214I: SAF authorization is enabled. WebSphere for z/OS has been configured to use the z/OS security product for authorization. The authorization policies for WebSphere must be defined in the EJBROLE class of the z/OS security product. Authorization policies embedded in the applications will be ignored. No user action is required. security.admintask.duplicateAuthDataEntry.SECJ7813E=SECJ7813E: A duplicate alias name exists. You must use a unique alias name. A duplicate alias name in the format alias or nodeName/alias already exists. Input a unique alias name security.admintask.jaspi.provider.undefined.SECJ8010E=SECJ8010E: Authentication provider {0} is not defined in domain {1}. An authentication provider with the specified name does not exist in the security configuration. Specify the name of an existing authentication provider. Use the displayJaspiProviderNames command to list the names of defined authentication providers. security.admintask.ReuseCertError=SECJ7421E: Options to select certificate to use for signing are mutually exclusive. Cannot select reusing encryption certificate for signing with autogenerating or importing. Options are mutually exclusive. Select only one option: to reuse the certificate used for encrypting audit records, autogenerating a certificate to use to sign the audit records, or import a certificate. security.init.wccmjaas.dupentry=SECJ0217W: Detected a duplicate JAAS LoginModule alias name {0} when processing JAAS configuration information. A duplicate JAAS LoginModule alias name exist either in a JAAS login URL or in the security.xml file. The duplicate will be replaced with the last one processed. Verify no duplicate JAAS LoginModule aliases exist in the login URLs or in the security.xml file. security.admintask.fileNotExist=SECJ7545W: The {0} file does not exist This exception is unexpected. The cause is not immediately known. Check the file permissions for the file to ensure that they are readable. If the file is missing, create or restore it. security.zos.saf.idprop.disabled.info=SECJ6235I: The SAF feature for distributed identity mapping is not in effect. The SAF feature for distributed identity mapping is not in effect. No user action is required. security.configrpt.Moderator.Role.User=SECJ7102I: Moderator User None None security.admintask.ExceptionUseRegistryServerId=SECJ7341E: Exception raised while setting useRegistryServerId Exception raised while setting useRegistryServerId in the user registry object None security.j2c.fileNotFound=SECJ4027W: {0} does not exist, use {1} wsj2cdpm.properties Specified file did not exist. Use the default file. This is a warning. Check the specified file name. security.jaspi.configuration.factory.notdefault.SECJ8033I=SECJ8033I: The AuthConfigFactory instance is {0}. The JASPI factory implementation defined is not the default JASPI factory implementation provided by WebSphere Application Server. none. security.admintask.config.object.does.not.exist.SECJ7821E=SECJ7821E: The object {0} does not exist in the security.xml file. The security configuration does not have this object. Run the command with a pre-existing security configuration. security.registry.findererror.type=SECJ0072E: Error finding registry for type {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.registry.nulluser=SECJ0334E: Cannot create credential for null user. Internal Error. The user name provided to create the credential is null. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.badAdminID.SECJ7716E=SECJ7716E: Primary administrative user Id does not exist in the registry. The primary administrative id specified was not found the user registry. Ensure a primary administrative id is provided. security.scanner.error.parse.xml=SECJ7502E: An exception occured while parsing the XML file "{0}". Detailed message: {1} An exception occured while parsing a configuration document. Check the error logs for more information into the failure. security.audit.service.exception.error=SECJ6008E: Exception caught in AuditService initialization, Exception = {0}. Runtime exception occured most likely due to incorrect class definition, incorrect class path, or missing class files. Examine the exception for the cause of the problem. security.configrpt.core.enable=SECJ7054I: Enable None None security.audit.cert.exception.audit=SECJ6121I: Client certificate Authentication failed due to internal error. The authentication failed due to an unexpected runtime exception. Report the problem to IBM. security.configrpt.core.enableOutOfSequenceDetection=SECJ7272I: Enable out of sequence detection None None security.admintask.CustomReportNoDataPoints=SECJ7453E: The report mode chosen is custom but no data points were specified. When specifying a report mode of custom, one or more data points must be specified. Specify one or more data points when electing to generate a custom report. security.configrpt.core.App.Servers=SECJ7279I: Application servers None None security.configrpt.core.dayOfWeek=SECJ7202I: Day of week None None security.zos.saf.idprop.versionNumber.info=SECJ6233I: The version number of the SAF product is: {0}. The version of the SAF product is displayed. No user action is required. security.admintask.CannotRemoveAuditorId=SECJ7435E: Empty value specified for auditorId. Cannot delete the auditorId when auditing is enabled. Auditing is enabled and requires an auditorId and auditorPwd. Disable auditing before deleting the auditorId security.audit.service.no.security.audit=SECJ6103I: Access to a web resource is allowed because no access control is required. Access to a web resource does not require access control because there is no security constraint. The URI is not protected. No action is required is this is the desired configuration. Otherwise, proper security constraint should be added to the web application. security.configrpt.core.ntlmTokenReceivedPage=SECJ7253I: NTLM token received page URL None None security.jsecman.exception.codebase=SECJ0307E: Unexpected exception is caught when trying to determine the code base location. Exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.tai.success.audit=SECJ6115I: Authentication successful with Trust Accosication Interceptor. The authentication via the specified Trust Association Interceptor was successful. No action is required. security.jacc.secpolicy.propagated=SECJ0415I: The security policy for application {0} is successfully propagated to the JACC provider. This message is provided for information purposes only. No user action is required. security.init.sambean=SECJ0205I: Security Admin mBean registered successfully The Security Admin mBean registered successfully None. Informational only. security.sap.error.authentication.token.not.mapped=SECJ5010E: Could not create default AuthenticationToken during propagation login. The following exception occurred: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.audit.service.missing.warning=SECJ6011W: Custom property {0} was not defined. The specified audit service provider was not defined in the global security custom properties. Define the specified properties if security auditing service is required in your business environment. security.jaas.removeCredException=SECJ4017E: An unexpected exception occurred in Login Module {0} when removing WSCredential during cleanup {1} Exception occurred while removing the credential. Contact your service representative with exception stack trace information present in the error log. security.policy.template.parser=SECJ0310E: Caught a ParserException while adding the grant entry to the policy template {1}. The exception is {0} A ParserException occurred while adding the grant entry to the policy template. Check the ParserException data. Check the specified policy file. security.web.httpsPort.notFound=SECJ0428E: The product cannot locate the HTTPS port value in the list of virtual hosts. Confirm that the port exists in the virtualhosts.xml file for the cell. The product cannot locate the HTTPS port value that is specified in the URL. The port value is not found in the list of virtual hosts. Check that the HTTPS port value that is specified is in the virtualhosts.xml file for the cell. The virtualhosts.xml file is located in the profile_root/config/cells/cell_name directory. security.secvrfactory.createrr=SECJ0245E: An unexpected exception occurred when the SecurityServerFactory tried to create the SecurityServer. The exception is {0}. An error occurred that prevented the SecurityServer from being created. The log should contain additional errors that might indicate the cause of the problem. security.admintask.InvalidNotificationRef=SECJ7376E: Non valid reference for Audit Notification. Non valid reference for audit notification specified. Verify that a valid reference has been specified for the audit notification security.ltpa.nopasswd.nocreate=SECJ0059E: Cannot create LTPAServer without a password The wrong constructor was used when trying to create an instance of LTPAServerBean. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.jaspi.provider.registered.SECJ8031I=SECJ8031I: JASPI binding has been registered: Application={0}, Web Module={1}, Registration ID={2}[{3}], Provider Class={4}. The named JASPI provider will perform authentication of web requests for the named application and web module. none. security.jaspi.configuration.provider.invalid.SECJ8029E=SECJ8029E: The provider name in the application's or web module's bindings is null or is empty. The web module's JASPI binding cannot be registered in AuthConfigFactory because the provider name is null. Verify the provider name in the application's or web module's bindings is defined in the security configuration. security.audit.service.bad.factory.error=SECJ6013E: The configured J2EE AuditEventFactory implementation did not implement the J2EEAuditEventFactory interface. As a convention, an AuditEventFactory implementation that is configured under the J2EE name must implement the J2EEAuditEventFactory interface. Examine the com.ibm.websphere.security.audit.AuditEventFactory properties in global security custom properties. security.configrpt.core.minute=SECJ7193I: Minute None None security.web.authz.isuserinrole.failed=SECJ0393E: Error when checking the isUserInRole requirement for the contextID {0}. The exception is {1}. Could not determine the isUserInRole requirements for this resource. The default value false will be returned Make sure that the RoleRef information is correctly configured in the deployment descriptor. security.admintask.InvalidAuditorId=SECJ7358E: Non valid or no value specified for auditor identity. The auditor identity is a required field. Verify that a value has been specified for the auditor identity security.mg.removeerr=SECJ0101E: Error removing method group This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.authn.invalid.data=SECJ0057E: Invalid authentication data This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.NoEncryptionKeyStore=SECJ7422E: Cannot use the encryption certificate as the signer certificate: No encryption keystore found. No encryption keystore found: unable to reuse the same certificate for signing audit records. None security.adminapp.other.error.SECJ8024E=SECJ8024E: An error occurred processing Jaspi bindings during application deployment. {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.loginAliasDoesNotExist.SECJ7736E=SECJ7736E: The JAAS login entry {0} does not exist. The JAAS login entry does not exist in the configuration. Ensure that the JAAS login entry exists. security.wsaccessmanager.VendorAuthTableGenericError=SECJ0163E: Generic Error from Vendor AuthorizationTable Unknown error from Vendor's authorization table Contact your service representative with exception stack trace information present in the error log. security.audit.service.login.audit=SECJ6104I: Access to a web resource is allowed because the URI is either login page, error page or form login page. Access to login page, error page, and form login page does not require access control. The URI is not protected. No action is required. security.policy.ratemplate.io=SECJ0199E: Caught an IOException while adding the grant entry to the policy template of the resource adaptor {1} . The exception is {0}. An IOException occurred while adding the grant entry to the policy template of the resource adaptor. Check the specified ra.xml file. security.web.config.error=SECJ0086E: Configuration error This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.MalformedURLException=SECJ7464E: Exception was raised while trying to open the keystore. The keystore location is malformed. The keystore location url is malformed. Verify that the keystore location is valid and that the keystore does exist. security.audit.service.access.default.audit=SECJ6014I: AuditEventType = {0}, AuditOutcome = {1}, AuditOutcomeReason = {2}, unique Event ID = {3}, Cell Name = {4}, Node Name = {5}, Server Name = {6}, Component Name = {7}, App Name = {8}, Session ID = {9}, Resource Name = {10}, Resource Type = {11}, Method Name = {12}, Provider Name = {13}, Provider Successful = {14}, Exception = {15}. This message is intended to be used by the defaultAuditEventFactoryImpl sendAccessAuditEvent method only. No action required. security.admintask.localModeNotSupported.SECJ7814E=SECJ7814E: This command is not supported in local mode This command is not supported in local mode This command is not supported in local mode security.secsrv.create.registry=SECJ0281E: Error creating user registry object. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.j2eePolicyImplClassName=SECJ7035I: J2EE Policy implementation class name None None security.sas.initerror=SECJ0045E: Error initializing security/SAS An error occurred while initializing the Secure Association Service, which is part of the ORB security. Verify that the property file, usually sas.server.props, is present and has read permission. security.registry.ldap.connected.audit=SECJ0419I: The user registry is currently connected to the LDAP server {0}. This name refers to the LDAP host name that is currently used by the WebSphere Application Server security registry. No user action is required. security.configrpt.core.trustStore=SECJ7161I: Trust store None None security.configrpt.core.systemLoginConfig=SECJ7082I: System login configuration None None security.mg.finderr.one=SECJ0098E: Error finding method group {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.configrpt.core.trustFileName=SECJ7076I: Trust file name None None security.sas.encode.error=SECJ0106E: An unexpected exception occurred when encoding the value [{0}] for password [{1}] in the security configured URL The password cannot be encoded because it is missing or malformed. Verify that the passwords in the security configuration URL are not corrupted or missing. Reset the affected password through the WebSphere Admin console if possible. If all else fails, reset the password to its plain text value in the security configuration URL (which is usually sas.server.props). security.ejb.getreqrole.exception=SECJ0113E: An unexpected exception occurred in getRequiredRoles for method {0} and resource {1}. The exception is {2} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.sasconfig.propload=SECJ0110E: I/O Error occurred when loading property URL {0} A loadProperties() operation probably failed. Verify that the file permissions associated with security configuration URL property file (typically sas.server.props) are read and writable. security.audit.csi.cert.failure.audit=SECJ6144I: Authentication failed. Failed to convert the client certificate. No action is required. security.configrpt.core.IBM=SECJ7066I: SAS None None security.configrpt.core.wsNotification=SECJ7213I: Notifications None None security.admintask.noUnconfigure.SECJ7726E=SECJ7726E: {0} is the active user registry unable to unconfigure. A user registy cannot be unconfigured if it is the active user registry. Change the active user registry in the global security setting then unconfigure the user registry. security.audit.service.enabled.audit=SECJ6000I: Security Auditing is enabled. This audit message indicates that the WebSphere Application Server Security Auditing service is enabled. No action is required is this is the desired setting. security.configrpt.core.repertoire=SECJ7067I: SSL configuration repertoires None None security.merge.node.missing.server.password=SECJ0427E: The server password is null or missing in the dmgr configuration. Cannot add an older version node unless the server password is entered. An earlier leveled node cannot be added to a dmgr whose configuration is missing the server password The dmgr configuration needs to be modified to specify the server password security.audit.service.loading.error=SECJ6002E: Failed to load {0} name {1} and class name {2}. Failed to load the specified class which was defined in the global security custom properties. Verify that the class name, class path, and class file are configured properly. security.admintask.KeyStoreObjectExists=SECJ7402E: Encryption key file object already exists. The specified object already exists. Unable to create another one. Create the object with a unique name security.admintask.FailAccesstoSecWS=SECJ7312E: Failed to get to Security workspace Exception raised when accessing the Security object in the workspace None security.j2c.unexpectedIOException=SECJ4031E: Unexpected IOException caught {0} Unexpected IOException was caught while processing callbacks. Contact your service representative with exception stack trace information present in the error log. security.admintask.NotificationMonitorNotConfigured=SECJ7381E: Audit Notification Monitor is not configured. Audit Notification Monitor is not configured. None security.policy.all.permission=SECJ0319I: java.security.AllPermission was found in the application policy file {0}. java.securityAllPermission was found in the application. none. This is an informational message. security.configrpt.core.WSSchedule=SECJ7150I: Schedules None None security.configrpt.core.enabledCiphers=SECJ7159I: Enabled Ciphers None None security.servcomp.removePolicy=SECJ0289E: Failed to call removePolicy for {0}. A unexpected exception occurred when trying to call the removePolicy() method for the specified type. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.policy.rar.path=SECJ0179E: An exception was caught while trying to get the Resource adaptor''s absolute file path. The exception is {0}. Could not get the absolute filepath of the resource adaptor policy file. Check the filepath specified in resource.xml file. Enable security trace with com.ibm.ws.security.policy.* to get more detailed information. security.admintask.EventFactoryExists=SECJ7389E: An audit event factory implementation with this unique name is already configured. Cannot configure an audit event factory with the same unique name as one that is already configured. Specify a unique name for the new audit event factory security.mg.createerr=SECJ0102E: Error creating method group This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.web.cred.getTokFail=SECJ0116W: Unable to extract the credential token from the credential The credential is possibly malformed or corrupted. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.admintask.noRealms.SECJ7753E=SECJ7753E: No realms provided to add to the trusted realm list. No realm name were provided to add the the trusted realm list. Ensure a realm or realm list is provided when the command is run.