Handle secret hash for multiple issuers #4
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
SeanArmstrong
approved these changes
Jun 15, 2017
|
Can you bump the version number too? https://github.com/Sage/omniauth-jwt/blob/master/lib/omniauth/jwt/version.rb |
abramin
force-pushed
the
support-multiple-issuer-secrets
branch
from
e5043c1
to
da7060c
Compare
|
@chrisbarber86 Done, hadn't pushed |
abramin
force-pushed
the
support-multiple-issuer-secrets
branch
from
da7060c
to
408eb2d
Compare
chrisbarber86
approved these changes
Jun 15, 2017
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 allows to send a hash of secrets which will vary depending on issuer.