9.3. Configuring Login-related Access Settings

Engineering Knowledge Manager

Installation Guide | Chapter 9: Configuring Login Authentication and Access Settings |

9.2. How User Logins Work |  | 9.4. LDAP Mapping
Prev |  | Next

## 9.3. Configuring Login-related Access Settings

After you have configured the login module, as described in Configuring Login Authentication, you can proceed with specifying the following settings in the EKM_HOME/conf/ekm.xml file:

Table 9.2: Login-related Access Settings

| What it means | How it is specified
--- | --- | ---
Default workspace | The workspace to which all users will connect at login. [a] | Defined in the `defaultDomain` setting in the ekm.xml file. For more information see Specifying the Default Workspace (<defaultDomain>) in the Administration Guide. [b]

Designated Root User

The only user who will be able to perform restricted configuration on EKM workspaces.

The designated Root User is specified during installation, but can also be specified or changed later.

The EKM user name defined in the `defaultRootUser` setting in the ekm.xml file will be the designated Root User for all defined workspaces. See Specifying the Default Root User (<defaultRootUser>) in the Administration Guide.

The `defaultRootUser` setting can be overridden for a specific workspace. See Designating a Root User for a Workspace in the Administration Guide.

Important: The value specified for the Root User must always be an EKM user name, and must match the EKM user name exactly. The concept of EKM user names is described in How User Logins Work.

RSM Windows domain (If jobs will be submitted to a Windows cluster submit host) | This is the Windows domain name that will be prepended to the user name of all EKM users when batch jobs are submitted to RSM. All user jobs will be submitted to RSM as `rsmWindowsDomain value`\`OS account name`. | An RSM Windows Domain setting is specified during the installation of an EKM server. The value can be modified in the `rsmWindowsDomain` setting in the ekm.xml file. For more information see Specifying Remote Process Policies (<remoteProcess>) in the Administration Guide.

[a] It is possible for users to log in to other workspaces through the use of cookies, bookmarks, and so on.

[b] In order for users to be able to log in to the default workspace, the workspace must meet one of the following criteria:

- It must have automatic account creation enabled (see Creating User Accounts Automatically in the Administration Guide)

- If automatic account creation is disabled, user accounts must be manually created (see Adding and Modifying Users in the Administration Guide)

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.