logout state clean up #3219
Merged
logout state clean up #3219
Conversation
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
prakashsvmx
requested review from
bexsoft,
dvaldivia,
jinapurapu,
kaankabalak and
reivaj05
reivaj05
approved these changes
Feb 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #3210
Issue Replication steps
create a the policy as in #3210
As an admin,
create a bucket
clientsand someprefixesliketest-userandtest-user-1and upload files to each prefixes.create 2 users
test-userandtest-user1and assign the policy.in a different browser, login as
test-userand navigate to the prefix and logout.now in the same browser login as
test-user-1and navigate . observe "Access Denied" this is due to previous state (bucket, prefix is retained) is not reset and request is made to the old state prefix. ( hard reload i.e Refresh of browser window would work as expected)Verify the fix.
build and run the PR.
With this fix, the above steps would not result in "Access denied" error.