Return
-
Title
How to generate a new FMS/FglAM auth-token -
Description
Starting in FMS 5.7.1 / FglAM 5.8.1, a valid auth-token must exist to allow FMS and Agent Manager (FglAM) to communicate with each other.
If this auth-token doesn't match, or becomes invalid, or is missing, use the following steps to create a new one.
-
Cause
If the auth-token is missing, or cannot be loaded, FglAM will not start successfully, the following error will appear in the FglAM logs:
2015-02-17 15:33:57.573 VERBOSE [Startup Thread] com.quest.glue.common.util.crypto.KeyStoreManager - Restoring securityContext Keystore from /local/quest/foglight/foglight/fglam/state/securityContext/securityContext.keystore2015-02-17 15:33:57.576 VERBOSE [Startup Thread] com.quest.glue.common.util.crypto.KeyStoreManager - securityContext Keystore has been initialized2015-02-17 15:33:57.579 VERBOSE [Startup Thread] com.quest.glue.common.util.crypto.KeyStoreManager - securityContext KeyStore has been persisted to /local/quest/foglight/foglight/fglam/state/securityContext/securityContext.keystore2015-02-17 15:33:57.580 DEBUG [Startup Thread] com.quest.glue.core.comms.auth.CoreSecurityContext - Caught unimportant exception; safe to ignore: No access token available during startup.2015-02-17 15:33:57.582 ERROR [Startup Thread] com.quest.glue.core.Glue - Auth-Token is not available within current security context. Startup aborting.2015-02-17 15:33:57.596 ERROR [Startup Thread] com.quest.glue.core.Glue - Unable to start. Cause: Failed to load Auth-Token.java.lang.SecurityException: Failed to load Auth-Token. -
Resolution
Please follow the instructions attached to this article to recreate the auth-token.
Please note that the steps are different if the Agent Manager (FglAM) is embedded compared to a non-embedded FglAM. Steps for both are included.
-
Attachments