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

clarify token validation is the RP's responsibility #391

Merged
merged 1 commit into from
Jan 13, 2023

Conversation

kdenhartog
Copy link
Contributor

@kdenhartog kdenhartog commented Jan 11, 2023

closes #318


Preview | Diff

Copy link
Contributor

@achimschloss achimschloss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm unsure if it makes sense to even delve into (validation etc.) this given the FedCM API leaves it open what is passed here, or just name this as an general example. The FedCM token could as well not be an ID token type piece of information, but rather something that resembles an auth code, access token, ....

Keeping it more generic in pointing out that its the RPs role to leverage that token in general in a non FedCM related process makes sense I would think.

@samuelgoto samuelgoto merged commit e346efe into w3c-fedid:main Jan 13, 2023
github-actions bot added a commit that referenced this pull request Jan 13, 2023
SHA: e346efe
Reason: push, by samuelgoto

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@kdenhartog kdenhartog deleted the kdh/issue-318 branch January 15, 2023 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Need to define token validation steps for the RP
4 participants