/explore
|
You are here 
|
www.keycloak.org | ||
| | | | |
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 | |
| | | | |
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. | |
| | | | |
blog.christianposta.com
|
|
| | | | | In the previous blog, we dug into dynamically registering OAuth clients leveraging SPIFFE and SPIRE. We used SPIRE to issue software statements in the SPIFFE JWT SVID that Keycloak can trust as part of Dynamic Client Registration (RFC 7591). Once we have an OAuth client, we will want to continue to use SPIFFE to authenticate to our Authorization Server. This eliminates the need for a long-lived "client secret" which is common for Confidential OAuth. This means we can use the Agent or MCP client's identity (based on SPIFFE) for authorization flows based on OAuth. We dig into that in this blog. | |
| | | | |
gist.github.com
|
|
| | | Script which access the Jamf Pro API and uses provided API client authentication to obtain and verify bearer tokens - jamf_pro_api_client_token_management.sh | ||
