Skip to main content

Hi everyone, 

I'm experiencing an issue in a Salesforce Sandbox when trying to access: 

Setup → App Manager → View App → Manage Consumer Details 

 

When I click Manage Consumer Details, Salesforce opens the Verify Your Identity dialog, but the authentication immediately fails with the following error: 

There are no built-in authenticators available to this browser. 

Verify Your Identity fails with 'There are no built-in authenticators available to this browser' when opening Manage Consumer Details

 

Environment:

  • Salesforce Sandbox
  • Google Chrome

 

What I've already verified:

  • Touch ID is correctly registered as my authentication method.
  • Touch ID works correctly for other authentication requests.

 

From what I've investigated, it appears that the Verify Your Identity dialog may be rendered inside an internal iframe, and the browser is therefore unable to access the registered authenticator. 

 

Has anyone encountered this issue before? Is this a known Salesforce or Chrome limitation, or is there a configuration or workaround that resolves it? 

 

Any help or suggestions would be greatly appreciated. 

 

Thank you! 

 

 

 

#Security

14 个回答
  1. 10月1日 13:39

    A work colleague has shared another alternative solution with me. 

     

    In Setup → Session Settings → Session Security Levels, move Passwordless Login via Passkeys to the High Assurance category. 

     

    Why does this work? 

     

    Salesforce allows us to define which authentication methods establish a High Assurance session. By classifying Passwordless Login via Passkeys as High Assurance, users who log in with a passkey start their session at that security level. 

     

    As a result, when they perform sensitive operations that require High Assurance, Salesforce doesn’t prompt them to verify their identity again during the same session: 

     

    If you require high assurance for sensitive operations and users have a high-assurance session after logging in, they aren’t prompted to verify their identity in the same session.

     

    The list of affected operations and the corresponding configuration can be found here: Require High-Assurance Session Security for Sensitive Operations

0/9000