|
You are here |
clymb3r.wordpress.com | ||
| | | | |
csandker.io
|
|
| | | | | Compared to Linux, the Window's authorization process is quite complex and quite a few actors and objects are involved in this process. As a result, there a lot of terms and acronyms that must be known in order to understand and follow up on the topic. To get an idea of what is covered in this guide take a look on this overview of terms and acronyms... | |
| | | | |
zer1t0.gitlab.io
|
|
| | | | | ||
| | | | |
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.... | |
| | | | |
msfjarvis.dev
|
|
| | | GitHub Actions paired with GitHub Pages provides an excellent CD platform for a status page. Here's how I used it to create mine. | ||