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

Define discovery metadata for support of the Transaction Token functionality #95

Open
gffletch opened this issue May 17, 2024 · 1 comment

Comments

@gffletch
Copy link
Collaborator

Should we add to the spec a mechanism for a client to discover if the AS has support for the transaction token profile of the token-exchange endpoint? Or do we need to define a new .well-known location for the Transaction Token Service?

@tulshi
Copy link
Collaborator

tulshi commented Jun 14, 2024

Notes from call on 06-14-24

  • (George) Discovery by an external client may not be useful, but for internal clients, it might be important. We could chain it out of the AS, because we would expect services to know where the AS is.
  • (Atul) Can we do a 401 response with the location of the TTS?
  • (Pieter) Agree that external clients don't need to discover the TTS. Discovery is useful for internal clients. Can we do resource metadata?
  • (George) One way is to add a new URL to the AS metadata. We should discuss this in Vancouver
  • (Atul, Pieter) Can we use OPRM?
  • (Pieter) The flow is going to be different because it assumes OAuth Access tokens

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

No branches or pull requests

2 participants