Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment models, Transaction Tokens and Discovery #34

Open
gffletch opened this issue Nov 4, 2024 · 0 comments
Open

Deployment models, Transaction Tokens and Discovery #34

gffletch opened this issue Nov 4, 2024 · 0 comments

Comments

@gffletch
Copy link
Collaborator

gffletch commented Nov 4, 2024

Another topic discussed in the IETF 121 OAuth meetings is the discovery of the token issuing service (Transaction Token Service) and whether different deployment models affect discovery or token issuance in any way.

Three possible deployment models (NOT exhaustive):

  1. Embedded in an Authorization Server, or API GW
  2. Single HA Transaction Token Service
  3. Distributed (geographically) Transaction Token Service

How does a client of the Transaction Token Service endpoint know where to go? Is this out-of-scope for any specifications and the security concern of a client sending a transaction token request to an incorrect (unauthorized) endpoint should just be clearly called out in the security considerations.

The thinking from the OAuth meeting is that this topic should be discussed in WIMSE as well.

OAuth Transaction Tokens github repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant