User Data (ttams1100s000)

The Tools user code is normally similar to the user code specified in the Доступ в систему field. However, you can specify more than one Tools user for one system logon.

When a user starts the bshell, by default the system starts with the Tools user code that is equal to the system logon code. You can start the bshell with a different Tools user code by setting the User environment variable.

Пример

If the user with the system logon dave starts the bshell, by default he will be user dave in Tools. The user dave can fill the environment variable User with dave_01 or dave_02, to start as another Tools User.

If the user with the system logon dave sets the environment variable USER to john or john_01 and tries to start the bshell, the message Not authorized to run as user john appears. In the same way, UNIX user john can only start the bshell as Tools User john or john_01, but not as dave, dave_01 or dave_02.

You can leave the SSO User field empty. In that case the value of the Доступ в систему field is used during the Convert to Runtime. The Infor SSO User must be unique; for example, an Infor SSO User can only be specified for one LN user.

During the convert to runtime this field is dumped into the u<user> file with the sso_user tag.

Also a $BSE/lib/user/sso/s<SSO_USER> file, that contains the Application User name, is created. The format is baanuser:<baan user name>. This file is used by the Bshell to make the mapping from SSO user to Application User.

To prevent that an end user can tamper with the configuration to get more credentials, an extra file $BSE/lib/sso.permissions is introduced for BLogin. This file contains the permissions for SSO users to impersonate a certain OS user. The file is to be maintained by the system administrator and must only be writable on OS level by the system administrator. It must be considered as having the same security status as for example the OS password file. If this file does not exist, BLogin refuses to handle SSO requests.

The Использовать типового системного пользователя field is enabled if the Разрешается переопределение системного пользователя check box in the Параметры SSO (ttams0100m000) session is selected.

Before installing Tools, a number of system logons have to be created by the system manager by using a system administration program.

Tools checks if the logon code specified in this field exists in the password file. If not, a warning appears.

Note that the System Login field will be disabled when the Use Generic System User field is checked. This is the case when SSO is activated. The value of the displayed Generic System User field will than be used during Convert to Runtime.

Access to a company is only possible if the package combination of the Tools user and company are the same.

A role contains personalization settings, such as session personalizations and menu personalizations.

A role-enabled user has one current role and can have multiple roles assigned. If multiple roles are assigned to a user, the user can switch between these roles.

See Multilanguage application data.

You create the template in the Шаблон параметров разработки (ttams1150m000) session.

Пример

A manager must have the same authorizations as his staff in the organization, in addition to his own authorizations.

If this check box is cleared, the developer is only authorized for the package VRC that is specified in the Шаблон авторизаций разработчиков (ttams1151m000) session.

A textgroup authorization template must be specified for a normal user, otherwise the user is unable to read or write text in Tools.