accomodate cert chain for raoidc sade environments on new 10 dot star… #747
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new 10.* IP's (and their DNS) for ECAS RAOIDC come with a new certificate chain that has to be added so that the sade servers can successfully communicate with RAOIDC. These changes add that certificate to the Dockerfile. Note that it is necessary to add a build argument in teamcity for the cert to be included in the container successfully:
--build-arg AUTH_ECAS_CA=%env.AUTH_ECAS_CA%There is a corresponding vault entry to house the new certificate (%vault:bdm-dev-secure-client-hub/data/NEXT-AUTH!/AUTH_ECAS_CA%)