There are 2 Workarounds to this issue.
Workaround # 1. Get the FglAM installer from the Linux or Windows FMS where the new FglAM is going to connect to.
FglAM Installers that are downloaded from an FMS contain an embedded Auth-Token that is used as a means to authenticate the FglAM client. When the FglAM installation is run, this auth-token is registered within the FglAM runtime and used to authenticate with the FMS when connecting.
Things to take into consideration when installing FglAM that uses https connection to the FMS:
- If the error message indicates that Authorization header(s) not valid, that is, the FglAM installer might not be downloaded from the FMS that you connected to.
- If the error message indicates that Request too old, the clock drift between the FglAM machine and FMS machine might be more than 10 minutes. The timestamp header value in FglAM machine is too old or ahead, there will cause the request to be rejected by FMS.
- If the error message indicates that Missing required authorization header(s), then there might be something wrong with the securityContext. Create a support case for further investigation.
For silent installation, please check the FglAM log for the error message.
In conclusion, there are 2 pre-conditions for FglAM 8.1 & FMS 7.1 :
- The FglAM installer must be downloaded from the prepared FMS.
- The clock drift between the FglAM machine and FMS machine must be less than 10 minutes.
WORKAROUND # 2. Download FglAm 5.8.5 and set disable the Auth Token check in the FglAm adapter.
FglAM 5.8.5 which is compatible with FMS 5.7.1 contains a switch to disable the Auth Token feature. The switch is located in the FglAM Adapter properties.
