spec: Identity/authenticator API consistency analysis#5758
Open
carmenlau wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ref DEV-3630
This document maps how identity and authenticator data is exposed across our API surfaces, identifies naming inconsistencies, and defines a canonical data model as a guideline for future APIs.
Planned change: Add oauth_provider_type and oauth_provider_alias alongside provider_type and alias in the Auth Flow API — additive, non-breaking.
Out of scope for now: Admin GraphQL and Webhook Events both use a raw namespaced claims map. We are keeping them as-is; the canonical model serves as a reference for when they are eventually updated.