Versions Compared

Old Version 35

changes.mady.by.user Vladimir Gololobov

Saved on

compared with

New Version Current

changes.mady.by.user Mikhail Yakovlev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Indeed Axidian Log Server component allows recording to record events from all Indeed Certificate Manager CertiFlow servers in a Unified Windows Event Log, Microsoft SQL Database, PostgreSQL or Syslog servers.

Info

The component is can be installed Install Axidian Log Server on one of Indeed CM the CertiFlow servers or on a separate workstation (in within or outside the domain or outside it). The system requirements for installing the component System requirements are the same as the Indeed CM for Axidian CertiFlow server. 

Installation Indeed

Installing Axidian Log Server

  1. Sign Log in to the workstation as a local administrator.

  2. Install the Indeed Log Server by running IndeedRun Axidian.LogServer-<version number>.x64.msi installer ( installer. The installer is located in the Indeed Axidian.Log.Server directory).

  3. Copy the following files from IndeedcmSchema.config. file from Axidian.Log.Server directory : To theand move it to C:\inetpub\wwwroot\lsdirectory — cmSchema.
  4. Copy eventLogTarget.config, msSqlTarget.config, pgSqlTarget.config and sysLogTarget.config. To the files and move them to C:\inetpub\wwwroot\ls\targetConfigsdirectory — cmEventLogTarget.config, cmMsSqlTarget.config, cmPgSqlTarget.config and cmSysLogTarget.config.
Note

Indeed Axidian Log Server works with one Read storage (<ReadTargetId>) and with multiple Write storages (<WriteTargets>).


Warning

IIS role restart is required to To apply changes in configuration files, restart the IIS.

Configuring event

Configuring event reading and writing to

the

Windows event log

  1. Edit the configuration file clientApps.config (C:\inetpub\wwwroot\ls\clientApps.config) as follows:

    • In Add the following data in Application section, add:

      Code Block
      languagexml
      firstline35
      <Application Id="cm" SchemaId="cmSchema">
	<ReadTargetId>cmEventLogTarget<<ReadTargetId>eventLogTarget</ReadTargetId>
    <WriteTargets>
       	<TargetId>cmEventLogTarget<<TargetId>eventLogTarget</TargetId>
    </WriteTargets>
	<AccessControl>
		<!--<CertificateAccessControl CertificateThumbprint="001122...AA11" Rights="Read" />-->
	</AccessControl>
</Application>


    • In the Targets section add Add a new element in Targets section:

      Code Block
      languagexml
      <Targets>
    <Target Id="cmEventLogTargeteventLogTarget" Type="eventlog"/>
</Targets>


  2. Save the changes and close the configuration file.

Configuring event reading and writing in MS SQL

The database for storing Indeed used as data storage for Axidian Log Server data must be is created manually, and is filling . The database contents are populated automatically.

  1. Create a database with an arbitrary name in the SQL Management Studio environment:
    • In the Object Explorer right-click the Databases tab.
    • Select New database... item from the context menu .
    • Specify the Database name: , e.g., LogServer.

    • In the Owner: field define the database owner of the database being created.

      Info

      Create a new account (say, servicesqle.g. cfServiceSql) or use any internal SQL account or Active Directory account (e.g., service account to be used with Indeed CM: servicecm). After the database is created. Once you create the database, this account would possess is granted db_owner, public privileges and shall be used by the system . The service account is now used to perform read/write operations from/to the database.


    • Save Click ОК to save the created database by clicking ОК.

      Scroll Pagebreak


  2. Edit the cmMsSqlTargetmsSqlTarget.config file (C:\inetpub\wwwroot\ls\targetConfigs\cmMsSqlTargetmsSqlTarget.config) according to the settings belowas follows:
    <Settings> … </Settings>:
    • Data Source -  this this parameter defines the server instance. The parameter is mandatory for all connections. Admissible values are: network name or server IP address, local or localhost for local connections.
    • Database -  database database name (ILS).
    • User Id -  the name of the service account name used to connect to the database.

    • Password  - service account password.

      Code Block
      languagexml
      <Settings>
	<ConnectionString>Data Source=MSSQL\SQLEXPRESS;Database=LogServer;User Id=servicesqlcfServiceSql;Password=P@ssw0rd</ConnectionString>
</Settings>


      Note

      If you use a named instance of Microsoft SQL Server, specify the Server parameter value in the following format: <server name>\<instance name>:

      Code Block
      <Settings>
    <ConnectionString>Server=sql\Named instance; ... </ConnectionString>
</Settings>



  3. Edit the configuration file clientApps.config (C:\inetpub\wwwroot\ls\clientApps.config) to working operate with cmMsSqlTargetmsSqlTarget.config as follows:

    • In Add the following data in Application section, add:

      Code Block
      languagexml
      <Application Id="cm" SchemaId="cmSchema">
	<ReadTargetId>cmMsSqlTarget<<ReadTargetId>msSqlTarget</ReadTargetId>
    <WriteTargets>
       	<TargetId>cmMsSqlTarget<<TargetId>msSqlTarget</TargetId>
    </WriteTargets>
	<AccessControl>
		<!--<CertificateAccessControl CertificateThumbprint="001122...AA11" Rights="Read" />-->
	</AccessControl>
</Application>


    • In Add a new element in the Targets section add a new element:

      Code Block
      languagexml
      <Targets>
    <Target Id="cmMsSqlTargetmsSqlTarget" Type="mssql"/>
</Targets>


  4. Save the changes and close the configuration file.

Configuring event reading and writing in PostgreSQL

The database for storing Indeed used as data storage for Axidian Log Server data must be is created manually, and is filling . The database contents are populated automatically.

  1. Create the database in PostgreSQL (for example, via pgAdmin):
    • In Browser section In Browser section right-click on the Databases menu item, select  Databases and select Create > Database...
    • Enter database name (for example, LogServer) in the database name in the Database field on General tab. Select the service account (for example, servicepg) in the Owner list which will be  Select a service account in the Owner field. This service account is used to connect to the database, then click . Click Save.

  2. Grant privileges to service account on database tables:
    • Select created database and open click Image Added to open the Query Tool (by clicking on Image Removed button or by pressing ALT+SHIFT+Q).

    • Enter the text of the request , specifying and specify the account name in it:

      Code Block
      languagesql
      GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO "service account without quotesname";


    • Select Execute/Refreshin Query Tool to grant privileges.

  3. By default PostgreSQL allows localhost connections only, so there is changes in configuration are required to grant access from other host, you can connect to PostgreSQL databases only locally. To operate between several servers, configure a remote connection to the database:

    • Open the pg_hba.conf in PostgreSQL directory.

      Info
      titlePg_hba.conf file location:

      For Windows — C:\Program Files\PostgreSQL\<version number>\data

      For *nix — /etc/postgresql/<version number>/main


    • Add a line with the following formatparameters:

      Code Block
      CONNECTIONTYPE DATABASE USER ADDRESS METHOD

      Where:

      • CONNECTIONTYPE -   Specify local or TCP/IP connection type. If "host" specified, To use TCP/IP connection will be used, you can specify host as CONNECTIONTYPE.
      • DATABASE - Name name of the database ("ALL" to . To allow connections to all databases), enter ALL.
      • USER - Database database user account ("ALL" to . To allow connections from all accounts), enter ALL.
      • ADDRESS - Range range of IP-addresses/IP-address/Hostname hostname of the Indeed Certificate Manager server ("CertiFlow server. To allow connections from any IP-address, enter 0.0.0.0/0" to allow connections from any IP-address).

      • METHOD - User account authentication method (for example, "md5", "of user account. E.g. md5, scram-sha-256" to use password-based authentication in a secure way).

        Code Block
        titleExamples:Example
        host LogServer servicepgcfServiceSql 192.200.1.0 md5
host ALL servicepgcfServiceSql 10.0.0.0/8 md5
host ALL ALL 0.0.0.0/0 scram-sha-256


  4. Edit the cmPgSqlTargetthe pgSqlTarget.config config file (C:\inetpub\wwwroot\ls\targetConfigs\cmPgSqlTargetpgSqlTarget.config) according to the settings belowas follows:
    <Settings> … </Settings>:
    • Host - Name name or IP-address of the PostgreSQL server.
    • Port - The TCP port that TCP port used to connect to PostgreSQL server listens on (default value is 5432 by default).
    • Database - Database name created in step 1name of the database.
    • Username - Service service account with that has access to the database.

    • Password - Service service account password.

      Code Block
      languagexml
      <Settings>
  <ConnectionString>Host=SRV-POSTGRESQL;Port=5432;Database=LogServer;Username=servicepgcfServiceSql;Password=P@ssw0rd</ConnectionString>
</Settings>


  5. Edit the configuration file clientApps.config (C:\inetpub\wwwroot\ls\clientApps.config) to working operate with cmPgSqlTargetpgSqlTarget.config as follows:

    • In the Add new TargetIds for ReadTarget and WriteTarget in Application section, add:

      Code Block
      languagexml
      <Application Id="cm" SchemaId="cmSchema">
    <ReadTargetId>cmPgSqlTarget<<ReadTargetId>pgSqlTarget</ReadTargetId>
             
    <WriteTargets>
        <TargetId>cmPgSqlTarget<<TargetId>pgSqlTarget</TargetId>
    </WriteTargets>
 
    <AccessControl>
        <!-- <CertificateAccessControl CertificateThumbprint="001122...AA11" Rights="Read" /> -->
    </AccessControl>
</Application>


    • In the Targets section add Add a new element in Targets section:

      Code Block
      languagexml
      <Targets>
	<Target Id="cmPgSqlTargetpgSqlTarget" Type="pgsql"/>
</Targets>


Configuring event writing in Syslog

Note

Indeed Syslog is limited to events writing only (<WriteTargets>), events reading is not available. Axidian Log Server supports only event writing to Syslog (<WriteTargets>) due to restrictions of Syslog protocol. Example below complements configuration from PostgreSQL case.

  1. Edit the cmSysLogargetthe sysLogarget.config file (C:\inetpub\wwwroot\ls\targetConfigs\cmSysLogTargetsysLogTarget.config) according to the settings belowas follows:
    <Settings> … </Settings>:
    • HostName - Name name or IP-address of the Syslog server.
    • Port - Specify port that used to connect to Syslog server listens on (default value is 514 by default).

    • Protocol - Connection type of connection to the Syslog server: UDP, TCP, TCPoverTLS.

    • Format - Optional, specify Format (optional)- logs format: Plain, CEF, LEEF.

    • SyslogVersion - Optional, specify protocol of the Syslog (optional) - Syslog protocol: RFC3164, RFC5424.

      Code Block
      languagexml
      <Settings HostName="SRV-SYSLOG" Port="514" Protocol="UDP"/>


  2. Edit the configuration file clientApps.config (C:\inetpub\wwwroot\ls\clientApps.config) to work with cmSysLogTargetsysLogTarget.config as follows:

    • In Add the following data in Application section, add:

      Code Block
      languagexml
      <Applications>
	<Application Id="cm" SchemaId="cmSchema">
		<ReadTargetId>cmPgSqlTarget<<ReadTargetId>pgSqlTarget</ReadTargetId>
			
		<WriteTargets>
			<TargetId>cmPgSqlTarget<<TargetId>pgSqlTarget</TargetId>
			<TargetId>cmSysLogTarget<<TargetId>sysLogTarget</TargetId>
		</WriteTargets>

		<AccessControl>
			<!-- <CertificateAccessControl CertificateThumbprint="001122...AA11" Rights="Read" /> -->
		</AccessControl>
	</Application> 
</Applications>


    • In the Targets section add Add a new element in Targets section:

      Code Block
      languagexml
      <Targets>
	<Target Id="cmPgSqlTargetpgSqlTarget" Type="pgsql"/>
	<Target Id="cmSysLogTargetsysLogTarget" Type="syslog"/>
</Targets>


Attachments
previewfalse
uploadfalse
oldfalse
patterns*.config
sortByname


Divbox
styleposition: fixed;

Table of Contents
printablefalse