In order to login into the TimeKeeper Web UI, you will need to know the IP address, as well as your Username, and Password (defaults are provided below).
If VelaSync is connected to your network, the unit will likely have been assigned a static IP address by you or a co-worker (see Configuring IP Address(es)).
If VelaSync is NOT yet connected to a network, and you want to access TimeKeeper in order to change the IP address, you can use the unit's factory default IP address for the Ethernet port you have chosen. The IP address for ETH0, for example, is 192.168.1.1. (For the other IP addresses, see Rear Panel Overview.)
- Using a computer that is connected to your VelaSync unit, open a web browser, and enter the IP address of your VelaSync unit into the address field. The TimeKeeper Login window will appear:
- Enter Username and Password (the default Admin Username is "admin", the password is "fsmlabs").
Note: For safety reasons, it is recommended to change the default Username and Password immediately (login via https, then navigate to Configuration > Service & System Management: Manage TimeKeeper).
The TimeKeeper Status page will be displayed:
For more information on https support, see HTTPS Support.
Logging in as Admin will allow you to manage all aspects of the system, including visualization, service management, configuration, and other supported options. For a more limited login, refer to the next section on the Readonly and Loguser users.
Authentication of the web login is handled based on how the unit is configured:
- Since VelaSync is used as a server—rather than a client—, by default the TimeKeeper authentication and password control is local to the system “admin” account.
Note: TimeKeeper can also be run as a client, when installed on NTP/PTP client computers. In these cases authentication is internal to TimeKeeper.
- If RADIUS or TACACS+ is enabled, authentication is handled by the configured servers. Should authentication via TACACS+ or RADIUS fail (such as during a network outage), the provided password will be tested against the local system account.
Note: For “admin” to be authenticated via RADIUS or TACACS+, the authentication server must have an account named “admin” with matching credentials.
A VelaSync TimeKeeper upgrade will detect that there is a need for a local system “admin” account for authentication, and consequently will add this account. As a precautionary measure SSH will be disabled, so as to prevent unauthorized logins with the default "admin" password, until this password can be changed to something unique. SSH access can then be re-enabled via the Web UI.
Note: Upgrading from TimeKeeper Version 6.3.12 will require web login with the default credentials of “admin” and “fsmlabs”. The password can be set as before via the Web UI.
More limited user accounts are also available with the Readonly and Loguser accounts. Both can be configured by the Admin user via the Web UI. Both types of accounts can log in and review TimeKeeper data, but cannot reconfigure or manage the system. On VelaSync, both accounts are identical.
If RADIUS or TACACS+ is enabled, any user that can authenticate with the configured server that is not named Admin will be logged in as the Readonly role with reduced capabilities.
By default, the Readonly and Loguser accounts are present but not configured and cannot be used.
To configure either account:
- Log in as Admin.
- Navigate to Configuration > Service & System Management. The Set readonly [loguser] password button will allow you to configure a password, which will be named “readonly” or "loguser", respectively.