Register a user in Workspace of SystemLink Server

Updated Sep 18, 2023

Reported In

Software

  • SystemLink Server

Issue Details

In SystemLink Server 2022 Q1, a function called Members has been added to the Edit panel of Workspace.
SystemLink21.png
  • Previously, users could only be registered from Workspace's role mapping, but is there any difference when using the member function to register users and set roles?
  • When registering a Windows account to SystemLink Server as a user, is there a way to register without logging in with that account?

Solution

Adding users from members and adding users from role mappings are functionally equivalent. In either case, only users who have logged in to SystemLink Server once can be added as domain-managed users, and users who have never logged in to SystemLink Server cannot be added.

To register a domain-managed user in SystemLink Server, you need to log in to SystemLink once with that user account. When you log in for the first time, the authentication required to register a user with SystemLink is performed, and the registration information as a SystemLink user is created. This is a Microsoft function and cannot be executed from an external application such as SystemLink, so domain-managed users must log in to SystemLink Server at least once.


User enrollment and role mapping in Workspace

Each Windows account can be set and checked by the user with access rights, and by entering the user name on SystemLink in the role mapping of each Workspace, it is possible to register to Workspace and set the role (authority). If a large number of users are logged in to SystemLink Server, the users who have logged in in the past will be displayed in the access privilege user screen. If you use the member function when registering to each Workspace, you can register while searching for these user information. However, even when registering users using the member function, each Windows account user must log in to SystemLink Server once.

There is no difference in the HTTP API used when registering users and setting permissions from Workspace role mapping as described above and when doing the same from members. However, there are some differences in the payload part. If you want to check the difference in the HTTP API that is executed in the background when you perform operations on SystemLink, you can check by using Google DevTool or Wireshark. In the case of this operation, the following differences can be confirmed. Although there is a difference whether the key is user or user-id, the behavior obtained as a result of the following is the same.
Comparison of user registration authority settings to Workspace.png

Additional Information