- Knowledge Base
- Windows Logon Manager (WLM)
- 
        
        
      
        General Support
- 
        
        
      
        Technical Guides
- 
        
        
      
        SurePassID Authentication Server
- 
        
        
      
        Authenticators ("Tokens")
- 
        
        
      
        Windows Logon Manager (WLM)
- 
        
        
      
        ADFS Adapter
- 
        
        
      
        SAML2 IdP
- 
        
        
      
        LDAP
- 
        
        
      
        Self Service Portal (SSP)
- 
        
        
      
        LDAP Gateway
- 
        
        
      
        FIDO2/WebAuthn
- 
        
        
      
        License Management
- 
        
        
      
        Third Party Integrations
- 
        
        
      
        Twilio
- 
        
        
      
        Announcements and Alerts
- 
        
        
      
        Office 365
- 
        
        
      
        SurePassID Authentication Server VLE
- 
        
        
      
        WLM Session Manager
- 
        
        
      
        RADIUS
- 
        
        
      
        MFA-as-Code
What should the server name be in the Windows Logon Manager (WLM) Configuration Tool?
When configuring a WLM instance, what server name should I be using?
The server name is the fully qualified domain name (FQDN) of the SPAS (MFA) server that you have set up, ideally with a valid, trusted certificate that includes a Subject Alternative Name (SAN) matching the FQDN. This ensures smooth SSL/TLS handshaking between clients and the SPAS server.
If you are utilizing our production Software as a Service (SaaS) instance, you can simply use "mfa" as the server name, serving as a shortcut for mfa.surepassid.com.
In essence, you are instructing the Web Login Manager (WLM) on which FQDN to utilize to connect to the MFA server.
