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.

Sign up for GitHub

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

Jump to bottom

Should all login_hint formats be supported by an implementation? #227

Open

trehman-gsma opened this issue Nov 12, 2024 · 0 comments

Labels

Collaborator

trehman-gsma commented Nov 12, 2024 •

edited

Loading

Problem description
Seeking clarification on the extent of format support that is required within a flow that uses the login_hint parameter.

The Security and Interoperability Profile currently has 3 login_hint formats:

Is it mandatory for an API implementation to support all login_hint formats? For example, a SimSwap implementation may not find value in supporting ipport.
If not mandatory, what is the expected response when an unsupported login_hint is passed in?

Expected action
Clarification in documentation.

The text was updated successfully, but these errors were encountered:

trehman-gsma added the documentation label

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