SessionLimit v2
  • Infrastructure Documents
  • Overview
    • What is SessionLimit
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • POC Requirements
    • Supported Configurations
    • Windows Server Requirements
    • SQL Server Requirements
    • Other Requirements
    • Network Considerations
    • Design
      • 2Factor VPN Design
      • 2Factor for OWA Access
      • 2Factor for Company Resources
  • Deployment
    • GMSA Account for Application Pool
    • DNS Service Record for Agent Autodiscovery
    • Installing Microsoft SQL Server
    • Internet Information Service Installation
    • .NET Core 8.0 Download and Install
    • .Net Framework 4.7.2 Download and Install
    • HTTPS Certificate
    • Installing SessionLimit 2.1
    • Upgrading SessionLimit
      • Upgrading SessionLimit 2.0.12 to 2.0.13
      • Upgrading SessionLimit 2.0.13 to 2.0.14
      • Upgrading SessionLimit to 2.0.15
      • Upgrading SessionLimit to 2.0.16
      • Upgrading SessionLimit to 2.0.17
      • Upgrading SessionLimit to 2.0.18
      • Upgrading SessionLimit to 2.1.0
      • Upgrading SessionLimit to 2.1.2
      • Upgrading SessionLimit to 2.1.3
      • Upgrading SessionLimit to 2.1.4
    • First Time Wizard
    • Agent Deployment
  • Managing
    • Logging to SessionLimit 2.0
    • Dashboard (Home)
      • General Dashboard
      • My Dashboard
      • Agents Dashboard
    • Policy
      • Session Protection Policy
      • 2FA Policy
    • Limitations
    • Endpoint Management
      • Users
      • Computers
    • Settings
      • General
        • Server Settings
        • LDAP Settings
        • Notification Settings
          • General Notification
          • E-Mail
          • SMS
        • Syslog Settings
        • Syslog Message Settings
      • Advanced Settings
      • 2FA
      • Agent
    • Events
    • Reports
    • Role Management
    • License Management
      • Online License
    • Syslog
      • Logon Operations
  • Agent
    • Session Control
    • 2FA
  • Tips&Tricks
    • SQL Express Usage
    • Fixing 500.19 web.config error
    • Enable HTTPS Redirection in IIS with HSTS
    • Using GMSA Account in Application Pool
    • Give Database Access for GMSA Account
    • What are the SessionLimit protection states?
    • Securing Windows Server
    • How to Create Custom Protected Attribute in Active Directory
Powered by GitBook
On this page
  • Create LDAP Connection
  • Domain FQDN
  • Port/Secure
  • Authentication (Username/Password)
  • Edit LDAP
  • AD User Phone Attribute
  1. Managing
  2. Settings
  3. General

LDAP Settings

Scope: SessionLimit 2.0

PreviousServer SettingsNextNotification Settings

Last updated 9 months ago

SessionLimit is Active Directory integrated software. Supports single Active Directory domain. One of the most important issues in SMS integration is mobile phone information. From this screen, the attribute containing the mobile phone number must be selected.

UserPrincipalName and samAccountName information can be used in user login operations.

Create LDAP Connection

Domain FQDN

Active Directory domain FQDN address is entered. This field supports entering the server name. It is recommended to enter Domain FQDN information. Example: domain.com

Port/Secure

LDAP port information is entered. By default, Unsecure LDAP connection is TCP 389, Secure LDAP connection is TCP 636. If a special port is used, it must be entered in this field.

The Secure option determines the use of LDAP/Secure LDAP.

Authentication (Username/Password)

In the username field, the user account that will be connected to the Active Directory domain and has the privileges of unlocking the account, resetting the password, reading mobile phone information, and reading alternative username attribute information is entered. This user account is also preferred to be given Replicate Directory Changes authority at the domain root level. Thanks to this authority, password history checks become applicable in password reset operations.

Test buttons are used to perform LDAP connection testing.

Edit LDAP

Click the edit button to determine the mobile phone and alternative username field and make changes to the LDAP connection.

AD User Phone Attribute

The attribute to be used for the mobile phone is selected. If this attribute is protected, the account used for the LDAP connection needs read permission for this attribute.

When the Authentication option is selected, it is stated that a user account will be used for LDAP transactions. If the Authentication option is not selected, the user account specified for the is used for the operations specified below.

IIS Application Pool