Troubleshooting: "Unable to Select Registration Method" for SMS, Voice, or Push

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All
     
     

    Overview

    Registering for a multi-factor authentication method (SMS, Voice, or Push) fails with Unable to Select Registration Method. This can have more than one cause:

    • See Cause 1 - The server's time is incorrect.
    • See Cause 2 - The wrong certificate is selected for the realm.
    • See Cause 3 - The selected certificate is missing permissions.

     

    In this article


     

    Cause 1: Incorrect Server Time

    The server's system time (or time zone) is incorrect.

     

    Resolution 1:

    Check the server's time to confirm both the time and time zone are correct.

     


     

    Cause 2: Incorrect Certificate Selected

    The certificate selected for the realm is not the correct one.

     

    Resolution 2:

    On the realm's System Info tab, verify the certificate selected under Client Cert Serial Nbr is correct.

     


     

    Cause 3: Certificate Permissions Missing

    The selected certificate is missing the permissions it needs.

     

    Resolution 3:

    In Certificate Manager, confirm the certificate has Network Service Read permission.

     

    Special Considerations

    Also confirm the URLs under SecureAuth Cloud Services on the System Info tab are correct:

    The SecureAuth Cloud Services section of the System Info tab, showing the expected Certificate URL and the Telephony, SMS, Push, Link-to-Accept, Phone Fraud Service, Geo-Location, SecureAuth Threat Service, and Titan URLs all pointing to us-services.secureauth.com.

    If you need to open a support ticket, hover over the red Unable to Select Registration Method text and take a screenshot of the full error — this will help whoever picks up the ticket.


     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.