Add in Cache-Control headers with CyberArk Credential Providers#104
Open
iam-decoder wants to merge 3 commits intoansible:develfrom
Open
Add in Cache-Control headers with CyberArk Credential Providers#104iam-decoder wants to merge 3 commits intoansible:develfrom
iam-decoder wants to merge 3 commits intoansible:develfrom
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. ❌ Your patch check has failed because the patch coverage (50.00%) is below the target coverage (100.00%). You can increase the patch coverage or adjust the target coverage. |
This file contains hidden or 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.
We've been noticing a lot lately that when we request credentials through these plugins that the password almost always pulls an older password, after forcing a cache-less approach in our CyberArk servers we were finally able to get current passwords. However, running in an enterprise environment, we can't have caching disabled indefinitely.
I searched long for any way to add in headers to the UI to handle this but that bore no fruit. Hoping this gets reviewed and deployed timely to correct my issues.
Thank you for your consideration.