May 26, 20241 yr 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 May 26, 20241 yr by Ivarson
May 30, 20241 yr Enabling the Temporarily unexpire M124 flags flag Open Chrome, then type chrome://flags into the address bar In the flags page which opens, tap the search box, then search for M124 Tap Default under Temporarily unexpire M124 flags then tap Enabled. Tap the Relaunch button that appears at the bottom of your browser Enabling Android Credential Management for passkeys flag Open Chrome, then type in chrome://flags into the address bar In the flags page which opens, tap the search box, then search for passkeys Tap Default under the Android Credential Management for passkeys flag, then tap Enable for Google Password Manager and 3rd party passkeys Tap the Relaunch button that appears at the bottom of your browser
May 31, 20241 yr Author On 5/30/2024 at 8:31 AM, Amandeep Kumar said: Enabling the Temporarily unexpire M124 flags flag Open Chrome, then type chrome://flags into the address bar In the flags page which opens, tap the search box, then search for M124 Tap Default under Temporarily unexpire M124 flags then tap Enabled. Tap the Relaunch button that appears at the bottom of your browser Enabling Android Credential Management for passkeys flag Open Chrome, then type in chrome://flags into the address bar In the flags page which opens, tap the search box, then search for passkeys Tap Default under the Android Credential Management for passkeys flag, then tap Enable for Google Password Manager and 3rd party passkeys 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?
Create an account or sign in to comment