WebUI SecurityCenter messages

SECG0001E: Cannot find SecurityAdmin MBean. The exception is {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0002E: An exception occurred in ConnectToRuntime when the server checked the password for user: {0}. The exception is {1}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: This exception can occur when the configured user registry cannot be contacted to perform authentication. The user registry might be configured correctly. However, check the user registry configuration and also verify that if you are using a local OS user registry, the user name that the WebSphere Application Server process is using has the right privileges to contact the registry application programming interfaces (APIs) (On UNIX systems, the server has the root privilege and on Windows systems the server has the "Act as part of operating system" privilege).

SECG0003E: An exception occurred in ConnectToRuntime when generating Lightweight Third Party Authentication (LTPA) keys. The exception is {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0004E: An exception occurred when importing Lightweight Third Party Authentication (LTPA) keys: The exception is {0}.
Explanation: Unable to import specified Lightweight Third Party Authentication (LTPA) keys. The most likely cause is the password is not valid and cannot decrypt the importing keys.
User Response: Verify that the password matches the Lightweight Third Party Authentication (LTPA) keys. This password must exactly match the password that is used to generate the keys on the originating server. If the password is unknown, generate the keys and export them again. Record the password. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0005E: An exception occurred when exporting Lightweight Third Party Authentication (LTPA) keys: The exception is {0}.
Explanation: Unable to get the Lightweight Third Party Authentication (LTPA) keys from the server.
User Response: Regenerate the keys and try the operation again. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0006E: An exception occurred in ConnectToRuntime when retrieving the realm. The exception is {0}.
Explanation: Unable to get the realm for the active user registry.
User Response: Verify that the user registry configuration is correct. If you are using a Local OS user registry, verify that the process running WebSphere Application Server can access the registry application programming interfaces(APIs) (On UNIX systems, the user has root privilege and on Windows systems the user has "Act as part of operating system" privilege).

SECG0007E: An exception occurred when exporting the Java Authentication and Authorization Service (JAAS) configuration: {0}.
Explanation: Unable to update the Java Authentication and Authorization Service (JAAS) run time.
User Response: Retry the operation after a few minutes. If the problem persists, contact IBM support for assistance.

SECG0008E: A SecurityAdmin MBean was not found for the object {0}: returning null.
Explanation: The administrative service factory was unable to locate an MBean for the object name in the message.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0009E: The Security object was not found in the Java Authentication and Authorization Service (JAAS) run time update.
Explanation: A security.xml file was not found in the resource set.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0010E: An exception occurred retrieving the security object: {0}.
Explanation: A security.xml file was not found in the resource set.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0011E: The Security object was not found in extent in changeLdapDirType().
Explanation: A security.xml file was not found in the resource set or the Security object was not found in the security.xml file.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0012W: An exception occurred retrieving the contents of the LdapConfig.nlsprops file: {0}.
Explanation: LdapConfig.nlsprops is unavailable. The file might not exist or the current user might not have the read access.
User Response: If the server process is not owned by the root user, or a user with administrator privileges on Windows systems, verify that the user who owns the process on which the server is running has the proper access privileges on all of the server files. See the ldapConfig.nlsprops to check the permissions. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0013W: An exception occurred closing the LdapConfig.nlsprops file: {0}.
Explanation: Unable to close the LdapConfig.nlsprops file. This exception is usually caused by file contention.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

SECG0014W: An exception occurred retrieving the contents of the LdapConfig.nlsprops file: {0}.
Explanation: LdapConfig.nlsprops is unavailable. The file might not exist or the current user might not have read access.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0015W: A Lightweight Directory Access Protocol (LDAP) search filter entry was not found in the security.xml file in the LDAP User Registry section.
Explanation: A Lightweight Directory Access Protocol (LDAP) search filter was not available.
User Response: Add the new Lightweight Directory Access Protocol (LDAP) search filter entry through the administrative console. To add the entry, expand Security > User Registries and click LDAP. Under Additional Properties, click Advanced LDAP Settings. If the problem persists, contact IBM support for assistance.

SECG0016E: An exception occurred while importing the Lightweight Third Party Authentication (LTPA) keys: {0}.
Explanation: The server was unable to import the specified Lightweight Third Party Authentication (LTPA) keys.
User Response: Verify that the Lightweight Third Party Authentication (LTPA) keys are available in the specified location. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0017E: An exception occurred while exporting the Lightweight Third Party Authentication (LTPA) keys: {0}.
Explanation: The server was unable to export the Lightweight Third Party Authentication (LTPA) keys to the specified location. The user might not have write access to the target directory.
User Response: Verify that the user has write access to the location specified. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0018E: An exception occurred while extracting the resource {0}: {1}.
Explanation: A security.xml file was not found in the resource set.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0019E: An exception occurred while loading the resource {0}: {1}.
Explanation: A security.xml file was not found in the resource set.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0020E: An exception occurred while creating a new security.xml file and security extent in context {0}: {1}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0021E: An exception occurred while validating security configuration values: {0}.
Explanation: Improper values might be specified in the field.
User Response: Verify that the proper value was entered. If the problem persists, contact IBM support for assistance.

SECG0022E: An exception occurred while setting the Lightweight Directory Access Protocol (LDAP) security configuration values: {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0023E: An exception occurred while creating a new security.xml file and security extent in context {0}: {1}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0024W: The security.xml file was not available in the context {0}.
Explanation: A security.xml file was not found in the resource set.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0025E: An exception occurred while loading the security object in the context {0}: {1}.
Explanation: A security.xml file was not found in the resource set.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0026E: An exception occurred while setting up the detail form for server security: {0}.
Explanation: Errors might exist in the security.xml file.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0027E: The Ignore case option is required for the Lightweight Directory Access Protocol (LDAP) directory type {0}.
Explanation: Select the Ignore case option for the LDAP directory type selected.
User Response: Enable the Ignore case option in the administrative console. Expand Security > User Registries. Click LDAP and select the Ignore case option.

SECG0028E: The Registry object does not exist.
Explanation: An internal error has occurred. The security configuration file might be corrupted.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0029E: The Lightweight Third Party Authentication (LTPA) object does not exist.
Explanation: An internal error has occurred. The security configuration file might be corrupted.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0030E: The Lightweight Third Party Authentication (LTPA) password is missing.
Explanation: A Lightweight Third Party Authentication (LTPA) password is needed to generate LTPA keys.
User Response: Verify that the Lightweight Third Party Authentication (LTPA) password is set. Expand Security > Global security > Authentication mechanisms. Click LTPA, and make sure that a value is present in the password field. If the password is already set, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0031E: The Lightweight Third Party Authentication (LTPA) keys are missing.
Explanation: The server cannot find the Lightweight Third Party Authentication (LTPA) keys.
User Response: Verify that the Lightweight Third Party Authentication (LTPA) password is set. Expand Security > Global security > Authentication mechanisms. Click LTPA, and make sure that a value is present in the password field. Check for other possible exceptions. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0032E: The Lightweight Directory Access Protocol (LDAP) directory type is missing.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0033E: The Lightweight Directory Access Protocol (LDAP) search filter object does not exist.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0034E: The Lightweight Directory Access Protocol (LDAP) host name is missing.
Explanation: The Lightweight Directory Access Protocol (LDAP) host name, which is required to connect to the LDAP server, is missing.
User Response: Verify that the Lightweight Directory Access Protocol (LDAP) host name exists in the LDAP configuration. Expand Security > Global security > User registries. Click LDAP and make sure that the host name has a valid value. If the value is valid, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0035E: The custom user registry class name is missing.
Explanation: The server cannot retrieve the custom user registry implementation file name.
User Response: Verify that the custom user registry implementation class name exists in the custom user registry configuration. Expand Security > Global security > User registries. Click Custom, and make sure that the Custom registry class name field has a valid value. If the class name exists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0036E: The server cannot find the SecurityAdmin MBean.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0037E: An exception occurred in ConnectToRuntime when checking the Secure Sockets Layer (SSL) key file: The exception is {0}.
Explanation: The server is unable to validate the Secure Sockets Layer (SSL) key file information.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0038E: An exception occurred in ConnectToRuntime when checking the Secure Sockets Layer (SSL) trust file: The exception is {0}.
Explanation: The server is unable to validate the Secure Sockets Layer (SSL) trust file information.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG0039E: An exception occurred in ConnectToRuntime when checking the cryptographic token library file: The exception is {0}.
Explanation: The server is unable to validate the cryptographic token library file information.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

SECG1000E: An exception occurred loading the resource {0}: {1}.
Explanation: A ws-security.xml file was not found in the resource set.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

SECG1001W: The ws-security.xml file was not available in the context {0}.
Explanation: A ws-security.xml file was not found in the resource context.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.