What happens if Silent Authentication is triggered from a web browser instead of the app? What happens if Silent Authentication is triggered from a web browser instead of the app?

What happens if Silent Authentication is triggered from a web browser instead of the app?

Anson

Question

What happens if Silent Authentication is triggered from a web browser instead of the app?

Applies To

  • Verify
  • Silent Auth

Answer

Considerations for Silent Authentication in Web Browsers

When implementing Silent Authentication, it is important to account for the following browser-specific behaviours:
Mobile Web Browser: Silent Auth can be directly implemented within mobile web browser applications.
Desktop Web Browser: Silent Auth is also supported on desktop browsers. However, successful authentication requires the end-user to scan a QR code using a mobile device connected to mobile data.

Fallback Behaviour
If neither of the above implementations is in place, and the Silent Authentication flow fails, Verify will either:

  • Automatically fail over to the next available channel defined in the authentication workflow, or
  • Return an error to the ASP backend, allowing failover to be managed on the server side.

Implementation Guidance
Silent Auth should not be used as the primary authentication channel unless ASP has implemented support for both desktop and mobile browsers. Relying solely on SA without full browser coverage may introduce delays in the authentication flow and require additional front-end logic to handle exceptions.

Additional Information

For more information, see the Silent Authentication API Guide

Articles in this section