SessionAudit
  • Infrastructure Documents
  • Overview
    • What is Session Audit
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • POC Requirements
    • Supported Configurations
    • Windows Server Requirements
    • SQL Server Requirements
    • Agent Requirements
    • Other Requirements
    • Network Considerations
    • Design
      • Single Deployment
      • Distributed Deployment
  • Deployment
    • Installing Microsoft SQL Server
    • HTTPS Certificate
    • DNS Records
    • .Net Framework 4.7.2 Download and Install
    • .NET Core 6.0.16 Download and Install
    • Internet Information Service Installation
    • Single Deployment
      • DB Creation
      • IIS and Site Settings
      • Database Permissions
    • Distributed Deployment
    • Upgrade Existing SessionAudit Installation
  • Initial Configuration
    • First time Login to SessionAudit
    • License Management
    • LDAP Settings
    • Role Management
    • Change Admin Password
  • Advanced Configuration
    • Login to the Portal with Domain Account
    • Settings
      • Server Settings
      • Agent Settings
      • LDAP Settings
      • Notification Settings
      • Syslog Settings
  • Managing
    • Dashboard (Home)
    • Tracker
    • Reporting
    • Computers
    • Role Management
    • License Management
  • Troubleshooting
    • SQL Express Usage
    • Securing Windows Server
Powered by GitBook
On this page

Was this helpful?

  1. Advanced Configuration
  2. Settings

LDAP Settings

Scope: SessionAudit 1.0

PreviousAgent SettingsNextNotification Settings

Last updated 1 year ago

Was this helpful?

To enable users to log in to the SessionAudit web interface and the agent, LDAP settings and Active Directory information must be entered. More than one LDAP server information can be entered. In SessionAudit 1.0, GMSA is not supported if an account is used for LDAP settings. A normal service account can be used, or queries can be made without authentication. Secure / Unsecure options can be used for LDAP connections.

After licensing, you should enter LDAP informations of your domain. When you configure LDAP settings, you will need to domain fqdn address, valid username and password to query LDAP, and LDAP port information.

  • Domain FQDN: Active Directory fully qualified domain name. e.g. domain.com

  • Authentication: If a username and password are to be used for LDAP connections, this option must be activated. If username and password are to be used, it is strongly recommended to enable the Secure option.

  • Username: User account authorized to run LDAP queries in Active Directory. While this account doesn't need to have any special privileges, make sure there are no privilege restrictions that could prevent it from performing an LDAP query.

  • Password: It is the password of the selected user account to be able to make LDAP queries.

  • Port: LDAP protocol listens on 2 ports by default.

  1. TCP port 389 runs over the unsecured channel. The use of this protocol is not recommended for security reasons. In this protocol, data is transmitted openly between servers without insecure encryption.

  2. TCP 636 port runs over the secure channel. The use of this protocol is recommended for security reasons. In this protocol, data is securely encrypted and transmitted between servers. This is the recommended protocol.

After all the information is entered, the LDAP test should be performed. If the settings are entered correctly and the user's privileges are correct, the test will be successful. In this case, LDAP settings are added to the system by clicking the Add button.

LDAP Settings