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

Implicit Flow #103

Open
VeftSkil3 opened this issue Nov 18, 2014 · 0 comments
Open

Implicit Flow #103

VeftSkil3 opened this issue Nov 18, 2014 · 0 comments

Comments

@VeftSkil3
Copy link
Contributor

Er þetta rétt og góð skýring á af hverju verið er að nota Implicit Flow?
http://stackoverflow.com/questions/13387698/why-is-there-an-authorization-code-flow-in-oauth2-when-implicit-flow-works-s
The implicit flow is only possible in a browser environment because of security reasons:
You want to allow developers to use non-HTTPS redirect URI because not all developers have an SSL enabled server and if they do it's not always properly configured.
You don't want hackers to be able to steal access/refresh tokens by intercepting requests.
In the implicit flow the access token is passed as a hash fragment. Browsers will pass the hash fragment directly to the destination webpage/the redirect URI which is the client's webpage so you have to read the hash fragment using Javascript. Hash fragment cannot be intercepted by intermediary servers/routers.

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