Updated guidance based on experience #1
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
JasSuri
reviewed
Oct 6, 2020
| @@ -450,8 +450,8 @@ | |||
| <Item Key="UserMessageIfOldPasswordUsed">Looks like you used an old password</Item> | |||
|
|
|||
| <Item Key="ProviderName">https://sts.windows.net/</Item> | |||
| <Item Key="METADATA">https://login.microsoftonline.com/{tenant}/.well-known/openid-configuration</Item> | |||
| <Item Key="authorization_endpoint">https://login.microsoftonline.com/{tenant}/oauth2/token</Item> | |||
| <Item Key="METADATA">https://login.microsoftonline.com/{your_tenantId}/.well-known/openid-configuration</Item> | |||
There was a problem hiding this comment.
These are special identifiers {tenant}, you shouldn't actually need to populate these at all.
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.
I added some notes on readme.md based on my experience in implementing this sample. Also updated the policy file and replaced {tenant} to {your_tenantId} to be consistent with the guidance in readme.md