Add support for MeB.org OAuth provider #510
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
|
TODO: Rename scopes for MeB.org to use project namespaces and check for the relevant scopes here. |
|
Once BB and LB have migrated to using new tokens exclusively, the old OAuth provider in CB can be removed. |
amCap1712
force-pushed
the
oauth-meb-support
branch
from
1ecc1ae to
7ded448
Compare
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.
Use the newly developed MeB.org OAuth provider for handling login. Also, add support for writing reviews, voting and retrieving profile if the appropriate scopes are granted to tokens issued by the MeB.org provider. To distinguish the origin of the tokens, the fact that MeB.org issued tokens start with
meba_can be used.