User authentication and authorization is available in the Enterprise delivery variant. Accounts and role model are controlled and configured on the server side in the "Access control" module. "Robin Player user".
After launching the application, the ROBIN Agent connection indicator should be green.
A green indicator indicates that ROBIN Studio or ROBIN Player is connected to the ROBIN Agent and the Agent is connected to the Orchestrator. When you move the cursor over the indicator, the corresponding prompt "Robin Studio is connected to Agent and Agent is connected to Orchestrator" will be displayed. If the indicator is red, there is no connection. In this case you should:
|
2. After clicking on the "Login" button, the prompt "Log in in the browser tab that opens" will appear. This will open the window of your default browser to continue the login process.
If you accidentally close the tab that opened, you can click the "Login" button again - it's always clickable, and clicking it again will open another tab in the browser to continue the login process.
3. If you have previously logged in to other applications on the platform, the browser tab that opens will display:
In this case, you do not need to perform credentials entry again. If the user has the Robin Studio user role, the System will automatically allow you to log in to Studio.
If you have not logged in to the System before or have already logged out of the System, you need to log in on the opened browser tab as described below.
ROBIN supports two user authentication options:
Logging in as an internal user
Logging in with an internal user account when there is no corporate Active directory collaboration configuration. In this case, the user login will be as follows:
a) First, the browser will display a window on the opened tab:
b) It should be skipped by clicking on the "Cancel" button.
c) The authorization page will open, where you must enter the login and password of the internal ROBIN user:
d) Click on the "Login" button.
Logging in as a domain user
Logging in under a domain user account is possible if the ROBIN platform has been configured to interact with Active Directory.
If Robin Studio has not received a response to its request and the timeout time has expired, the following message will appear in the "Login" window:
Need to try logging in again.
2. If the error "Insufficient rights to work" occurs when trying to log in:
The message means that the user has not been assigned a role to work with the corresponding application. In this case, it is necessary to assign it through the "Access control" module.