Authentication and encryption procedures #
The connection between the Designer and the Server can be established using different authentication and encryption methods.
The following combinations of transport encryption and authentication are available:
Note: To use Kerberos transport encryption or authenticate an Active Directory (AD) user, a Kerberos Target Principal Name (TPN) is required.
TPN can either be a User Principal Name (UPN) or a Service Principal Name (SPN). Further information on TPN can be found in the Knowledge Base Article How to use target principal field (TPN).
|Authentication Method||Description||TPN required|
|Windows credentials (current user)||The AD user, who runs the Designer authenticates himself towards the Server via Kerberos. All data exchanged between Designer & Server is encrypted using Kerberos.||x|
|Windows credentials (different users)||The AD user, whose user name and password are entered in the login window, authenticates himself to the XU server via Kerberos. All data exchanged between Designer & Server is encrypted using Kerberos.||x|
|Custom credentials (TLS encryption)||The custom user, whose user name and password are entered in the login window, authenticates himself to the Server. All data exchanged between Designer & Server is encrypted via TLS. To use TLS transport encryption, an X.509 server certificate is required for the Service (can be stored in the server settings. In the login window, the DNS hostname of the server for which the certificate is issued needs to be entered into the Server field.||-|
|Custom credentials (Kerberos encryption)||The custom user, whose user name and password are entered in the login window, authenticates himself to the Server. All data exchanged between Designer & Server is encrypted using Kerberos.||x|
|Anonymous (no encryption)||There is no authentication. The data exchanged between Designer & Server is transferred in plain text without transport encryption.||-|
Activating Authentication Methods #
The different logon options can be activated/deactivated in the Server Settings.
- Open Server > Settings from the main window.
- Select the tab Configuration Server.
- Activate or deactivate your authentication methods.
Users and User Groups #
The Designer offers Access Management for different users and user groups. You can use already existing Windows AD Users and Groups or create your own custom users and groups.
Note: Windows AD Users and Groups are created outside the Designer. Be careful to only add Windows AD Security Groups to the Designer. Users that are assigned to Distribution Groups are denied access at logon.
How to create a custom user and assign the created users to user groups:
- Navigate to Security > Manage Users.
- Click [Add] to create a new user. At the time of user creation, no rights need to be assigned. See also Access Management.
- Navigate to Server > Settings.
- Select the tab Configuration Server and check the checkbox Restrict Designer access to the following users/groups.
- Click [New] to create a custom user group.
- Navigate to Security > Manage Users.
- Click [Edit]. The “Create new user” window opens.
- Use the arrows [<] and [>] to assign and remove users to and from groups. Custom users can only be assigned to custom user groups. Windows AD users can only be assigned to Windows AD groups, but not to custom user groups.
Recommendation: It is advisable to assign users to groups and grant access to particular actions instead of adding single users and granting them access one by one.
Migration and Update #
As custom users can only be assigned to custom user groups and Windows AD users can only be assigned to Windows AD groups, the created custom user groups may disappear when migrating to a product newer version. This does not affect access management, but the access at user level is resolved.
To grant access at group level, the Windows AD users need to be assigned to newly created Windows AD groups.