Token
A token can be used to start a new session. This is always permanently assigned to a user. The ID of a token is randomly generated and always has 64 characters. The strength of a token is thus fixed at 384 bits.
Tokens can be automatically created by the system when the user interacts accordingly. This behavior is normal. For example, if a user resets their password, a token will be sent via email.
Security: Please pay close attention to where you store tokens. Access to a token automatically grants access to the system for anyone.
Types
There are different types of tokens with various functions. See the following table for details.
Note: Changing the type does not automatically adjust the session. The token would need to be used again for this purpose.
| Symbol | Type | Description |
|---|---|---|
| Do Not Save Login Data | Static token. This creates a new session. The token remains unchanged and is retained. | |
| Save Login Data | Saves the login data via token for a maximum of one year. The expiration time is automatically extended when the user uses the visualization. This token does not work in Antcas Control. | |
| Log In Once | Deletes the token immediately after logging in. The session remains active until the user logs out. | |
| Synchronized With Session | The session is linked to the token. The expiration of the token or its deletion also ends all connected sessions. | |
| Synchronized With Antcas Control | If a system session is active, this token can be created instead of the one above. It will then automatically log in when Antcas Control is used. However, the session is not terminated upon logging out from the editor. | |
| Synchronized With Antcas Cloud | The session is synchronized with the Antcas Cloud. This is used for automatic login via the cloud. When changing a password, this token is automatically removed. | |
| Set Password | Set a new password. A dialog window appears after login and forces the user to set a new password. |
Using Tokens
To use tokens, the token ID must be appended to the server URL (see Hostname) and the visualization port. The ID is visible in the configuration by double-clicking on a token and can be easily copied.
https://hostname:8000/de-ch/?token=TOKEN_ID
Tip: You can also create tokens in the PLC. See Function Block INVITE_USER and RESETPWD_USER for details.
Sending Tokens
When a token is sent, for example via email or chat, it can be deleted by a scanner before reaching the user. Therefore, there is an option to prevent this behavior using an additional parameter. The URL must be extended with &link=send for this purpose.
https://hostname:8000/de-ch/?token=TOKEN_ID&link=send
This means that an additional intermediate step is called in the browser to remove the token.
Note: This method has no effect on the API.