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
Change spec name to focus on Authz #67
Comments
PieterKas
changed the title
Explain how spec is used for identity chaining
Change spec name to focus on Authz
Dec 7, 2023
My suggestion: "OAuth Cross-Domain Authorization Framework" It focuses on the cross-domain authorization aspect, and also makes it clear this is a framework that will need to be profiled to be implemented. |
Some discussion has happened elsewhere (email and webex) with apparent consensus forming around “OAuth Identity and Authorization Chaining Across Domains” as the proposed name. |
Merged
bc-pi
added a commit
that referenced
this issue
Feb 16, 2024
* update draft name closes #67 * Update draft-ietf-oauth-identity-chaining.md Co-authored-by: Brian Campbell <71398439+bc-pi@users.noreply.github.com> * Incorporate Arndt's suggestion into the Introduction --------- Co-authored-by: Brian Campbell <71398439+bc-pi@users.noreply.github.com> Co-authored-by: Brian Campbell <bcampbell@pingidentity.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Change name to focus on authorization (e.g. cross-domain authorization). Purpose of renaming is to create clarity that this is a mechanism for cross domain authz and that identity flows with the authorization. Add text to make it clear how identity chaining is achieved as a result of using this spec (the idea that the identity is following the authorization).
The text was updated successfully, but these errors were encountered: