This variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. can be used to define whether automatic logon (Single Logon) is allowed.
Key |
Value |
New start required |
---|---|---|
WinNT |
AUTO |
No |
UNIX |
AUTO |
No |
LINUX |
AUTO |
No |
Call |
AUTO |
No |
This variable is supplied in clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. 0000. Its settings are valid for the whole AE system and can only be changed in client 0000.
Access to the operating system is granted via the specification a valid userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. ID and passwordA secret combination of characters for a Automation Engine user.. Logging on to the AE system is not required if the variable UC_USER_LOGON is used. In this case, the system checks if a User objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task exists in the client and if so, logon is automatic. Otherwise the UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]'s loginAn Automation Engine object type that stores account credentials used by agents on target systems. window opens.
When Single Logon is enabled, access control is shifted to the UserInterface's OS. Unattended screens can become a security risk and must therefore be avoided using the means of the relevant operating system.
Single Logon can be used for CallAPIs. The benefit is that the password does not have to be stored in programs or procedures. Therefore, it is not required to change every time the password is changed.
The following steps are required to activate Single Logon:
Description |
|
---|---|
-Cclient |
For Windows and UNIX or Linux: The user nameName of the Automation Engine user. is taken from the operating system. The system then searches an AE user with that name. The departmentDepartment name to which the Automation Engine user belongs. is not taken into consideration. There can only be one user with this name, regardless of the department. If the user is found, logon is accepted without password verification. |
-Dclient |
Alternative parameter for -C under Windows: The user name is taken from the operating system. The particular Windows domain is used as the department. If the user is found, logon is accepted without password verification. |
-SAE system or connection name |
It is crucial to indicate the name in order to enable automatic logon because there can be more than one AE system. The login window is displayed if this parameter is missing. You can also enter the connection name which is specified in the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. fileuc4config.xml, XML element <connection name="Name" system="System"> instead of the AE system nameName of the Automation Engine instance to which a user is connected.. |
See also:
Overview of all variables
in table form
Variable
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |