Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Implement built-in delegation/impersonation support (RFC8693)

See original GitHub issue

The OAuth 2.0 token exchange specification - originally known as “OAuth 2.0 Token Exchange: an STS for the REST of us” - was finally standardized last year.

Note: OpenIddict 3.0 already supports the requirements brought by this specification (like being able to set multiple audience or resource parameters, which was explicitly disallowed in the original OAuth 2.0 specification), as they were already part of ASOS 2.0 and OpenIddict 2.0.

RFC: https://tools.ietf.org/html/rfc8693

Issue Analytics

State:
Created 2 years ago
Reactions:8
Comments:6 (3 by maintainers)

Top GitHub Comments

4reactions

ahanoffcommented, May 25, 2021

hi @kevinchalet, could you please explain how far this feature from completion and what is required to complete it? I most likely need this in my project soon, would be great if it supported out of the box in this awesome project

2reactions

mzroscommented, Jul 28, 2023

any news on this?

Top Results From Across the Web

RFC 8693 - OAuth 2.0 Token Exchange

Delegation vs. Impersonation Semantics. One common use case for an STS (as alluded to in the previous section) is to allow a resource...

Impersonation Approaches with OAuth and OpenID Connect

There are different approaches for implementing impersonation and delegation with the Curity Identity Server: Exchanging Tokens; User Assertion Grant ...

Token Exchange

The OAuth Token Exchange specification (RFC 8693) describes a general purpose ... Common use cases are creating tokens for impersonation and delegation ......

Implementing Impersonation | Curity Identity Server

Learn how to implement an Impersonation Flow. ... Implementing Impersonation. The actor attribute will end up in the act claim as specified in...

OAuth 2.0 Token Exchange

The claim, as explained in RFC 8693, is a JSON object that specifies the party or parties allowed to act on behalf of...