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

[Q] How does authentication work internally #45

Open
Cilenco opened this issue Mar 21, 2017 · 0 comments
Open

[Q] How does authentication work internally #45

Cilenco opened this issue Mar 21, 2017 · 0 comments

Comments

@Cilenco
Copy link

Cilenco commented Mar 21, 2017

I would like to use this to authenticate my slim REST API but I'm a bit confused right now.

Don't I have to add an accessToken or something like this to my response from login? If a user calls login and after that tries to get some other data how does the system know that the user is authenticated and allowed to call the method? Of course then I have to test if the accessToken is valid in each route but it seams that I do not have to do all this by myself.

The only way I could think of is that the authentication is IP based but I see some problems with that so that could not be the answer, right?

Also how long is the authentication valid? Can I set a experation date somewhere?

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