Skip to content

CosmosClient should propagate the new AuthorizationToken to the AuthorizationPolicy #337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
MindFlavor opened this issue Aug 5, 2021 · 0 comments · Fixed by #339
Closed

CosmosClient should propagate the new AuthorizationToken to the AuthorizationPolicy #337

MindFlavor opened this issue Aug 5, 2021 · 0 comments · Fixed by #339
Assignees
@MindFlavor
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved.

Comments

@MindFlavor
Copy link
Contributor

As seen in #331, the permission_token_usage test fails because the change of AuthorizationToken does not get propagated to the new AuthorizationPolicy.
What happens is that the "old" code uses the new token while the "new" one (the one using the AuthorizationPolicy) does not.
@MindFlavor MindFlavor added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Aug 5, 2021
@MindFlavor MindFlavor self-assigned this Aug 5, 2021
@MindFlavor MindFlavor mentioned this issue Aug 5, 2021
Merged
@github-actions github-actions bot locked and limited conversation to collaborators Feb 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@MindFlavor MindFlavor

Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

CosmosDB: support for changing AuthorizationToken in pipeline MindFlavor/azure-sdk-for-rust
1 participant
@MindFlavor