/explore
|
You are here 
|
nicolaiarocci.com | ||
| | | | |
www.rasikjain.com
Here are three scenarios for implementing authentication workflows. Internet Applications (Public facing) For internet web applications and APIs, Session based (SessionID cookie) and Token Based (JWT) Authentication can be implemented. Session Based: Implemented for a majority of traditional and stateful web applications. Once the user is authenticated, A Session state is created and stored in an external State server or SQL database. The Session state is identified by a unique SessionID.... |
|
| | | | | ||
| | | | |
aaronparecki.com
An updated version of this post can be found here. |
|
| | | | | ||
| | | | |
fhirblog.com
If you've read the previous posts talking about OAuth2, then (hopefully) it's clear how a user can authorize an application to retrieve their data from some server without needing to expose their login credentials. The Authorization Server is the only component that needs to have the persons username and password (or whatever authorization method is... |
|
| | | | | ||
| | | | |
github.com
Ember Simple Auth extension that is compatible with token-based authentication like JWT. - fenichelar/ember-simple-auth-token |
|
| | | |||
