Picture of the token-exchange flow in the documentation

closes #39881

Signed-off-by: mposolda <mposolda@gmail.com>
Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
Co-authored-by: Alexander Schwartz <alexander.schwartz@ibm.com>
This commit is contained in:
Marek Posolda 2025-10-29 11:38:37 +01:00 committed by GitHub
parent 3cf0989498
commit 5693899246
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 7 additions and 0 deletions

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 224 KiB

View File

@ -54,6 +54,9 @@ _subject token_ and exchange it for another token _requested token_.
. The _requested token_ is returned to `requester-client`. This token can now be sent to the `target-client`.
. The `target-client` can fulfill the request and return the response to the `requester-client`. The `requester-client` can then follow and return the response to the request from step 2.
.Token Exchange Example Flow
image::token-exchange-example-flow.dio.svg[Token Exchange Example Flow]
Many other use-cases exist for token exchange, but the preceding example is the most typical.
==== Example token exchange request