Skip to main content
Version: v25.07.31

Authentication

The feature of VPN server authentication allows the user to select a preferred authentication method allowing secure and controlled access to the network. Whether you need to integrate with a directory service like LDAP or choose to use office365 credentials, this configuration ensures the flexibility and security to suit your organizational needs.

Follow the steps below to enable and configure authentication settings on the vpn server.

Enabling VPN Server Authentication​

Access VPN Server Settings​

  • Go to the Login > CE Device > [Select CE] > VPN Server.

Enable the VPN Server​

  • Check the box next to the VPN server option to enable it.

    image-1

Set Authentication Type​

  • Go to the Authentication section.

  • Choose the desired authentication type from the available options:

    • Office365:- Connect using Office365 authentication.
    • LDAP:- Use LDAP directory services for authentication.
    • Default:- Use the system's standard authentication method for Platform VPN Users.

    image-2

1. Office365​

  • If Office365 is selected, complete the following fields:

    • Tenant ID:- Enter the Tenant ID. This is a unique identifier for your organization within Office365. (i.g:- 12345-abcd-67890-efgh)
    • Client ID:- Enter the Client ID. : The client ID is associated with the registered application in Azure Active Directory. (i.g:- abc123-clientID-xyz456)
    • Client Secret:- Enter the Client Secret. This is a secret key generated when registering the application in Azure Active Directory. It is used to authenticate the application. Ensure this is kept secure.
    login-info

    If Office365 authentication is selected, login requires an Office365 username & password.

    image-3

2. LDAP​

  • If LDAP is selected, fill in the following fields:

    • LDAP Server:- Enter the LDAP Server. Specifies the hostname or IP address of the LDAP server to which the system will connect. This is the entry point for querying the LDAP directory. (i.g:- ldap://100.100100.100:portno)
    • LDAP Base DN:- Enter the LDAP Base DN. Defines a base Distinguished Name (DN) for LDAP queries. This is the root context from which all searches are performed. (i.g:- dc=com)
    • LDAP Bind DN:- Enter the LDAP Bind DN. Specifies the distinguished name (DN) of the user that will connect to the LDAP server for authentication. Bind DN is used for operations that require credentials. (i.g:- cn=admin)
    • LDAP Bind Password:- Enter the LDAP Bind Password.
    • LDAP Filter:- Enter the LDAP Filter. The filter used to define the scope of the query. (i.g:- objectClass=person)
    login-info

    If LDAP authentication is selected, login requires an LDAP username & password.

    image-4

3. Default​

  • If Default is selected, the system platform will use its standard authentication method for VPN users.

  • After selecting the desired authentication method, click Save Config to apply the changes.

    image-5

info

The authentication type selected will determine the availability of certain configuration options. Make sure you choose one that aligns with your security policies.

Confirmation Message​

  • By clicking on Save Config, a message will appear on the screen indicating that the VPN configuration is saved successfully.

    image-6

Important Notes for Users​

  • Choose the authentication type carefully — it directly impacts how users log in.
  • Office365 requires valid Azure AD configuration (Tenant ID, Client ID, Client Secret).
  • LDAP configuration must point to a reachable and secure directory server.
  • Client Secret and passwords must be stored securely and should not be shared.
  • Changing authentication type may affect existing VPN users.
  • Ensure only authorized administrators configure authentication settings.
  • Always verify login functionality after saving the configuration.
  • Use “Inactive” mode instead of deleting authentication settings whenever possible.

FAQs​

Q1: What is VPN server authentication?

VPN server authentication is the process of verifying user identity before granting access to the VPN. It ensures that only authorized users can establish a secure connection to the network. By requiring credentials (Office365, LDAP, or platform default), authentication provides: Controlled access to sensitive resources Secure communication through encrypted tunnels, Flexibility to integrate with organizational identity systems. This guarantees that VPN usage is both secure and compliant with organizational policies.

Q2: When should I use Office365 authentication?

You should use Office365 authentication when your organization relies on Microsoft Office365 for identity and access management. It is ideal if: Users already have Office365 accounts and credentials, You want seamless integration with Azure Active Directory, Centralized identity management and single sign‑on (SSO) are required, Security policies mandate using Microsoft’s authentication ecosystem, This option simplifies user management by leveraging existing Office365 accounts.