---
title: "Alternate step: configuring your proxy"
slug: "dpo-configure-fido2-alternate-step-configuring-your-proxy"
updated: 2026-10-27T20:13:12Z
published: 2026-10-27T20:13:12Z
canonical: "docs.onespan.com/dpo-configure-fido2-alternate-step-configuring-your-proxy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Alternate step: configuring your proxy

If you replace the DigipassONE API Server with your own proxy, you need to work around a limitation with how Android handles native FIDO2. Currently, FIDO2 on Android requires a non-empty allowCredentials during authentication, which means you need to supply the username of the person requesting authentication. See the [W3 Web Authentication documentation](https://www.w3.org/TR/webauthn/#dom-publickeycredentialrequestoptions-allowcredentials) for an explanation of allowCredentials.

A recommended solution is to pass the username when you initiate authentication. When you call the DigipassONE Server’s INIT_AUTH or INIT_ADAPTIVE operations, send the user name in the payload using the attribute userName. The user must have existing registrations. The Auth Server automatically populates allowCredentials with the public key credentials for all the user’s registered authenticators. For more information about INIT_AUTH and INIT_ADAPTIVE operations, see [Adaptive authentication](/dpoa/docs/s3suite94-adaptive-authentication-1) in the reference to the REST API.

Formerly known as Digipass S3.

Formerly known as Digipass S3 Server.