[5.x] Add Slack OpenID provider #704
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
|
@driesvints You're welcome. I just converted this PR to draft to add some tests. |
|
Thanks @maartenpaauw. We'd also appreciate a PR to the docs! |
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.
This pull request adds a separate Slack OpenID provider. It follows the entire auth flow, documented by Slack at: https://api.slack.com/authentication/sign-in-with-slack#implementation
The name of the provider class and retrieving configuration is inspired based on the LinkedIn OpenID provider.
To try the new provider out, you have to create a Slack application with the user scopes
openid,profileandemail.This pull request closes issue #702