fix the invalid scope by adding .default #1678
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
Signed-off-by: David Justice <[email protected]>
devigned
force-pushed
the
cosmos-scope-fix
branch
from
b5f69a8 to
4c79a0d
Compare
Signed-off-by: David Justice <[email protected]>
heaths
approved these changes
Jun 17, 2024
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.
fixes #1593
The CosmosDB scope is currently incorrectly formatted as
"https://${YOUR_ACCOUNT_NAME}.documents.azure.com". This causes an error when using any auth flow other than primary key. This PR fixes the scope formatting changing the scope to"https://${YOUR_ACCOUNT_NAME}.documents.azure.com/.default".I have validated that this via sample apps: