search

deansaxe / wimse-token-exchange-and-translation

Other
4 stars 3 forks source link

Develop Use Cases #2

Closed dhs-aws closed 5 months ago

dhs-aws commented 7 months ago

Develop the use cases language for token exchange.

dhs-aws commented 7 months ago

@adeinega in slack shared the following:

I don't how this would be useful for anyone from you... but these use cases just from the top of my head... after some research

workloadA doesn't have any "incoming" token but has its own service account token and wants to obtain an access token in order to talk to workloadB

workloadA has both an "incoming" Bearer token and its own service account token and wants to obtain an access token in order to talk to workloadB

workloadA has both an "incoming" DPoP token and its own service account token and wants to obtain an access token in order to talk to workloadB

gffletch commented 7 months ago

We may want to consider more than just hop-to-hop protections and think about a transaction as a unit regardless of how many workloads are involved. This doesn't negate the need for hop-to-hop protections or use cases.

The use cases listed apply to transactions as well as individual messages.

gffletch commented 7 months ago

For the 3rd use case, we should probably consider it to cover any sender constrained token regardless of method (DPoP, HTTP Signatures, mTLS bound tokens, etc).

dhs-aws commented 5 months ago

Closing, as this work is now happening at https://github.com/yaroslavros/wimse-tokentranslation-requirements.