Discord authenticated context mapping #248
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
|
Thanks for the patch |
woutervs
added a commit
to woutervs/StsExample
that referenced
this pull request
Aug 22, 2019
Some magic to connect to discord account but prevent unverified users to connect (we automagically sync by e-mail address if an unverified discord user tries to connect and there's a local e-mailaddress connected he could impersonate...) Also using the owin project locally cause the nuget package contains a bug (PR TerribleDev/OwinOAuthProviders#248)
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.
When trying to map the verified property on the user json object this always resulted in false because discord serializes true as "True" added a tolowerinvariant to counter this.