---
title: "Authenticating with the User Name"
slug: "s3suite94-authenticating-with-the-user-name"
updated: 2026-10-27T18:42:16Z
published: 2026-10-27T18:42:16Z
canonical: "docs.onespan.com/s3suite94-authenticating-with-the-user-name"
---

> ## 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.

# Authenticating with the User Name

Accept the default value of Enabled for the field **Authenticate with user name**. Do this regardless of the client your apps are implemented on. In particular, this fixes a limitation with how the old Android FIDO2 API handles native FIDO2 by enabling an authentication flow in which the username is known up front.

If your organization wants to hide the user's FIDO2 registrations, activate the API Server's Privacy Credential Generator plugin.

You can perform both these actions using the Admin Console.

1. Login to the new tenant. Navigate to **Configuration > API Server > Session Plugins**.

![Session plugins overview showing enabled and disabled authentication features and settings.](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Screenshot 2025-12-02 at 10.21.43 AM.jpg?sv=2026-02-06&spr=https&st=2026-10-29T03%3A28%3A12Z&se=2026-10-29T04%3A28%3A12Z&sr=c&sp=r&sig=HQ82wZGT4IG8h1ANWgxWZZJRiF26zCOJsJBx0mfrYJk%3D)

1. Click the value for **Authentication with the user name** and select Enabled.
2. To hide the user's FIDO registrations, find the **Privacy Credential Generator** label and click its **Modify** button. Click the **Generate** button and confirm that you want to generate a new configuration object. Click **Activate** if the plugin is deactivated. You can view the current configuration by clicking the **Privacy** **Credential Generator** label.

The old FIDO2 API on Android requires a non-empty allowCredentials during authentication, which is fixed by enabling **Authenticate with user name** or assigning true to auth_with_username. See the [W3 Web Authentication documentation](https://www.w3.org/TR/webauthn/#dom-publickeycredentialrequestoptions-allowcredentials) for an explanation of allowCredentials. Currently the App SDK is configured to use the newer Credential Manager API by default, which doesn’t have that limitation.