A valid auth-token must exist to allow the Foglight Management Server (FMS) and Agent Manager (FglAM) to communicate with each other.
If this auth-token doesn't match, becomes invalid, or is missing, use the following steps to create a new one.
If the auth-token is missing, or cannot be loaded, FglAM will not start successfully, the following error will appear in the FglAM logs:
YYYY-MM-DD 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.keystore
YYYY-MM-DD 15:33:57.576 VERBOSE [Startup Thread] com.quest.glue.common.util.crypto.KeyStoreManager - securityContext Keystore has been initialized
YYYY-MM-DD 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.keystore
YYYY-MM-DD 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.
YYYY-MM-DD 15:33:57.582 ERROR [Startup Thread] com.quest.glue.core.Glue - Auth-Token is not available within current security context. Startup aborting.
YYYY-MM-DD 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.
Please follow the instructions to recreate the auth-token; note that the steps are different if the Agent Manager (FglAM) is embedded compared to a non-embedded FglAM. Steps for both are included.
NOTE: Please note that there are 3 copies of this function. We’re interested in the one with 2 Prams; as of this writing, it is the 3rd (last) entry of generateAuthToken(). See screenshot below.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center