Repository navigation
Replies: 4 comments 2 replies
|
Just a quick follow-up. Here is a demo showing the user experience with the proposed standard OAuth 2.0 First-Party Applications. Sign.In.with.Passkeys.mp4A high-level overview of the required customizations I developed for the demo:
In the demo, Keycloak is configured with an extension and a new flow that supports passkeys using a new authenticator. Both users have already registered their passkeys in Keycloak. [1] https://datatracker.ietf.org/doc/draft-parecki-oauth-first-party-apps/ |
|
I like the idea and it is easy to follow. Where do we get the extension? I want to implement this. |
|
The document has been adopted as an Internet Draft: https://www.ietf.org/archive/id/draft-ietf-oauth-first-party-apps-00.html |
|
See the related discussion on refactoring authenticators to support an API-based authentication approach #36924 |
|
@embesozzi , is there any updated regarding native OAuth 2 for mobile |
|
curious as well |
Uh oh!
There was an error while loading. Please reload this page.
As an IAM Architect based on my experience, the user experience of opening a browser in a mobile application for the federation process is not optimal. Therefore, offering more control of the authentication process to native applications is going to enhance the login experience.
As a reference, we have the DRAFT OAuth 2.0 for First-Party Native Applications, which provides some high-level guidelines:
Other vendors such ForgeRock or now Microsoft Entra, are offering similar user experiences:
ForgeRock implemented it in a custom way; Microsoft's implementation is currently unknown.
Concerns:
All reactions