We are currently working on LGTM deployment, where the deployment activity involves certificate installation on the target hosts.
The deployment was successful in the Development environment. However, for Production and TE2 environments, the deployment did not proceed directly as it went for approval. To avoid approval dependency, the required hosts were whitelisted under reference number: .
Even after whitelisting the hosts, the deployment still went for approval. We have now scheduled a call with the CREDS team to understand what additional configuration or mapping is required.
As per the available FAQ, the technical account may also need to be mapped in ISAAC for the deployment to proceed without approval. We need support to confirm the complete requirement and identify what is currently missing, so that future LGTM deployments to Production and TE2 can proceed without manual approval for this account.
Request:
Please help review the current setup and confirm:
Whether the host whitelisting has been correctly applied.
Whether the technical account needs to be mapped in ISAAC.
Any additional approval bypass configuration required for Production and TE2.
What changes are needed so that LGTM certificate deployment can proceed without approval for this account. :::
A shorter title could be:
LGTM deployment going for approval despite host whitelisting
0 comments:
Post a Comment