Skip to main content

Fetch

When using a mobile app with an SDK integration, QR code or push based requests can be fetched on demand, directly from the user device.

Login using push notification

Fetch overview​

Sometimes, authentication requests using push notifications or QR codes can fail to reach the user or go unnoticed. This can leave the user confused and wondering why the authentication process isn't proceeding. Or it may be that your business case does not allow the use of push notifications, but a similarly seamless authentication experience is still desired. For these cases we recommend the use of fetch, which can be used in SDK integrated mobile apps.

We recommend fetch as an authentication method, if the following are true for your business:

  • Your mobile app uses the Nevis Mobile Authentication SDK
  • You want a solution for when authentication requests do not arrive automatically, or are not noticed by the user
  • You do not want to rely on the availability of push services on user devices.

Fetch can be used as an additional feature to the push or QR code authentication methods, or even as its own authentication method, when push notifications are set up to be generated, but not delivered to user authenticator devices.

To use fetch, you need to have QR codes or push notifications set up as authentication method on your instance. QR or push based requests are then generated the same as in normal QR or push authentication scenarios, but fetch offers the possibility for users to request ongoing authentication operations that are present on the server side. This way authentication actions can be triggered and completed on demand.

For more details about using the fetch channel, see Using fetch in the Nevis Mobile Authentication SDK documentation.