You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are implementing a REST server for a bunch of Android and IoS apps and are using KeyCloak 20.x as our authentication/authorization backend. All requests are proxied through our API - the end user has no direct access to KeyCloak. When a user logs in, they receive a JWT indirectly from KeyCloak which enables them to further make requests to our REST API. This all works fine.
Now we want to add WebAuthn to allow our users to register and use their devices' biometric features. I understand how to do this when users have direct access to the KeyCloak console but I'm unclear how this works indirectly through the KeyCloak admin API.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are implementing a REST server for a bunch of Android and IoS apps and are using KeyCloak 20.x as our authentication/authorization backend. All requests are proxied through our API - the end user has no direct access to KeyCloak. When a user logs in, they receive a JWT indirectly from KeyCloak which enables them to further make requests to our REST API. This all works fine.
Now we want to add WebAuthn to allow our users to register and use their devices' biometric features. I understand how to do this when users have direct access to the KeyCloak console but I'm unclear how this works indirectly through the KeyCloak admin API.
Any help would be appreciated...
Gregor
All reactions