Explore >> Select a destination
|
You are here 
|
marcolabarile.me | ||
| | | | |
openid.net
|
|
| | | | | What is OpenID Connect OpenID Connect is an interoperable authentication protocol based on the OAuth 2.0 framework of specifications (IETF RFC 6749 and 6750). It simplifies the way to verify the identity of users based on the authentication performed by an Authorization Server and to obtain user profile information in an interoperable and REST-like manner.OpenID | |
| | | | |
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.... | |
| | | | |
www.criipto.com
|
|
| | | | | JWT claims contain details about authenticated users within OpenID Connect. See real examples of JWTs. Learn how Criipto Verify can help you easily issue JWTs. | |
| | | | |
svrooij.io
|
|
| | | I'm super enthusiastic about managed identities, because it allows you to deploy your application without having to worry about credentials. Federated credentials are a way to accomplish the same for none Azure resources. You can use federated credentials to authenticate several tasks inside Github Actions, and thus securely deploy your app to Azure without the need of a secret configured in GitHub. As the regular readers might expect this post will explain how federated credentials actually work inside GitHub Actions, a deep dive into the techniques that are actually driving this feature. Get a federation token from GitHub | ||
