You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Spec not clear as to which auth flows are supported #72
Originally submitted by dgtonge (Dave Tonge) on 2017-04-26
Actually I think its a bit clearer now:
shall require the response_type values code id_token or code id_token token;
shall return ID Token as a detached signature to the authorization response;
shall include state hash, s_hash, in the ID Token to protect the state value;
Activity
bitbucket-import-issues commentedon Jul 2, 2026
Since we agreed that we need to have both the request and response signed, only the viable flow is the Hybrid Flow.
bitbucket-import-issues commentedon Jul 2, 2026
We discussed on the call that I will make a pull request with a clarification
bitbucket-import-issues commentedon Jul 2, 2026
Just waiting for a pull request.
bitbucket-import-issues commentedon Jul 2, 2026
Please provide the location where this should be fixed or updated.
bitbucket-import-issues commentedon Jul 2, 2026
Actually I think its a bit clearer now:
I think we can close this.
bitbucket-import-issues commentedon Jul 2, 2026
Going to close this.