agent-to-agent token exchange#6220
Open
susanharper-okta wants to merge 7 commits into
Open
Conversation
susanharper-okta
requested review from
barbaravo-okta,
brentschaus-okta,
emikhasyak-okta,
grahamsmith-okta,
ishan-krishna-okta,
janethu-okta and
paulwallace-okta
as code owners
This comment was marked as outdated.
This comment was marked as outdated.
| --data-urlencode "subject_token_type=urn:ietf:params:oauth:token-type:access_token" \ | ||
| --data-urlencode "requested_token_type=urn:ietf:params:oauth:token-type:id-jag" \ | ||
| --data-urlencode "audience=https://{yourOktaDomain}/oauth2/{authServerId}" \ | ||
| --data-urlencode "resource=https://agent2.{yourOktaDomain}" \ |
Contributor
There was a problem hiding this comment.
Suggested change
| --data-urlencode "resource=https://agent2.{yourOktaDomain}" \ |
| @@ -0,0 +1,65 @@ | |||
| In this step, Agent 2 receives the access token (T3) from Agent 1. Agent 2 validates the request by performing another token exchange, exchanging T3 at the org authorization server for an ID-JAG token (T4). Agent 2 also adds itself to the actor chain. The ID-JAG now reflects Agent 2 as the immediate actor, with Agent 1 in the delegated chain, and the original service client as the origin. | |||
Contributor
There was a problem hiding this comment.
Suggested change
| In this step, Agent 2 receives the access token (T3) from Agent 1. Agent 2 validates the request by performing another token exchange, exchanging T3 at the org authorization server for an ID-JAG token (T4). Agent 2 also adds itself to the actor chain. The ID-JAG now reflects Agent 2 as the immediate actor, with Agent 1 in the delegated chain, and the original service client as the origin. | |
| In this step, Agent 2 receives the access token (T3) from Agent 1. Agent 2 uses T3 to perform another token exchange, exchanging T3 at the org authorization server for an ID-JAG token (T4). Agent 2 also adds itself to the actor chain. The ID-JAG now reflects Agent 2 as the immediate actor, with Agent 1 in the delegated chain, and the original service client as the origin. |
or something along those lines, it's not 'validating' the request
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description:
Resolves:
Netlify Preview Link: