Chapter 10. Protection against unauthorized use: specifics and configuration

<< Prev   Next >>

10.1. General information

Protection against unauthorized use of the 1C:Enterprise application can be built on the use of the HASP4 Net network protection system (see page ) or the software licensing system (hereinafter SLS, see page ). Any of these systems provides simultaneous operation of a certain number of users (sessions) with the 1C:Enterprise application. The users can be located both within the local network and outside it (when using web clients or thin clients connected via a web server). The choice of a security system is determined by the delivery of the software product. For detailed description of 1C:Enterprise licensing options, see page . For comparison of features and application areas of 1C:Enterprise licenses, see the table below.

Feature

Software

Hardware

Can be stored on user computer

Yes

Yes

Can be stored on 1C:Enterprise server

Yes

Yes

Can be stored on another computer in a local network

No

Yes

Licenses stored on the same computer can be combined

Yes

No, only keys of different series

Can share over networks for any infobase types (license manager)

No

Yes

Can use licensing service

Yes, both client and server licenses

No

License consumption options:

License consumption option

Software

Hardware

License is acquired by client application on a local computer

Per computer

Per computer

License is acquired by client application from license manager over network

Not supported

Per computer

License is acquired by client application from 1C:Enterprise server

Per session

Per session

Web client

Per session

Per session

Mobile client

Per session

Per session

"Per computer" license allows you to run any number of client applications using any number of infobases on the computer that has the license. "Per session" license is acquired for one session only. Each infobase connection requires a separate "per session" license.

In addition, you can verify the licensed use of a particular application (see page ). During this check, information is used about the application itself and the user, to whom this application is registered.

Attention!  This chapter only describes the technical aspects of licensing 1C:Enterprise 8. For legitimate use of 1C:Enterprise 8, a different number of licenses may be required. Read the answers to FAQs on licensing here: http://v8.1c.ru/predpriyatie/questions_licence.htm.

10.2. HASP security system

10.2.1. General information

To protect against unauthorized use of the 1C:Enterprise application, the network security system HASP4 Net can be used. This security system helps to ensure the simultaneous operation of a certain number of users (sessions) with the 1C:Enterprise application. At the same time, users can be located both within the local network and outside it: web clients and thin clients connected to the infobase via a web server. In this case, users are counted either by the special  HASP License Manager program, or by the server part of 1C:Enterprise.

Attention!  Interacting with the HASP License Manager is only possible over IPv4.

With any method of counting users, one or several computers should be located on the network, to the USB ports of which the client HASP4 Net USB keys are connected. The total number of users, who can work with the application, is defined as the amount of the licenses available in each of the connected client keys (for some of the features described on page ).

IMPORTANT! It does not make sense to attach several HASP4 Net dongles of the same series to USB ports of one computer, designed to protect 1C:Enterprise, since these dongles are indistinguishable and only one of them will be actually used (chosen arbitrarily).

HASP License Manager can be started as a regular Windows application, as a service (only in Windows 2000 and later), or as a Linux application. When using a multi-user protection system, there is no need to install the HASP Device Driver on user computers, on which 1C:Enterprise is running and to the USB port of which the 1C:Enterprise client dongle is not connected.

You can download the latest versions of the HASP Device Driver and the HASP License Manager from:

  •  
    •  
    • https://thales-sentinel.ru/helpdesk/download-space/.
  •  
    •  
    • https://thales-sentinel.ru/helpdesk/download-space/.
  • Aladdin Monitor (for Windows only): https://thales-sentinel.ru/helpdesk/download-space/ (HASP HL tab, Utilities section, Aladdin Monitor utility).

10.2.2. USB key marking

USB key function

Marking

Local client USB key

ORGL8

Multi-user client key (the number of users is indicated after “NET”: 5, 10, 20, 50, 100)

NET5 ORGL8

NET10 ORGL8

NET20 ORGL8

NET50 ORGL8

NET100 ORGL8

Multi-user client key for 300 users

NET250+ ORG8A

Multi-user client key for 500 users

NET250+ ORG8B

Local key for 32-bit server

ENSR8

Local key for 64-bit server

EN8SA

A multi-user license for 1 000 users is supplied as a set of two multi-user licenses for 500 users (two NET250 + ORG8B keys are included in the package).

10.2.3. Specifications

One key of series ORGL8, ORGL8A and ORGL8B can simultaneously work on the same computer. The licenses are searched in the following order:

  • In the ORGL8 key
  • In the ORG8A key
  • In the ORG8B key

The 32-bit server dongle allows you to run any number of 32-bit working processes on a physical computer. The 64-bit server dongle allows you to run any number of 32-bit and 64-bit working processes on a physical computer.

When using dongles, the USB over IP technology, which allows access from a virtual machine to a USB device connected to a physical computer (for example, to a host computer), is not supported. If you need to ensure the execution of 1C software in a virtual machine, we recommend that you use either a software licensing system (see page ) or a server cluster licensing service that runs on a physical computer ({HL:cs:TI000000048}).

There is a function of storing the dongle whose license was obtained by the user during the last connection. During the next access attempt, a license will be obtained from this dongle. If a license cannot be obtained from the stored dongle, the search for an available license will be performed as described above.

10.2.4. Protection against unauthorized use

To prevent the illegal use of 1C:Enterprise, it is provided to users in a protected form.

The possibility to use the software at one or several workplaces, as well as the ability to use the 1C:Enterprise server are determined by the existing license agreements.

One of the components of the security system used is the dongle that protects against unauthorized use.

For the operation of the product, the use of which is governed by the License Agreement for one workspace or for one additional workspace, a dongle must be connected to the USB port of the computer (for more information on installing the protection driver, see page ). If the use of the product is regulated by an additional multi-user license, insert the USB key to the USB port of the computer, on which the HASP License Manager is running (for installation and usage, see page ).

Information about the latest changes in the security system is placed in the readme.htm file.

10.2.5. Monitoring the client licenses

10.2.5.1. General information

Depending on the type of client and the location of the key (local or network) with client licenses, several options for license monitoring are available. They are reviewed in detail below.

10.2.5.2. File mode

In this case, there are the following options for obtaining licenses.

10.2.5.2.1. Local USB key

Allows running any number of instances of the application in 1C:Enterprise or Designer mode on a computer with the USB key.

10.2.5.2.2. Multi-user client USB key accessible over the network through the HASP License Manager

Provides simultaneous operation of the computers depending on the number of users in the key. Allows running any number of instances of the application in 1C:Enterprise or Designer mode.

The number of licenses is limited by the total number of available licenses from all computers on the network, on which the HASP License Manager is installed and configured.

10.2.5.3. Client/server mode

In this case, there are the following options for obtaining licenses.

10.2.5.3.1. Local USB key

Allows running any number of instances of the application in 1C:Enterprise or Designer mode on a computer with the USB key.

10.2.5.3.2. Multi-user client USB key accessible over the network through the HASP License Manager

Provides simultaneous operation of the computers depending on the number of users in the key. Allows running any number of instances of the application in 1C:Enterprise or Designer mode.

The number of licenses is limited by the total number of available licenses from all computers on the network, on which the HASP License Manager is installed and configured.

10.2.5.3.3. A local multi-user client key without an installed HASP License Manager and a multi-user client key accessible via the network through the HASP License Manager

In this case, the key can be located both on the computer where the 1C:Enterprise server is installed (local multi-user client key) and on the network. The licenses number is counted by the cluster manager to which the session data service is assigned. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two instances of 1C:Enterprise are running on the same computer (in any wake-up mode and with any kind of client), then two licenses will be spent on it.

See also:

  • Shared use of dongles (see page ).

10.2.5.4. Web client

Depending on the version of the infobase (file or client/server), licenses are counted by either the web server extension module (in the file mode) or 1C:Enterprise server (in the client/server mode).

In this case, the key can be located both on the computer where the web server expansion module is installed (or the 1C:Enterprise server), and on the network. The web server extension module (or 1C:Enterprise server) directly counts the licenses. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two windows of a web browser are open on the same computer with access to the same infobase, then two licenses will be spent on it.

See also:

  • Shared use of dongles (see page ).

10.2.5.5. Thin client running via web server

To obtain licenses the thin client may use:

  • Local USB key
  • Multi-user USB key accessible for the thin client over the network through the HASP License Manager
  • Web server extension module or 1C:Enterprise server

If the license is obtained directly by a thin client, then on one computer you may start an arbitrary number of instances of the application in 1C:Enterprise mode.

A license can also be issued by a web server extension module (in the case of the file mode) or by 1C:Enterprise server (in the case of the client/server mode). In this case, the web server extension module or the 1C:Enterprise server directly counts the licenses number. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two copies of 1C:Enterprise are running on one computer, then two licenses will be spent for this. In this case, the key can be located both on the computer where the web server expansion module is installed (or the 1C:Enterprise server), and on the network.

See also:

  • Shared use of dongles (see page ).

10.2.5.6. Local key and web client

If a local key is installed on a computer with a 1C:Enterprise server or a web server (in the case of the infobase file mode), then you can run:

  • Any number of Designer instances on a computer with the key
  • Any number of client applications (except for the web client) on other computers if client licenses are available to them
  • In case of the infobase file mode:
    • One client application (including the web client) on any computer if the client key is not available to it
    • Any number of client applications (except the web client) on a computer with the USB key
  • In case of the infobase client/server mode:
    • One client application (including the web client) on any computer if the client key is not available to it
    • Any number of client applications (except the web client) on a computer with the USB key

In other words, you may perform developing and debugging with a web client using just the local key.

NOTE. When using a local key, only one web client can be started.

10.2.5.7. COM connection

When using a 32-bit COM connection, the available licenses are searched for in the following order:

  • Local client licenses
  • Local server licenses (both 32-bit and 64-bit)
  • Network client licenses
  • Client licenses on the 1C:Enterprise server (when in client/server mode) or on the web server (when in file mode, connected via the web server)

When using a 64-bit COM connection, the available licenses are searched for in the following order:

  • Local client licenses
  • Local server license (64-bit only)
  • Network client licenses
  • Client licenses on the 1C:Enterprise server (when in client/server mode) or on the web server (when in file mode, connected via the web server)

10.2.5.8.  Internet services and background jobs

Internet services (web services, HTTP services, and requests to OData) and background jobs do not require client licenses. However, if the infobase that provides Internet services operates in a client/server version, you must have a server license for the operation of the 1C:Enterprise server.

10.2.5.9. Terminal server

In this case, there are the following options for obtaining licenses.

10.2.5.9.1. Local USB key

Using a local key in the terminal session is not possible on the following operating systems:

  • Client operating systems: Microsoft Windows 7 and later.
  • Server operating systems: Microsoft Windows Server 2008 and later.

If the OS used is later than the above, then using a local key allows only one user to operate, who has connected to the terminal session with the identifier 0. Allows running any number of instances of the application in 1C:Enterprise or Designer mode. For terminal sessions with a non-zero session identifier, local keys are not available.

10.2.5.9.2. Multi-user client key

Licenses from a multi-user client key installed on the terminal server are available for use only if the HASP License Manager is installed and configured on the terminal server. Client licenses are counted for in a manner similar to a multi-user client key available on the network through the HASP License Manager. In this case, one terminal session is considered as one workstation.

10.2.5.10. Mobile client

Depending on the version of the infobase, the license is counted by:

  • File mode – web server extension module
  • Client/server mode – 1C:Enterprise server

The key can be located both on the computer, where the web server extension module is installed (or the 1C:Enterprise server), and on the network. Licenses are consumed at the rate of “one session  one license”. Thus, if two copies of an application that are connected to the same infobase are running on the same mobile device, then two licenses will be spent on it.

Remember that the mobile client always requires a separate client license (from a multi-user set). It means that the full development of an application running on a mobile client using only a local dongle is impossible.

See also:

  • Shared use of dongles (see page ).

10.2.5.11. Shared use of dongles

When 1C:Enterprise server (or web server extension) counts the client licenses, then the client licenses, which in Aladdin Monitor have the Timeout column value equal to 0, will be considered busy. In this regard, it is not recommended to use the same multi-user HASP keys to simultaneously obtain client licenses using the HASP License Manager and the 1C:Enterprise server (or web server extensions).

It is also necessary to consider the following feature: if several ORGL8 series multi-user client keys are detected on the network, the server will select one random key. After all licenses are used up for this key, you may use one multi-user ORG8A key, and then you may use one multi-user ORG8B key. When a client application selects the same network client key, which is selected by the server, the client application can also stop searching for a license in other keys of the same series available on the network.

10.2.5.12. Standalone server

In case of using the standalone server, a license can be obtained using:

  • Local key (thin client only).
  • Multi-user USB key accessible for the thin client over the network through the HASP License Manager
  • Standalone 1C:Enterprise server.

If the license is obtained directly by a thin client, then on one computer you may start an arbitrary number of instances of the application in 1C:Enterprise mode.

If the license is issued by the standalone server, then the licenses are spent "per session". In this case, the key should be available to the instance of the standalone server, which serves the used infobase. For the standalone server, the option to issue licenses must be enabled (infobase.distribute-licenses parameter of the standalone server configuration file).

10.2.6. Obtaining a server license

10.2.6.1. Server clusters

The dongle must be installed on the computer running (one or more) working process (rphost) of the server cluster. Working processes may belong to different server clusters. Checking for a server license is performed at the moment when the client application connects to the working process.

The server dongle is local and unavailable over the network.

10.2.6.2. Standalone server

The hardware dongle must be installed on the computer on which the standalone server instance is running. Checking for a server license is performed at the moment when the client application connects to the standalone server.

When working with a file infobase, there is an option to work simultaneously up to 3 (three) client sessions (including three sessions) without using the hardware dongle. At the same time, sessions of background jobs and Internet services are technically ignored when calculating the number of simultaneously used sessions.

The server dongle is local and unavailable over the network.

10.2.7. Installing HASP Device Driver

10.2.7.1. On Windows

The HASP Device Driver installation program (haspdinst.exe) is included in the delivery package and installed on the computer when you install the 1C:Enterprise server cluster.

To install HASP Device Driver, select the menu item Start  Programs  1C:Enterprise 8  Additionally Protection driver installation.

You can also install the HASP Device Driver "manually". To do this, from the command line, run the haspdinst.exe program located in the \Program Files\1cv8\common\ directory with the -i command. Thus, the command line for installing the HASP Device Driver is as follows:

haspdinst -i

TIP. It is recommended that you first install the HASP Device Driver, and then attach the dongle to the USB port.

IMPORTANT! Disconnecting the dongle from the USB port during operation is prohibited.

In case of uselessness the HASP Device Driver can be removed from the system. To remove HASP Device Driver, select the menu item Start  Programs  1C:Enterprise 8  Additionally  Protection driver removal.

To remove the HASP Device Driver, you can also use the following command line:

haspdinst -r

10.2.7.2. On Linux

Download HASP Device Driver for Linux before the installation. For the download hyperlink, see page .

To install the HASP Device Driver, perform the following steps (actions must be performed as administrator):

  • Unpack the archive by executing the command:
tar xzf HASP_SRM_LINUX_3.50_Run-time_Installer_script.tar.gz
  • Go to the directory with the unpacked driver by executing the command:
cd HASP_SRM_LINUX_3.50_Run-time_Installer_script
  • Install the driver by executing the command (make sure that you enter the dot at the end of the command line):
./dinst .

TIP. It is recommended that you first install the HASP Device Driver, and then attach the dongle to the USB port.

IMPORTANT! Disconnecting the dongle from the USB port during operation is prohibited.

To remove the driver key, go to the directory with the unpacked driver and execute the command:

./dunst

10.2.7.3. On macOS

Download HASP Device Driver for macOS before the installation. For the download hyperlink, see page .

To install the driver, open this archive using the Finder and run the Install Sentinel Runtime Environment file and follow the instructions of the installation program.

TIP. It is recommended that you first install the HASP Device Driver, and then attach the dongle to the USB port.

NOTE. Disconnecting the dongle from the USB port during operation is prohibited.

To delete the driver, open this archive using the Finder and run the Uninstall Sentinel Runtime Environment file and follow the instructions of the uninstall program.

10.2.8. Installing HASP License Manager

10.2.8.1. On Windows

The 1C:Enterprise application includes the lmsetup.exe utility used to install the HASP License Manager. The utility is located on the installation disk of the 1C:Enterprise application and can be started either directly from the command line or through the 1C:Enterprise installation program menu.

HASP License Manager can be installed on any computer on a local network running Microsoft Windows operating systems. At the same time, in any of these systems, HASP License Manager can be installed as a normal application, and in Windows 2000 and later it can also be installed as a Windows service.

IMPORTANT! Unstable operation of the License Manager is possible if it is installed on a computer used as a terminal server. Installing the License Manager on a computer that is used as a terminal server is not recommended.

To install the HASP License Manager, start the lmsetup.exe installation program (the following is an example of installing the HASP License Manager version 8.32).

Fig. . Language selection

Then select English for the installation (see ).

Next you need to confirm that you accept the proposed license.

Fig. . License Acceptance

In the case of installing HASP License Manager on a computer running Windows 2000 and later, you will be offered two options for installing HASP License Manager as an application (Application) or as a service (Service). If the HASP License Manager is installed on a computer running Windows 98/Me, this dialog will be skipped, since only the application can be installed on these operating systems.

Fig. . Selecting installation mode

Next, you be offered to choose the directory where the HASP License Manager executable files and the help file will be placed. If you install HASP License Manager as a Windows service, the executable files will be placed in the Windows system directory, and only the help file will be installed in the selected directory.

Fig. . Choosing the installation path for HASP License Manager

At the next step of installation, you are prompted to select a group in which the shortcuts for starting the HASP License Manager and the help file will be placed. By default, a new group is created with the name HASP License Manager, but you can select an existing group or change the name of the group being created.

Fig. . Specifying a group name

When installing the HASP License Manager as a Windows application, you will be prompted to place the HASP License Manager shortcut in the Startup directory). In this case, the HASP License Manager will start automatically when the operating system boots. If you choose the other option, you will have to start the HASP License Manager manually.

Fig. . Selecting run mode

At the next step, it is proposed to install the HASP Device Driver, which is necessary for the normal operation of the HASP License Manager. Using this driver, the HASP License Manager interacts with the HASP4 Net USB dongle. If the HASP Device Driver has already been installed on the computer, then reinstalling the HASP License Manager is not required.

Fig. . Install protection driver

After the installation process is complete, you will be prompted to start the HASP License Manager. If you refuse, you can start it later manually. Procedures for starting the HASP License Manager for various installation options are described below.

Fig. . HASP License Manager starting dialog

10.2.8.1.1. Starting HASP License Manager as Microsoft Windows application

If the HASP License Manager was installed as a Microsoft Windows application, it is started by running the program file nhsrvw32.exe, which is placed on the hard disk of the computer by the HASP License Manager Setup program.

When you run nhsrvw32.exe from a command line, you can set the parameters, by which HASP License Manager can be more “instructed” about using a particular network protocol for interaction with the protected programs.

It should be noted that configuring network protocols makes sense only when the default mode of using the network protocols causes unstable operation or there are serious delays in running protected programs.

Each parameter is preceded with "-" or "/". Example:

nsrvw32 -tcpip

Or:

nsrvw32 /tcpip

When you start the nhsrvw32.exe program, the following parameters can be used.

-addrpath=<path>

Specifies where to save the haspaddr.dat file. By default, the file is saved in the directory where the HASP License Manager was downloaded.

-ipx

Instructs the HASP4 Net application to use the IPX protocol with SAP.

-ipxnosap

Instructs the HASP4 Net application to use the IPX protocol without SAP. When using the HASP License Manager for Win32, other protocols can be loaded using the-tcpip or -netbios commands. In this case, the HASP License Manager creates a newaddr.dat file that contains the address of the station where the HASP License Manager is running. When you download the HASP License Manager with one of these keys, only those protected applications that have access to the newaddr.dat file will be able to exchange data with it.

-ipxsocket num=<number>

Use this parameter if you want to change the socket that is used to exchange data with HASP License Manager. The default socket is 7483 (hex value).

-localnet

This parameter should only be used if you want the HASP License Manager to serve the stations exclusively on the local network. If the HASP License Manager receives requests from workstations that are not on the local network, they get error code 140.

-nbname=<name>

Assigns a NetBIOS name to the HASP License Manager. The parameter action is identical to -nethaspnb name.

-netbios

This parameter allows you to use the HASP4 Net application only with NetBIOS protocol. When using the HASP License Manager for Win32, other protocols can be loaded using the -tcpip or -ipxnosap commands.

-portnum=<number>

If you use TCP/IP, this parameter allows you to specify a network port that will use the HASP License Manager. The default port is 475.

-srvname=<name> [,name]

Assigns one or more IPX, TCP/IP, or NetBIOS names to the HASP License Manager. A maximum of 6 names can be assigned.

-tcpip

This parameter allows you to use the HASP4 Net application only with TCP/IP protocol. When using the HASP License Manager for Win32, other protocols can be loaded using the -ipx or -netbios parameters.

-use lananum=<x> [,x]

Instructs HASP License Manager to operate with specific communication channel numbers.

-userlist

Limits the number of users serviced by the HASP License Manager. The default value is 250.

10.2.8.1.2. Running HASP License Manager as a Microsoft Windows service

HASP License Manager can be started as a Microsoft Windows service only if it was installed to operate as a service. And this, as noted above, is possible only in the Microsoft Windows 2000 and earlier versions of operating systems.

When you install HASP License Manager as a Microsoft Windows service, it is installed as a startup, that is, the HASP License Manager will start every time you start Microsoft Windows.

If necessary, you can change the startup settings of the service and start and stop it manually.

To start, stop, and configure the HAPS License Manager service manually, you should refer to the control menu Start Setup Control Panel Administrative Tools  Service  (Start Control Panel Administrative Tools  Services). In the list of services that appears, you need to find the HASP Loader service and right-click it. Through the context menu that appears, you can perform all the necessary actions with the service.

10.2.8.2. On Linux

Download HASP License Manager for Linux before proceeding with the installation. For the download hyperlink, see page . HASP License Manager also requires you to install HASP Device Driver. For the download hyperlink, see page .

To install the HASP License Manager, perform the following steps (actions must be performed as administrator):

  • Copy the downloaded file to the directory where the HASP License Manager will be located (for example,/opt/hasplm).
  • Unpack the archive by executing the command:
tar xzf hasplm_linux_8.30.tgz
  • Add the HASP License Manager starting command (before exit 0 command) to the /etc/rc.local file from the directory where it was unpacked:
/opt/hasplm/hasplm

Adding a command to the rc.local file will cause the HASP License Manager to start automatically when the system restarts.

  • Start HASP License Manager by executing the command:
hasplm

If you want to configure the HASP License Manager using the nhsrv. ini configuration file (see page), the path to the configuration file should be specified in the HASP License Manager command line:

/opt/hasplm/hasplm -c /etc/nhsrv.ini

10.2.8.3. Configuring the HASP License Manager with a configuration file

Some HASP License Manager settings can be set using the nhsrv.ini configuration file (see page).

If you are using keys with a lot of user licenses (for 300, 500, and 1,000 users), please pay attention to the NHS_USERLIST parameter when configuring HASP License Manager.

10.2.9. Setting up the 1C:Enterprise application for operation with the HASP License Manager

The 1C:Enterprise application is capable of using IPX, TCP/IP, or NetBIOS network protocols to communicate with the HASP License Manager. By default, the network protocol definition is automatically defined. This mode is always recommended, except when the automatic network protocol detection and communication setup mode is unstable or causes significant delays.

NOTE. Accessing the HASP License Manager is always made via UDP. Specifying the TCP/IP protocol in the nethasp. ini file is ignored.

To configure the parameters of the interaction of the 1C:Enterprise application with the HASP License Manager, the configuration file nethasp.ini is used (see page ).

Example of nethasp.ini file:

[NH_COMMON]
NH_TCPIP=Enabled
 
[NH_TCPIP]
NH_SERVER_ADDR=192.168.0.12
NH_PORT_NUMBER=475
NH_TCPIP_METHOD=UDP
NH_USE_BROADCAST=Disabled

In this example, the protection server is located on the network at 192.168.0.12, the network port 475 is used, UDP packets are used, and the TCP/IP broadcast mechanism is denied.

When installing the 1C:Enterprise application, the sample file nethasp.ini is copied to the directory of the configuration files of the 1C:Enterprise application. This file is almost entirely composed of commented lines and does not override the default settings in any way but it contains at the same time the most complete list of parameters that can be used to configure the interaction of the 1C:Enterprise system with the HASP License Manager.

10.3. Software Licensing System

10.3.1. General information

10.3.1.1. Overview and terms

The Software Licensing System ensures that users interact without using any additional physical devices. For operation you need to use a special platform software license file. This file, in encrypted form, contains the information required for the operation of the application,  the parameters of the license itself and the characteristics of the object, for which the license is activated. Activation (binding) is the procedure of acquiring a software license file in accordance with its (license) characteristics: serial number of the kit and PIN code. When activated, a software license becomes associated either with the computer's hardware, or with a HASP dongle available locally or in the network. Several PIN-codes are supplied in the package. The number of PIN codes in the package and the number of simultaneously active PIN codes are determined by the license type.

Application 1C:Enterprise (client or server), if required to obtain a license, searches for license files for all available paths (see page). Next, the parameters of the license and the characteristics of the object, for which the software license was obtained, are received from the files. If the parameters of the current object received from the license file match the actual object parameters,  checks are performed related to the number of users and the license type (client or server), otherwise the license is rejected. Access to the file is determined by the access rights of the operating system. If the user on whose behalf the application is running, does not have access to the license file (or the directory where the file is located), then the license will not be obtained.

10.3.1.2. Types of software licenses:

Software licenses can be:

  • Single-user client. Allow you to run any number of client applications on the same computer.
  • Multi-user client. Allow you to run a certain number of client applications from arbitrary computers. The number of client applications running simultaneously is determined by the license value.
  • Combined client. They are a combination of a single-user group and a one multi-user license. If any single-user license is activated first,  the multi-user license will not be activated and only single-user licenses can be used. If a multi-user license is activated first,  single-user licenses cannot be activated.
  • Server license for a 32-bit server. Allows the use of an arbitrary number of 32-bit working processes (rphost) on one computer.
  • Server license for a 64-bit server. Allows the use of an arbitrary number of 32-bit or 64-bit working processes (rphost) on one computer.
  • A server license with a limited number of concurrent sessions. Allows the use of one working server of any bit capacity (32 or 64) on one computer.

10.3.1.3. License location and combined use

Multi-user licenses can be located on a 1C:Enterprise server computer, a Web server extension module, or a terminal server. Only single-user licenses can reside on the client computer. Software licenses located on the server (1C:Enterprise or terminal), are added without restrictions. Software licenses can be used together with HASP dongles (in this event, the available licenses are combined). In the case of shared use, the software licenses will be used first and then  the licenses from the HASP keys.

10.3.1.4. Key parameters

A software license is associated either with the computer's hardware, or with a HASP dongle available locally or in the network (using license manager). If a software license is associated with a computer, key parameters of the computer's hardware are collected and analyzed. A software license can be associated with any HASP dongle in use by 1C:Enterprise.

Depending on association type, the following key parameters are analyzed:

  • Association with computer:
    • Key parameters:
      • Operating system name
      • Operating system version (for Windows, only the first two digits of the version number are analyzed)
      • OS serial number (Windows only, excluding Windows 10)
      • OS installation date (Windows only, excluding Windows 10)
      • Network name of the computer
      • Motherboard model
      • RAM memory
      • BIOS type and version
      • List of processors and their parameters
      • list of network adapters and their MAC addresses, however, the key parameter comparison procedure the following is excluded:
        • Bluetooth network adapters
        • Network adapters connected to IEEE 1394 or USB
        • WAN and RAS software adapters
        • Adapters that do not have MAC addresses or VEN_ and DEV_ data from the PNP ID
      • List of hard disks and their parameters
    • Usage:
      • If at least one of the key parameters is changed during the operation, it will be necessary to reactivate the software license (using a new PIN code). Computer parameters are polled not more than once a day.
      • USB and IEEE 1394 storage devices are ignored.
      • When verifying that the software license is compliant with the settings of the current computer, the operating system name and version are not parsed if the scan is running on Linux.
  • Association with HASP dongle:
    • Key parameters:
      • Dongle series
      • Dongle type
      • Dongle ID
    • Usage:
      • Each PIN code can be used to associate a software license with one HASP dongle only. However, the PIN code can be used any number of times to reactivate the software license for the same owner and the same HASP dongle.
      • You cannot use the software license with any HASP dongles except the one associated with this license.
      • When HASP dongle is used with license manager, activation check occupies 1 free license for 1 second. Activation check is performed once every 20 seconds or more. To ensure stable operation of a software license associated to a network dongle, you need to constantly have at least one free license in this dongle.
      • If multiple keys of the same series are used across the network, it is recommended that you specify the correct license manager in file nethasp.ini located on the computer where the activated software license is stored.

10.3.1.5. Available software licenses

The software license file is considered available for use if:

  • It is not in the blacklist.
  • It has a correct format.
  • It is associated with the current computer, or the associated HASP dongle is in use on this computer.
  • Contains an available license.
  • The network does not use other license files obtained for the same PIN-code and serial number of the program. If such a situation is detected, the license file is rendered unusable and blacklisted. If several license files obtained for one serial number are detected on one computer, then such files are not blacklisted, and only one file that was created or used most recently is used.

Hereinafter in this section, terms "software license file" and "software license" will refer to an available software license as defined above.

10.3.1.6. Software licenses and virtual machines

If you use 1C:Enterprise on virtual computers, you must activate the software license on each virtual machine. When using virtual machines, the software license is attached to the virtual machine settings (the virtual machine parameters are equivalent to the real computer parameters and are listed above). If any of these parameters are changed (this might happen during virtual machine migration or load redistribution, among others), you will need to reactivate the license using a new PIN code.

To avoid reactivating software licenses on virtual machines:

  • Use a licensing service installed on a physical computer or a virtual machine with fixed parameters (supported in client/server mode only).
  • Associate the software license with a HASP dongle. In this event, the dongle must be available on the virtual machine both before and after migration.
  • Use both methods described above, whenever possible.

10.3.1.7. Activation and usage

When planning to use software licenses, keep in mind the following peculiarities:

  • No more than 256 processes from one operating system session can simultaneously access to a one software license file.
  • On one computer, you can access one software license file from up to 256 operating system sessions.

If the software license is activated on per-computer basis, please keep in mind the following:

  • When checking computer information, only the removal of devices is analyzed, not the addition of devices. For example, when you activate the software license, one network adapter was installed on your computer. You can add another network adapter without having to reactivate the software license, but you cannot replace one network adapter with another.
  • You can increase the RAM on your computer, but you should not reduce it. For example, license activation was performed with 2 GB RAM. Without the need to reactivate the software license, you can increase the memory to 6GB and then reduce it to 4GB. However, reducing the amount of RAM below 2GB will require reactivation of the software license.
  • Changes are analyzed by the current state of the computer relative to the state when the license was activated.

A Licensing Center web page http://users.v8.1c.ru/lc/en is for receiving software licenses on electronic media. You have to submit a license request file (generated using this window) to the Licensing Center and get the license data file in return from the Licensing Center. A web service http://users.v8.1c.ru/LicenseCenter/ws/lm.1cws is for automatic receiving of software license.

See also:

  • nethasp.ini (see page ).
  • Cluster services Licensing service ({HL:cs:TI000000024})

10.3.2. License types

Client software license types:

Type

License Qty

Set of PIN codes

Users

Active

Supplied

Single-user, 1 user

1

1

1

3

Combined, 5 users

5

1

5

8

5

1

3

Combined, 10 users

10

1

10

14

10

1

3

Combined, 20 users

20

1

20

25

20

1

3

Multi-user, 50 users

50

50

1

3

Multi-user, 100 users

100

100

1

3

Multi-user, 300 users

300

300

1

3

Multi-user, 500 users

500

500

1

3

Multi-user, 1,000 users

1000

2*500

2*1

2*3

Multi-user license for 1,000 users is delivered as a set of two multi-user licenses for 500 users.

For combined licenses, you can determine which type of license is most suitable for your needs. If a single-user license is activated first when operating with a combined license, it is considered that a set of stand-alone licenses is selected and the Multi-user license becomes impossible. If a Multi-user license is activated first, it is considered that a multi-user license has been selected and further activation of single-user licenses becomes impossible.

NOTE. PIN codes additionally included in the delivery, can be used if the key license parameters are changed.

Server Software License options:

Type

Description

Set of PIN codes

Active

Supplied

Server, 32-bit

Allows the use of an arbitrary number of 32-bit working processes on one physical computer

1

3

Server,64-bit

Allows the use of an arbitrary number of 32-bit or 64-bit working processes on one physical computer

1

3

A server license with a limited number of concurrent sessions

Allows the use of one working server of any bitness on one physical computer

1

3

Server license with a limited number of concurrent sessions allows you to run one working server of arbitrary bitness (32 or 64-bit) on one computer, while maintaining a maximum of 5 client sessions and 1 Designer session. The following sessions are understood as client sessions: thick client, thin client, web client, external connection.   Client applications use client licenses that are obtained in the usual way.

10.3.3. Protection against unauthorized use

To prevent the illegal use of 1C:Enterprise, it is provided to users in a protected form.

The possibility to use the software at one or several workplaces, as well as the ability to use the 1C:Enterprise server are determined by the existing license agreements.

10.3.4. Monitoring the client licenses

10.3.4.1. General information

Depending on the type of client and the location of file with software licenses, several options for accounting licenses are possible. Subsections below contain detailed information on client software license accounting methods.

10.3.4.2. File mode

In this case, you may use only single-user licenses that ensures that the computer that contains the software license file will run an arbitrary number of application instances in 1C:Enterprise mode or in Designer.

The exception is the terminal mode of 1C:Enterprise. In this case, it is possible to use multi-user license infobase with file mode. For more information see page .

10.3.4.3. Client/server mode

In this case, there are the following options for obtaining licenses.

10.3.4.3.1. Single-user software license

Allows running any number of instances of the application in 1C:Enterprise mode or Designer on a computer with a software license file.

10.3.4.3.2. Multi-user software license

1C:Enterprise server counts the licenses.

In this case, the software license files are located on the computer where the 1C:Enterprise server is installed. The server directly counts the licenses. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two instances of 1C:Enterprise are running on the same computer (in any wake-up mode and with any kind of client), then two licenses will be spent on it.

10.3.4.4. Web client

Depending on the version of the infobase (file or client/server), licenses are counted by either the web server extension module (in the file mode) or 1C:Enterprise server (in the client/server mode).

In this case, the software license file can be located on the computer where the web server extension module is installed, or on the computer where the 1C:Enterprise server is installed. The web server extension module (or the server) directly counts the licenses. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two instances of 1C:Enterprise are running on the same computer (in any wake-up mode and with any kind of client), then two licenses will be spent on it.

10.3.4.5. Thin client running via web server

To obtain licenses the thin client may use:

  • Single-user software license
  • Web server extension module or 1C:Enterprise server

In this case of single-user license that ensures that the computer with a software license file will run an arbitrary number of application instances in 1C:Enterprise mode.

If you use a web server extension module or 1C:Enterprise server to obtain a license, then the web server extension module counts the licenses for file mode, and 1C:Enterprise server  for client/server mode. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two instances of 1C:Enterprise are running on the same computer (in any wake-up mode and with any kind of client), then two licenses will be spent on it.

The software license file can be located on the computer where the web server extension module is installed, or on the computer where the 1C:Enterprise server is installed.

10.3.4.6. Single-user software license and web client

If a single-user software license is installed on a computer with a 1C:Enterprise server or a web server (in the case of the infobase file mode), you can run:

  • Any number of Designer instances on a computer with a single-user software license file.
  • Any number of client applications (except for the web client) on other computers if they have access to client licenses.
  • One of the following startup options is also available:
    • One client application (including the web client) on any computer if the client license is not available to it.
    • Any number of client applications (except the web client) on a computer with the software license file.

In other words, you may perform developing and debugging with a web client using just the single-user software license. However, when you use the web client on the local computer, you still have the option to run only the Designer, other types of clients cannot be started.

10.3.4.7. COM connection

When using a 32-bit COM connection, the available licenses are searched for in the following order:

  • Single-user software licenses
  • Multi-user software licenses
  • Client licenses on the 1C:Enterprise server (when in client/server mode) or on the web server (when in file mode, connected via the web server)

When using a 64-bit COM connection, the available licenses are searched for in the following order:

  • Single-user software licenses
  • Multi-user software licenses
  • Client licenses on the 1C:Enterprise server (when in client/server mode) or on the web server (when in file mode, connected via the web server)

If COM connection is started from the code executed on the 1C:Enterprise server as the in-process COM server, and the server uses the server software license, then the COM connection uses the server software license. Otherwise, the COM connection searches for the client software license as described above in this section.

10.3.4.8. Internet services, background jobs

Internet services (web services, HTTP services, and requests to OData) and background jobs do not require client licenses. However, if the infobase that provides Internet services operates in a client/server version, you must have a server license for the operation of the 1C:Enterprise server.

10.3.4.9. Terminal server

10.3.4.9.1. General information

When using Windows applications, consider that the workspace is determined by the session ID number in the software licensing system. All license requests made from the same computer and with the same session ID are considered to have been received from one workplace. For example, if there is a computer that has a single-user software license installed, the license can be used by an arbitrary number of client applications running interactively. However, if on this computer the client application (in any mode) will be started from any Windows service, it will be considered as analogue of the terminal server, and an additional license will be required. This feature concerns any software licenses (not necessarily single-user).

You can also consider the following features of client license registration:

10.3.4.9.2. Single-user software license

Allows running any number of application instances in 1C:Enterprise mode or in Designer on behalf of one terminal session.

Software licenses (both single-user and multi-user) stored on the terminal server are added if the license files are available to all users of the terminal server.

10.3.4.9.3. Multi-user software license

Multi-user software license can be stored on a terminal server and used for both file and client/server modes of the application. In this case, you can run any number of application instances in 1C:Enterprise mode or Designer for the number of concurrent connections to the terminal server (terminal sessions) equal to the number of users a multi-user software license covers.

Software licenses (both single-user and multi-user) stored on the terminal server are added if the license files are available to all users of the terminal server.

10.3.4.10. Mobile client

Depending on the version of the infobase (file or client/server), licenses are counted by either the web server extension module (in the file mode) or 1C:Enterprise server (in the client/server mode).

In this case, the software license file can be located on the computer where the web server extension module is installed, or on the computer where the 1C:Enterprise server is installed. The web server extension module (or the server) directly counts the licenses. In this case, licenses are consumed at the rate of “one session  one license”. Thus, if two instances of mobile client are running on one mobile device, then two licenses will be spent for this. If Designer is running on the computer where the web server is located, and a mobile client is running on the mobile device that uses the web server to access the infobase, two licenses will also be required for such access.

10.3.4.11. Standalone server

In case of using the standalone server, a license can be obtained using:

  • Local software license (thin client only).
  • Standalone 1C:Enterprise server.

If the license is obtained directly by a thin client, then on one computer you may start an arbitrary number of instances of the application in 1C:Enterprise mode.

If the license is issued by the standalone server, then the licenses are spent "per session". The file with the activated software license must be accessible to the instance of the standalone server, which serves the infobase used. When defining availability, consider the user on behalf of whom the standalone server instance is running. For the standalone server, the option to issue licenses must be enabled (infobase.distribute-licenses parameter of the standalone server configuration file).

10.3.5. Activating and obtaining a server license

10.3.5.1. Server clusters

The software license must be activated for the computer that is running (one or more) of the server cluster working process (rphost) or the Cluster Manager (rmngr), to which the Licensing Service is assigned.

Checking for a server license is performed at the moment when the client application connects to the working process (rphost).

If the server license is issued by the cluster licensing service, keep in mind the following feature of the service: if the licensing service is simultaneously available software licenses for the 32 and 64-bit 1C:Enterprise server, then when requesting the license for the 32-bit server a license for the 64-bit server can be issued instead. This happens if, at the time of the license request, the 64-bit server license is the first available license (in the order of the files in the activated licenses directory). Thus, it is not advisable that one licensing service distributes software licenses for 1C:Enterprise 32 and 64-bit servers.

See also:

  • Cluster services ({HL:cs:TI000000024:details}).

10.3.5.2. Standalone server

The software license must be activated for the computer running the standalone server.

Checking for a server license is performed at the moment when the client application connects to the standalone server.

When working with a file infobase, there is an option to work simultaneously up to 3 (three) client sessions (including three sessions) without using an activated server license. At the same time, sessions of background jobs and Internet services are technically ignored when calculating the number of simultaneously used sessions.

10.3.6. Software license activation

10.3.6.1. General rules

One of the protection system components is the software license for the use of 1C:Enterprise. Software licenses can be activated by either of these utilities:

  • License activation wizard, which is available in Designer using the Service – Obtaining License ... command.
  • ring utility. For utility description, see page .

When activating a license:

  • Select an action:
    • Acquire a license (choose the Acquire a license option)
    • Upload license details file to acquire the license using an external storage device (choose the Specify license details file option)
  • If you want to get the license, specify the distribution package number and PIN code.
  • Click Advanced settings to specify additional parameters related to license activation:
    • To associate the license with 1C:Enterprise server, select the Install the license on the server check box and enter the 1C:Enterprise server access parameters into Server and Port fields. You should choose this option when you associate the software license with 1C:Enterprise server using Designer on another computer. In this case, the file with the activated software license will always be placed in the profile directory of the user, on behalf of which the 1C:Enterprise server (by default usr1cv83) is operating on the computer where this 1C:Enterprise server is running.
    • The Automatic acquisition check box determines the software license activation method. If the check box is selected,  the license will be activated automatically. If the check box is cleared, you will be prompted to choose one of 3 license activation methods: automatically, on an external storage device, or by phone.
  • Select an operation with license:
    • First-time registration  initial license acquisition,
    • Recovery  license reacquisition or update.
  • For first-time registration, you need to enter the license owner's parameters. Then, choose whether you want to associate the software license with a computer (description of this computer will be specified), or with an available HASP dongle (a list of available HASP dongles will be displayed).
  • For license recovery:
    • If key parameters of the computer associated with the license did not change, select the I am sure the key computer parameters have not been changed check box.
    • If key parameters of the computer associated with the license did change, clear the I am sure the key computer parameters have not been changed check box. Then, enter the extra (unused) kit PIN code in the Extra PIN field.
    • Check registration data of the license owner and select association with a computer or a HASP dongle.
  • The license is activated for all users on the computer. If the user on whose behalf the license is being activated cannot write to a directory that is available to all users, the application will notify you and prompt you to activate the license only for the current user.
  • To acquire a license on an external storage device:
    • Create the license request file
    • Obtain a license from the Licensing Center
  • When you obtain a license manually please:
    • Read to the Licensing Center operator the digits that are displayed in the wizard window (48 digits).
    • Enter the software license data read by the Licensing Center operator into the special field (120 digits).

NOTE. Remember that when you download a file from the Licensing Center, the settings (information about the software product and the license owner) specified in the License Activation dialog should be exactly the same as when you created License request file.

When activating licenses, remember:

  • If the initial activation of the software license was carried out via the Internet or on an electronic media, the reactivation and renewal of the license is possible only via the Internet or on the electronic media.
  • If the initial activation of the software license was performed manually by phone, then reactivation and renewal of the license is possible only manually by phone.
  • If you want to activate an additional client software license on a computer, on which the software license is already activated, do so exactly as you did with the first software license on this computer.
  • When you re-obtain or update a license, move the file with the current license (for this PIN-code and serial number) to a directory that is not used by the 1C:Enterprise application for software licenses search. Otherwise, the new (and already existing) license will be blacklisted and cannot be used.
  • If you are activating a server and a multi-user software license and it is possible to run Designer on a computer with the 1C:Enterprise server installed, then complete the activation of both licenses from the computer, on which the 1C:Enterprise server is located.
  • Network devices and external storage devices that are connected through the USB and IEEE 1394 interfaces are not considered during verifying the license file binding to this computer.

    However, while you obtain a media license, when requesting the Licensing Center to obtain a license and creating the license file by using a Licensing Center response, the computer settings must coincide with devices settings connected by USB and IEEE 1394. If this requirement is not met, you will receive an error message when downloading the response file from the Licensing Center in the license obtaining dialog box: Licensing Center response does not match the license or owner data you entered. Check the kit registration number, PIN code and license owner information. To complete license activation in this case, you must return the computer configuration to the state when the license request file was generated, for example, insert the same external drive into the USB port, and then repeat loading of the same License Center response file. After that, the external drive can be removed.

    If you cannot restore your computer settings, you will need to re-obtain the license using an additional PIN code.

  • Before re-activating the license for the previously used PIN code, or for a new PIN code from the same kit, you need to ensure that there are no 1C:Enterprise applications in the local network using the previously obtained license file with PIN code from the same kit.

The activated software license file consists of two sections. The starting section stores parameters of the activated license and parameters of the associated object. This information is encrypted. The final section stores the same information in human-readable format. Parameters of the associated object can be displayed in shortened form. The human-readable information does not affect the license validity in any way. It can be edited freely.

You should not store one software license file at the same time in several different directories available to 1C:Enterprise applications. This may cause the license file to become unusable due to violation of the license agreement. In this event, a text description of license invalidation reason might be written to the beginning of the license file.

When you automatically receive a software license file, this file is located:

  • For a computer with 1C:Enterprise server:
    • On Windows: in the %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses for Windows Vista and later) directory of the user on whose behalf the 1C:Enterprise server runs.
    • On Linux: directory /var/1C/licenses.
  • The current computer will be asked, to whom the obtained license can be available:
    • If the current user is selected, the file will be placed in the directory:
      • On Windows: %USERPROFILE%\Local Settings\Application Data\1C\1cv8\conf (%LOCALAPPDATA%\1C\1cv8\conf for Windows Vista and later) of the user on whose behalf the license is being obtained.
      • On Linux: ~/.1cv8/conf (~  home directory of the user on whose behalf Designer is running).
    • If all users are selected, the file will be placed in the directory:
      • On Windows: %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses for Windows Vista and later) data directory for all users of the computer.
      • On Linux: this option is not supported.

%ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses for Windows Vista and later) and /var/1C/licenses directories are created during the application installation to the computer (in the corresponding operating system). Consider the following features related to these directories:

  • On Windows: write and read rights to the created directory are given to the user on whose behalf the 1C:Enterprise server runs (selected in the application installation window, see page ). If you do not select the Install 1C:Enterprise Server as a Windows service check box, the rights to the created directory are not assigned to anyone and they remain in the default option.
  • On Linux: during the installation, a group grp1cv8 is created, which must include all user accounts on whose behalf the 1C:Enterprise servers run in daemon mode. In this case, rights are assigned to the created directory as follows:
    • Directory owner: root. Rights: read and write (rwx).
    • Owner group: grp1cv8. Rights: read and write (rwx).
    • Access rights of other users: read only (r-x).

10.3.6.2. Activation guidelines

It does not make sense to activate a multi-user software license on a client computer (in any type of the infobase).

NOTE. A client application running on Linux allows you to activate a license that is available to all users only if the activation is performed on behalf of the root user.

10.3.7. Location of software licenses files

A software license is a file with a .lic extension that can locate in different locations of the file system.

TIP. You should not store one software license file at the same time in several different directories available to 1C:Enterprise applications. This may cause the license file to become unusable due to violation of the license agreement.

The software license is obtained as follows:

  • A list of software license files is generated for all directories where software licenses may locate.
  • For each file in the list, the required license (client or server) is obtained before the license is received or before the list of software license files is prepared.

10.3.7.1. On Windows

In Windows, software license files can be located in the following directories (directories are listed in the search order):

  • Directory of configuration files for a specific platform version. By default C:\Program Files\1cv8\A.B.C.D\bin\conf.
  • %USERPROFILE%\Local Settings\1C\1cv8\conf (%LOCALAPPDATA%\1C\1cv8\conf for Windows Vista and later) directory of the user on whose behalf the application runs.
  • The directory specified in the Conf.cfg file that is located in the bin\conf directory of the specific version. For details on conf.cfg file format, see page .
  • %ALLUSERSPROFILE%\Application Data\1C\1cv8\conf (%ALLUSERSPROFILE%\1C\1cv8\conf for Windows Vista and later) data directory for all users of the computer.
  • %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses for Windows Vista and later) data directory for all users of the computer.
  • %ALLUSERSPROFILE%\1C\licenses (%ProgramData%\1C\licenses for Windows Vista and later) data directory for all users of the computer.

If no license was found in any of these directories, the %APPDATA%\1C\1cv8\ directory is used for search. If there is a location.cfg file in this directory, the directory specified in the location parameter (see page ) will be used for the search.

10.3.7.2. On Linux

In Linux, software license files can be located in the following directories (directories are listed in the search order):

  • The conf directory of a specific 1C:Enterprise version:
    • 32-bit version: /opt/1cv8/i386/A.B.C.D/conf
    • 64-bit version: /opt/1cv8/x86_64/A.B.C.D/conf
  • The conf directory of the root installation directory: /opt/1cv8/conf.
  • Directory ~/.1cv8/conf (~  home directory of the user, on behalf of which 1C:Enterprise operates).
  • The directory specified in the conf.cfg file that is located in the conf directory of the specific version. For details on conf.cfg file format, see page .
  • Directory /var/1C/licenses.

If no license was found in all of these directories, the ~/.1cv8/1C/1cv8/ directory is used for search. If there is a location.cfg file in this directory, the directory specified in the location parameter (see page ) will be used for the search.

10.3.7.3. On macOS

In macOS, software license files can be located in the following directories (directories are listed in the search order):

  • conf directory of the installed version. The path to this directory will be as follows: /opt/1cv8/A.B.C.D/conf.
  • Directory ~/.1cv8/conf (~  home directory of the user, on behalf of which 1C:Enterprise operates).
  • The directory specified in the conf.cfg file that is located in the conf directory of the specific version. For details on conf.cfg file format, see page .
  • Directory /var/1C/licenses.

If no license was found in all of these directories, the ~/.1cv8/1C/1cv8/ directory is used for search. If there is a location.cfg file in this directory, the directory specified in the location parameter (see page ) will be used for the search.

10.4. Determining if 1C:Enterprise can run

10.4.1. When you start the client application

When starting 1C:Enterprise checks the possibility of running by the following algorithm (if at any step the necessary license is found, further search stops):

  • On computer with the client application:
    • An attempt is made to obtain a license from the same type of software license file or HASP dongle (series, network, or local), from which the license was obtained during the last successful connection (see page ).
    • Search for software licenses is performed on the local computer
    • Search for local HASP key is performed
    • Search for multi-user HASP key available with the HASP License Manager is performed.
    • If the configuration is basic, the client application searches for the base version license on the local computer.
  • On the cluster manager computer to which the session data service is assigned:
    • An attempt is made to obtain a license from the same type of software license file or multi-user HASP dongle (series, network, or local), from which the license was obtained during the last successful connection (see page ).
    • Search for software licenses on the computer of the 1C:Enterprise server cluster manager is performed
    • Search for multi-user HASP keys installed on the computer of the 1C:Enterprise server cluster manager is performed
    • Search for multi-user HASP key available with the HASP License Manager is performed.
  • On the cluster manager computer to which the Licensing Service is assigned:
    • An attempt is made to obtain a license from the software license file, from which the license was obtained during the last successful connection (see page )
    • Search for software licenses on the computer of the 1C:Enterprise server cluster manager is performed

If the search for the HASP dongle is disabled (UseHwLicenses=0) using the 1cestart.cfg configuration file (see page ), it does not search for available licenses in the HASP dongles located on the client computer (both local and network) and does not attempt to obtain a license from the saved dongle.

10.4.2. When you start the server

When connecting a client application with the 1C:Enterprise server, the server license is checked (if the necessary license is found at any step, further search stops):

  • Search for a license on the working process computer that supports a connection to the infobase is performed:
    • An attempt is made to obtain a license from the software license file or HASP dongle, from which the license was obtained during the last successful connection (see page ).
    • Search for a 32-bit server software license (only for a 32-bit 1C:Enterprise server) is performed
    • Search for the 64-bit server software license is performed;
    • Search for the 32-bit server local key (see page ) (only for a 32-bit 1C:Enterprise server) is performed
    • Search for the 64-bit server local key is performed (see page )
  • Search for license on the cluster manager to which the Licensing Service is assigned is performed:
    • An attempt is made to obtain a license from the software license file, from which the license was obtained during the last successful connection (see page )
    • Search for a 32-bit server software license (only for a 32-bit 1C:Enterprise server) is performed
    • Search for a 64-bit server software license is performed.

10.4.3. Actions when a license is not found

If no licenses are found during the search (described above), the following steps are to be performed:

  • Designer, thin and thick clients run the software license acquisition wizard.
  • The web client generates an error message:
    • License not found. No software dongle or electronic license found.
    • License on 1C:Enterprise server is not found. No software dongle or electronic license found.
  • If you refuse to acquire a software license, Designer, thin and thick clients also generate the above error messages.
  • If you click Details in the error window, the Key search history window opens. This window provides information about where the license search was performed, the status of the search (successful or failed), and the reasons for the failed search. This log can make it easier to diagnose license issues.

10.5. Protection against misuse of applications

10.5.1. General information

When purchasing a license for the main delivery of any application, the user receives the distribution packages of the platform and of the configuration specified in the license of the current (at the time of purchase) versions.

For later versions of this configuration, as well as for other configurations with different names, rights are generally not granted automatically. This means that the user must ensure the proper registration of the acquisition of rights for the updated configurations.

The purpose of this mechanism is to inform the user in a timely manner about the actual use of certain versions or releases of the configuration that he/she does not have rights to, and related with these potential legal risks.

The situations when certain versions of the configuration may be used in violation of the rules established by the copyright holder are:

  • The user does not have a license for the main delivery of this configuration type.
  • The user obtained a license for the main delivery of the configuration of this type, but later updated the configuration in violation of the rules established by the copyright holder (for example, the user tries to use versions/releases issued after the expiry of the ITS (information &amp; technology servicing) service period). For information on the conditions of servicing, visit 1C:ITS Portal (https://portal.1c.ru/app/update).

Verification of use is performed for the applications deployed in a file mode or client/server mode using the MINI server (more information about the MINI is available at https://1c-dn.com/news/1c_enterprise_8_server_mini_is_available_at_1c_dn_com_online_store). If you operate an application that uses a basic license, no verification is performed. The verification uses the information about the application and the account information created during the registration of the application and servicing agreement on the 1C:ITC Portal (hereinafter the license client term will be used). If the application is used incorrectly, it periodically forms a dialog containing information on the reasons for the misuse of the application. Information about the results of the check is also displayed in the About application dialog box.

When loading the infobase from the *.dt file, verification of application is not performed.

10.5.2. Mechanism structure

After the database configuration update is complete, the 1C:Enterprise application submits a request to the Licensing Center (hereinafter referred to as the LC), specifying information about the application. License client data is used to personalize the request.

In case of successful completion of the request, the LC restores the legal status of use of this application for the specified license client. If the LC does not confirm the legal use of the application, the 1C:Enterprise application starts informing all infobase users that the application is used illegally, and the information obtained from the LC is displayed.

About dialog box contains information on the results of the request to LC:

  • License usage verification was not performed. This means that the 1C:Enterprise application was not yet able to connect to LC to verify whether the configuration is legitimate.
  • License usage verification completed. This means that the 1C:Enterprise application contacted the LC to verify the legitimacy of use and received confirmation that the application is being used legally.
  • Unlicensed use of the configuration. Illegal use of application.
  • Licensing Center unavailable. 1C:Enterprise application cannot access the LC.

License client data (used to contact LC) must be included in the infobase of the application used. You can set the settings from the Designer by using the Main menu – Administration – Set the licensing client settings command. When accessing the LC, in the 1C:Enterprise mode, a similar dialog box will be displayed in case the license client data is not defined for the infobase by the time of the request.

The application developer can implement its native licensing client data installation mechanism (using the SetSettingsofLicenseClient() method), for example, by getting them during the initial application setting. At the same time, the developer can implement a response of the platform to the license client data request and provide the user with a more convenient dialog box for entering the license client settings (using the ConnectHandlerofRequestforLicenseClientSettings(), in which the dialog box opens).

<< Prev   Next >>