Administration Guide > Encryption > Specifying the Authentication Method for the First Time

Specifying the Authentication Method for the First Time

During AE system installation, you can determine the authentication method to be used in your AE system. The utility AE.Load automatically adds the selected option to the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_AS_SETTINGS, key AUTHENTICATION.

Selecting the Authentication Method

UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] installation:

Setup installation:

Updating an AE system to version 8.00A or later:

Agent Installation

Agent installation depends on the selected authentication method.

None:

  1. Install the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host with the UserInterface or use the installation guide.
  2. Start the agent.
  3. An Agent objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task is automatically created in system 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.
  4. Log on to system client 0000 and assign the required client authorizations in the agent object if you do not use automatic client assignment.

Server:

  1. Install the agent with the UserInterface or use the installation guide.
  2. Log on to system client 0000 and export the Company Key via the System OverviewThe UserInterface window that contains information about the Automation Engine system.. Highlight the node for the client 0000 connection in the tree structure and use the context menu command "Export company".


  3. Transport the file containing the Company Key to all agents. 
  4. Enter the path and the name for the Company Key file in the agent's INI-file parameter InitialPackage= (Section [AUTHORIZATION]).
    In the parameter KeyStore=, enter the path and name of the file in which the agent should store the Company Key information.
    You must ensure that both files are stored in a separate protected directory.
  5. Start the agent.
  6. The agent reads the Company Key file and stores the acquired information in the KeyStore file. Then it deletes the original file.
  7. An Agent object is automatically created in system client 0000.
  8. Assign the required client authorizations in the Agent object.
  9. Release the agent in the System Overview using the context menu command "Authenticate Agent".

Server and agent:

  1. Install the agent using the UserInterface or refer to the installation guide.
  2. Log on to system client 0000 and create an Agent object. Its name must be the same as the one defined in the INI-file parameter name= (Section [GLOBAL]) .
  3. Assign the required client authorizations in the Agent object.
    The AE.ApplicationInterface can be used to create Agent objects and assign client authorizations very easily.
  4. Open the System Overview and highlight the agent. Open the context menu command "Export authentication packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components.".
    As of version 11, the actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios. "Export Authentication Package" has been restricted to users in the System client 0. Additionally a 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. needs the "W" permission for the Agent object to be able to export an authentication package.
  5. Transport the file containing the authentication package to the agent's computer.  
  6. Enter the path to the authentication package file in the agent's INI-file parameter InitialPackage= (Section [AUTHORIZATION]).
    In the parameter KeyStore=, enter the path and name of the file in which the agent should store the information acquired from the authentication package.
    You must ensure that both files are stored in a separate protected directory.
  7. Start the agent.
  8. The agent reads the authentication package file and stores the acquired information in the KeyStore file. Then the agent automatically deletes the authentication package file. 

See also:

Changing the Authentication Method

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH