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
  • AccessTokenExpiration
  • Verbose Logging
  • ConnectionStrings\SessionLimitDB
  1. Managing
  2. Settings

Advanced Settings

SessionLimit 2.0

SessionLimit 2.0 settings are grouped under different categories. General settings related to SessionLimit 2.0 are located under General Settings. However, there are some settings that cannot be made from the interface. Below are the settings made from local files.

The following settings can be edited in the appsettings.json file in the SessionLimit 2.0 installation directory.

Since the following settings are changed in the appsettings.json file, IIS must be restarted after the changes are made. Otherwise, the settings will not become valid and it will continue to work with the old settings.

AccessTokenExpiration

Determines the session duration of the user logging in to the web portal. It is in minutes and defaults to 60 minutes. Shortening the time will make usage more difficult and increase safety. If the period is extended, it will reduce the need to log in during the day. However, in this case, an accidentally forgotten session will remain open during this period.

Token duration can be between 10 and 43200 minutes (30 days). If durations other than these are used, the default value of 60 minutes is used.

Verbose Logging

The VerboseLog parameter can be used to collect detailed logs. The value of this parameter can take the values ​​of true and false. If the value is set to true, all agent and server activities are written in detail to the t_TempRequests table in the database. This should only be used for problem detection. Long-term use may cause the database to fill up, slow down, and SessionLimit to stop functioning. Default value is false.

ConnectionStrings\SessionLimitDB

SessionLimit 2.0 uses the database in SQL Server. The connection string to this server is defined in this field. The information entered in this field is automatically encrypted after IIS runs.

SQL Server with default instance and with SQL Authentication

Copy

"Data Source=SERVERNAME; Initial Catalog=SessionLimit; user Id=UserName;password=Password; pooling=true; TrustServerCertificate=True;"

SQL Server with an instance and with SQL Authentication

Copy

"Data Source=SERVERNAME\Instance; Initial Catalog=SessionLimit; user Id=UserName;password=Password; pooling=true; TrustServerCertificate=True;"

SQL Server with default instance and with Integrated Authentication

Copy

"Data Source=SERVERNAME; Initial Catalog=SessionLimit; Trusted_Connection=True; pooling=true; TrustServerCertificate=True;"

SQL Server with an instance and with Integrated Authentication

Copy

"Data Source=SERVERNAME\Instance; Initial Catalog=SessionLimit; Trusted_Connection=True;
appsettings.json
{
  "ConnectionStrings": {
    "DbConnectionString": "The encrypted string of the connection string to the SessionLimit database appears in this field."
    },
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "AllowedHosts": "*",
  "Localization": {
    "DefaultLanguage": "tr-TR",
    "DefaultLanguagesPath": "Localization\\Languages\\"
  },
  "LogValue": { 
    "VerboseLog": false
  },
  "TokenOptions": {
    "AccessTokenExpiration": 60
  }
}

PreviousSyslog Message SettingsNext2FA

Last updated 5 months ago