/explore
|
You are here 
|
blog.christianposta.com | ||
| | | | |
josiahparry.com
|
|
| | | | | ||
| | | | |
mydeveloperplanet.com
|
|
| | | | | This blog provides comprehensive guidance on setting up the OpenID Connect Authorization Code Flow using Keycloak. It explains key concepts, prerequisites, and step-by-step instructions to create realms, clients, and users. The blog emphasizes understanding OAuth2.0 and OIDC, concluding with the implementation of the Authorization Code Flow in applications. | |
| | | | |
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 | |
| | | | |
dusanmitrovic.rs
|
|
| | | Why I no longer use JWT and why you shoud maybe consider doing the same. | ||
