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

Is response type "id_token" and response mode "form_post" a sane default? #4

Open
tanguilp opened this issue May 31, 2020 · 0 comments

Comments

@tanguilp
Copy link
Owner

When used simply for authentication, receiving and validating an ID token is sufficient to open an authenticated session at the RP, hence the current default in v0.1.0:

  • response type "id_token" (implicit flow) and response mode "form_post" if the OP supports both
  • authorization code flow otherwise

An intercepted ID token could be replayed (if JTIRegister is not used to prevent it) but how could an ID token be intercepted in such a case?

A common scenario is when the user has installed a malicious extension. However, browser extensions can access all cookies and replaying an ID token wouldn't have an interest for the attacker already in possession of a stolen authentication cookie, at the RP or at the OP.

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

No branches or pull requests

1 participant