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

oauth2 implicit flow should allow custom protocols #180

Closed
aeneasr opened this issue Jul 28, 2016 · 5 comments
Closed

oauth2 implicit flow should allow custom protocols #180

aeneasr opened this issue Jul 28, 2016 · 5 comments
Assignees
Labels
bug Something is not working. upstream Issue is caused by an upstream dependency.
Milestone

Comments

@aeneasr
Copy link
Member

aeneasr commented Jul 28, 2016

But first, check the spec for further information on this.

@aeneasr aeneasr added the bug Something is not working. label Jul 28, 2016
@aeneasr aeneasr added this to the 0.2.0 milestone Jul 28, 2016
@aeneasr aeneasr self-assigned this Jul 28, 2016
@boyvinall
Copy link
Contributor

As per gitter, take a look at https://tools.ietf.org/html/draft-ietf-oauth-native-apps-03

@boyvinall
Copy link
Contributor

BTW - for my purposes, I'm looking at using the implicit flow, but I think this can also affect the authorisation code flow. Perhaps this makes the implementation easier?

@aeneasr
Copy link
Member Author

aeneasr commented Jul 29, 2016

No, the implicit flow is the only one where you can use custom uri schemes. Using this with the authorization code will leak the token to anyone who is listening. Seriously anyone, including me. ;)

@aeneasr
Copy link
Member Author

aeneasr commented Aug 1, 2016

upstream ory/fosite#60

@aeneasr aeneasr added the upstream Issue is caused by an upstream dependency. label Aug 1, 2016
@aeneasr
Copy link
Member Author

aeneasr commented Aug 1, 2016

this is justified by https://tools.ietf.org/html/rfc6819#section-4.4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working. upstream Issue is caused by an upstream dependency.
Projects
None yet
Development

No branches or pull requests

2 participants