/explore
|
You are here 
|
cloudentity.com | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
www.ayush.nz
[AI summary] This article provides a technical assessment of JSON Web Tokens (JWT) as a compact, self-contained mechanism for secure information exchange and authentication in APIs. |
|
| | | | | ||
| | | | |
sandrino.dev
Insomnia Core is lightweight and simple tool for testing your REST, GraphQL and gRPC services. With native support for OAuth 2.0 it also comes in handy when you're using Auth0 to secure these services. |
|
| | | | | ||
| | | | |
www.mathieupassenaud.fr
[AI summary] The article argues for securing user accounts by minimizing the number of passwords stored and utilizing robust authentication protocols like OAuth, OpenID, and WebAuthn provided by major services, suggesting password managers and hardware keys as effective alternatives. |
|
| | | |||
