-
Notifications
You must be signed in to change notification settings - Fork 142
docs: mobile token guides #422
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
Conversation
|
Awaiting the other PR and rebase before review. |
9948bc2 to
9c666b7
Compare
|
Rebased. |
|
Added small fixes. |
MGatner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is rather opinionated but I like it as a practical example of a real and common scenario in webdev.
|
Is this explanation comprehensive, what about tablets, smart watches and ...? |
|
Thanks for the additional work here @kenjis. @MGatner The code is mostly taken from the existing login method. I still want to look into how we do SPA authentication and provide a guide for that. I feel that might need a new method added, but unsure yet. If we use the session filter for SPAs I think we need to provide a way for an API to get a CSRF token. If we go with tokens for SPA's there needs to be some careful consideration there as that would leave the token exposed to anyone who wanted to look. So would probably have to put the token in a cookie or something to hide it? Unsure at the moment. |
Adds a guide describing one way of using Access Tokens to authenticate a mobile application.
Requires #417 to be merged first.