Explanation | The token factory was not initialized. |
Action | Validate the Token Manager configuration in the server.xml file, or any other resource specified by the configuration. |
Explanation | The unique_id parameter is null or was not specified in the token data. |
Action | Validate that the user has a unique ID. If using a custom user registry, validate that the token data contains a value for the unique_id parameter. |
Explanation | The specified key is missing, so the LTPA token cannot be created. |
Action | Explore the properties file in which the LTPA key information is stored, and check that the key information includes a secret key, a private key and a public key. |
Explanation | The LTPA keys do not exist and are generated automatically. Any services requiring LTPA will not start until the LTPA keys have been generated and the configuration is ready. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The LTPA keys could not be read or created at the specified location. |
Action | Ensure the location is accessible by the server process. Any FFDCs might indicate a fatal error in generating or loading the keys. |
Explanation | The LTPA keys need to be reloaded because there was a change to the LTPA keys file or the configuration. |
Action | Ensure that all servers participating in Single-Sign-On use the same LTPA keys and password. |