wip: configure provider with pre-signed jwt #1237
Draft
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 is a proof-of-concept PR following okta/okta-sdk-golang#319 that demonstrates the ability to configure the provider with a pre-signed JWT. I've left some context in that PR that I will duplicate here:
I decided to split up the work into two PRs to show the most obvious way that this would be implemented, but I am open to changes that keep this localized to the provider if that makes more sense to you all.
As it is now, the changes are pretty superficial - the provider simply passes the JWT through to the SDK, which then uses it to exchange for an access token.
Per a conversation we had yesterday, I've attached a rough example of how we (Etsy) plan on calling the provider with a
jwt
argument.