Jump to content
Enpass Discussion Forum

Passkeys broken in Chrome


Ivarson

Recommended Posts

All of a sudden, webauthn (passkeys) requests in Chrome are not being redirected and picked up by enpass. 

Chrome 125.0.6422.72

Enpass 6.10.2.986

Android 14/Samsung a54

Passkeys still works in (the few) native Android apps that supports passkeys. 

Edited by Ivarson
Link to comment
Share on other sites

  • Ivarson changed the title to Passkeys broken in Chrome

Enabling the Temporarily unexpire M124 flags flag

  1. Open Chrome, then type chrome://flags into the address bar
  2. In the flags page which opens, tap the search box, then search for M124
  3. Tap Default under Temporarily unexpire M124 flags then tap Enabled.
  4. Tap the Relaunch button that appears at the bottom of your browser

Enabling Android Credential Management for passkeys flag

  1. Open Chrome, then type in chrome://flags into the address bar
  2. In the flags page which opens, tap the search box, then search for passkeys
  3. Tap Default under the Android Credential Management for passkeys flag, then tap Enable for Google Password Manager and 3rd party passkeys
  4. Tap the Relaunch button that appears at the bottom of your browser
  • Thanks 1
Link to comment
Share on other sites

On 5/30/2024 at 8:31 AM, Amandeep Kumar said:

Enabling the Temporarily unexpire M124 flags flag

  1. Open Chrome, then type chrome://flags into the address bar
  2. In the flags page which opens, tap the search box, then search for M124
  3. Tap Default under Temporarily unexpire M124 flags then tap Enabled.
  4. Tap the Relaunch button that appears at the bottom of your browser

Enabling Android Credential Management for passkeys flag

  1. Open Chrome, then type in chrome://flags into the address bar
  2. In the flags page which opens, tap the search box, then search for passkeys
  3. Tap Default under the Android Credential Management for passkeys flag, then tap Enable for Google Password Manager and 3rd party passkeys
  4. Tap the Relaunch button that appears at the bottom of your browser

Workaround confirmed working. Is this something that can be addressed from Enpass side or do we have to wait for Google to sort Chrome out? 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...