This repository has been archived by the owner on Mar 14, 2022. It is now read-only.
Encode the issuer in a JWT #392
Open
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
jcoyne
force-pushed
the
applicationHeader
branch
from
8734d96
to
d579231
Compare
aaron-collier
suggested changes
Apr 12, 2018
docs/tokens.md
Outdated
| *note* the secret must be the same secret that TACO is configured with | ||
| (in the `TACO_SECRET_KEY` variable) | ||
| ``` | ||
| jwt encode --secret superSeckeret --iss hydrus.stanford.edu --subject "lmcrae@stanford.edu" |
There was a problem hiding this comment.
This command appears to be invalid --subject should be --sub, I get an error with --subject
|
I'm also just getting |
jcoyne
force-pushed
the
applicationHeader
branch
from
d579231
to
9bfd64a
Compare
aaron-collier
approved these changes
Apr 13, 2018
jcoyne
force-pushed
the
applicationHeader
branch
from
9bfd64a
to
3c8a16d
Compare
This allows us to track which upstream application is using the TACO service. Presenlty, go-swagger gives us no options for making sure that two authorization tokens are passed, so by using JWT, we encode the subject (user identification) and issuer (service) in a single token.
jcoyne
force-pushed
the
applicationHeader
branch
from
3c8a16d
to
2e5068f
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 us to track which upstream application is using the TACO
service.
Presenlty, go-swagger gives us no options for making sure that two
authorization tokens are passed, so by using JWT, we encode the subject
(user identification) and issuer (service) in a single token.
Fixes #375