Explore >> Select a destination
|
You are here 
|
minhajuddin.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.... | |
| | | | |
nobackend.org
|
|
| | | | | ||
| | | | |
meka.rs
|
|
| | | | | Modern WEB applications | |
| | | | |
davquar.it
|
|
| | | A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. | ||
