Handling 401 response code during stig mode #154
Merged
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
rajendraindukuri
requested review from
Deepak-Ghivari,
francis-nijay,
karthikk92,
bandak2,
rensyct and
panigs7
as code owners
karthikk92
approved these changes
Jul 12, 2023
panigs7
approved these changes
Jul 12, 2023
This commit contains changes needed to pass skipCertificateValidation flag from secrets file via configConnect object from csi-unity to goUnity so that the same can be leveraged during authentication retry when we hit 401 issue due to sessionIdleTimeout in STIG mode
rajendraindukuri
force-pushed
the
handling-401-response-code-during-stig-mode
branch
from
83de9ad
to
419dc95
Compare
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.
Description
Added skipValidationFlag to configConnect object to pass it to authenticate method which is useful in re-establishing session in
case of STIG mode when we hit genuine 401 error code
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?