--- title: "AuthX Secure - Windows V3.0.0" slug: "windows-v3" updated: 2026-01-13T07:39:06Z published: 2026-01-13T07:39:06Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.authx.com/llms.txt > Use this file to discover all available pages before exploring further. # AuthX Secure - Windows V3.0.0 > [!NOTE] > Release Date : January 31st 2026 ## **Overview** AuthX Secure V3 introduces a new generation of policy-based authentication for Windows agents. Unlike previous versions that relied on workflows configured within application settings, this release is governed by the **new Security Policy framework**, where **Rules, Workflows, and Networks** are centrally managed in the AuthX Admin Portal. User login behavior on Windows systems is determined entirely by the policy assigned to the Windows application. ## **Key Highlights of AuthX Secure V3** - **Centralized, policy-driven authentication** using the new Security Policy framework` ` Enables consistent and centrally managed authentication behavior across all Windows devices. - **Adaptive authentication with dynamic workflow selection**` ` Adjusts authentication requirements in real time based on user context, login mode, and network conditions. - **Visual Push authentication (new)**` ` Provides a more intuitive and secure approval experience for users during authentication. - **PIN enrollment directly from the login screen**` ` Allows users to self-enroll PINs without administrator involvement, reducing onboarding effort. - **Enhanced login screen user experience (UI improvements)**` ` Introduces user tiles based on previous sessions, a right-aligned unified authentication panel, language selection on the login screen, manual username entry to load registered authentication factors, and direct user switching in Single Mode. - **Windows Admin “Run As” authentication using AuthX**` ` Secures administrative elevation by enforcing AuthX authentication before privileged access is granted. - **Multi-****RFID****support with automated badge replacement**` ` Enables users to authenticate using multiple badges while simplifying badge lifecycle management. - **Application launch and termination scripts**` ` Automatically launches or closes applications during session start and end for better workflow control. - **Hot key support for Windows and web applications**` ` Improves user efficiency by allowing quick access to applications through configurable shortcuts. - **Display of logged-in user tiles on the login screen**` ` Simplifies user selection and authentication in shared and multi-user environments. - **Configurable display name formats on the login screen**` ` Enhances usability by presenting user identities in a clear and recognizable format. - **Simplified multi-domain configuration**` ` Eliminates agent-side domain configuration by managing all domains centrally in the Admin Portal. - **Multi-language support**` ` Allows users to authenticate in their preferred language, improving accessibility and adoption. - **Automatic light and dark theme support**` ` Adapts seamlessly to system theme settings for a consistent and comfortable user experience. ## **Adaptive Authentication in AuthX Secure V3** AuthX Secure V3 implements **adaptive authentication** through a **policy-driven decision model** that dynamically determines authentication requirements at runtime based on contextual inputs. Unlike earlier versions where authentication workflows were statically configured and directly associated with the Windows application, AuthX Secure V3 evaluates authentication requirements **for every login attempt** using the **new Security Policy framework**. *How Adaptive Authentication Works* During each user login attempt, AuthX Secure V3 follows the steps outlined below: 1. **Policy Evaluation** ` ` Each Windows application is associated with a Security Policy configured in the AuthX Admin Portal. This policy defines the authentication behavior using **rules, workflows, and network conditions**. 1. **Context Collection** ` ` At runtime, AuthX evaluates contextual information related to the login attempt, including: - User identity and account status - Login mode (Single, Shared, Workstation Lock, Delegated) - Network context (trusted or untrusted network) - Authentication factors available to the user 1. **Rule Matching** ` ` Based on the evaluated context, the applicable rule within the policy is identified. 1. **Dynamic Workflow Selection** ` ` The workflow associated with the matched rule is dynamically selected. This determines: - The authentication factors required - The number of authentication levels - The sequence of authentication factors 1. **Authentication Execution** ` ` The user is prompted only for the authentication factors defined by the selected workflow. ` ` The authentication flow can vary for the same user depending on contextual conditions such as network location or login scenario. *Key Characteristics of Adaptive Authentication* - Authentication workflows are **not statically bound** to the Windows application. - Authentication requirements **adapt dynamically** based on policy evaluation. - A single Windows application can support **multiple authentication flows** using one policy. - Security posture changes can be enforced centrally without redeploying or reconfiguring the Windows agent. **Example** - A user logging in from a **trusted corporate network** may be required to authenticate using **RFID****only**. - The same user logging in from an **untrusted network** may be required to complete **RFID****plus Push or PIN** authentication. - These variations are enforced entirely through **Security Policy rules**, without modifying the Windows agent configuration. --- ## **Authentication Factors Supported in AuthX Secure V3** - RFID - Fingerprint - Face - Face Push - Push Notification - Passcode - SMS - Call - Remote Lock (Single mode) - PIN - Visual Push - Offline QR code --- **Windows Application** in the AuthX Admin Portal The following options are **no longer supported** in AuthX Secure V3: - **User Groups** - **Authentication Workflow** These configurations are now **driven exclusively by the new Security Policy**. ` ` Only the **new version of the Security Policy** is supported with AuthX Secure V3. --- ## **Additional Features** ### ***Display Name Format on Login Screen*** AuthX Secure V3 supports configurable display formats for usernames shown on the login screen. Supported formats include: - Initials only - Full name - First name with last initial - Last name with first initial This setting applies to **Single Mode, Shared Mode, Workstation Lock Mode, and Delegated Mode**. ### ***Allow PIN Enrollment from Login Screen*** - Enables users to enroll a PIN directly from the AuthX login screen. - Functions similarly to RFID enrollment. - Supported across all login modes. ### ***Login Screen UI Enhancements*** AuthX Secure V3 includes multiple UI refinements to improve clarity, usability, and consistency across login scenarios. - **User Tile Display Based on Previous Sessions**` ` The login screen displays user tiles based on previously logged-in users, enabling faster user selection in shared and multi-user environments. - **Right-Aligned Authentication Panel**` ` The authentication panel is positioned on the right side of the screen, ensuring background images remain visible and unobstructed. - **Consolidated Authentication Information Panel**` ` Authentication factors, network logon options, and login screen display text are presented within a single panel on the right side of the screen. - **Language Selection on Login Screen**` ` Users can select their preferred language directly from the login page using the language dropdown. - **Manual Username Entry to Load Registered Authentication Factors**` ` Users can enter their username on the login screen to load the authentication factors registered for that user. - **User Switch Option in Single Mode**` ` In Single Mode, users can switch to a different user directly from the login screen. ### ***Application Launch and Termination Capabilities*** **Start-up and Termination Scripts** Administrators can define scripts that execute automatically during session lifecycle events: - **Start-up Scripts** – executed at session start - **Termination Scripts** – executed at session end Scripts are defined under **Manage Application > Application Execution Scripts** and selected under **Application Launch Preferences** and **Application Termination Preferences**. ### ***Machine-Level Enhancements*** **Hot Key Support** Support has been added for: - **Hot Key to launch Windows applications** - **Hot Key to launch Web applications** This aligns with the existing **Hot Key to End User Session** functionality. ### ***Windows Admin “Run As” Authentication Prompt*** AuthX Secure V3 enables secure administrative elevation using AuthX authentication. - When an application requiring administrative privileges is launched, an **AuthX authentication UI** is displayed. - Users authenticate by tapping an RFID badge associated with an AuthX account that has administrative permissions. - If the authenticated account has the required privileges, the application launch proceeds; otherwise, access is denied. ### ***Display of Users on the Login Screen*** In **Shared Mode**, **Workstation Lock Mode**, and **Delegated Mode**, the login screen displays a list of logged-in users. - Users are shown as **profile tiles**. - Users can select a tile to proceed with authentication. - The number of displayed users is governed by the **“Number of active user sessions allowed”** setting under **Manage Configuration**. ### ***Multi-******RFID******Support*** AuthX Secure V3 allows multiple RFID badges per user. - Enabled via **Settings > General Settings > Admin** using **“Allow Multiple Access Badges per User.”** - Up to **three (3)****RFID****badges** can be enrolled per user. - Enrollment methods: 1. AuthX Secure login screen (if enabled) 1. Manage Authentication module 1. AuthX Admin Portal Users may authenticate using any enrolled badge. **Badge Replacement Functionality** If the maximum number of badges is reached, enrolling a new badge automatically replaces the **oldest enrolled badge**. ### ***Multi-language Support*** Users can select their preferred language from the **language dropdown on the login screen**, based on languages configured under **Settings > General Settings > Language**. ### ***Multi-domain Configuration*** - Domain management is handled under **Settings > Domain**. - Parent domains and alias domains can be configured. - Multi-domain configuration in the Windows agent is no longer required. *Light and Dark Theme Support* The AuthX Secure V3 Windows agent automatically adapts to the **system-defined light or dark theme**. --- ## **Setting Up AuthX Secure V3** *Pre-requisites* - Define policies under Security Policy > New Version, including rules, workflows, and networks. - Configure domains under Settings > Domain. - Select supported languages under Settings > General Settings > Language. *Setup Steps* 1. Log in to the AuthX Admin Portal. 1. Navigate to Applications > Manage Application > Configure Application. 1. Select Windows Application and provide an application name. 1. Click Apply a Policy and assign the policy created in the pre-requisites. 1. (Optional) Enable Auto Configuration and select workstation groups. Steps to Install the AuthX Secure Agent Using App ID, Key, and URL **Step 1: Collect Application Details** Before installation, obtain the following values from the Windows Application in the AuthX Admin Portal: - APPID – Application ID - APPKEY – Application Key - APPURL – Authentication Server Endpoint **Step 2: Run the Configuration Command** Run the following command in an Administrator Command Prompt to install the AuthX Secure agent: *msiexec /i "File Path of the downloaded Windows agent**MSI**file"**APPID**="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"**APPKEY**="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"**APPURL**="https://api-{hostname}.authx.com" APPTYPE="winapp"*` ` To install the AuthX Secure agent along with the EPIC launcher client, run: *msiexec /i "File Path of the downloaded Windows agent**MSI**file"**APPID**="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"**APPKEY**="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"**APPURL**="https://api-{hostname}.authx.com" APPTYPE="winapp" ADDLOCAL="MainFeature,EpicClient"*