--- title: "User ID and domain resolution" slug: "oas-ag-user-id-and-domain-resolution-3-28" updated: 2025-07-07T13:31:16Z published: 2025-07-07T13:31:16Z canonical: "docs.onespan.com/oas-ag-user-id-and-domain-resolution-3-28" --- > ## 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. # User ID and domain resolution To allow users to authenticate with user names in different formats, OneSpan Authentication Server identifies user accounts via the user ID and domain. [Table: User name resolution in OneSpan Authentication Server](/sec/docs/oas-ag-user-id-and-domain-resolution-3-28#Tab_UsernameResolutionInOAS) provides a comparison overview of the user name resolution methods. For a description of each user name resolution method and user account identification, see : - [Windows user name resolution](/sec/docs/oas-ag-windows-user-name-resolution-3-28) - [Active Directory user name resolution](/sec/docs/oas-ag-active-directory-user-name-resolution-3-28) - [Simple user name resolution](/sec/docs/oas-ag-simple-user-name-resolution-3-28) | Feature | User Name Resolution Type | | --- | --- | | | Windows | Active Directory | Simple | | User can authenticate with UPN and SAM account name, even if different. | ✓ | ✓ | | | User can authenticate with UPN that includes alternative UPN domain suffixes. | ✓ | ✓ | ✓ | | Supported where OneSpan Authentication Server is installed on a Windows machine which is a member server of the Windows domain. | ✓ | ✓ | ✓ | | Supported where the machine on which OneSpan Authentication Server is installed is either not a member server of the Windows domain or running a Linux operating system. | | ✓ | ✓ | | Support for Active Directory users. | ✓ | ✓ | ✓ | | Support for Active Directory or Global Catalog as back-end server. | ✓ | ✓ | ✓ | | Resolves user name to SAM account name and FQDN. | ✓ | ✓ | | | Requires additional configuration of back-end directory information | | ✓ | ✓ | ![Name resolution with ODBC data store](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Process.ODBC.png?sv=2026-02-06&spr=https&st=2026-11-16T15%3A30%3A13Z&se=2026-11-16T16%3A30%3A13Z&sr=b&sp=r&sig=dKv%2Fn95p%2BZLPNfIw1z5%2BLLHWBv6l8r1lA9Q4tARpP3o%3D) Figure: Name resolution ![Name resolution with ODBC data store and Active Directory back-end server](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Process.ODBC_with_AD_BE.png?sv=2026-02-06&spr=https&st=2026-11-16T15%3A30%3A13Z&se=2026-11-16T16%3A30%3A13Z&sr=b&sp=r&sig=d%2FrB9UDl1KSaHPECX4%2BRvOlZIXFB2gGlYOENtbSGDXg%3D) Figure: Name resolution with Active Directory back-end server