| Home Prev |  InCenter 2.2.5 On-Premises Administration Guide
|
Next |
|---|
The InCenter WebUI is a graphical interface that allows interaction with the InCenter server through a standard web browser. It can be used for performing a range of administration and monitoring tasks.
The WebUI cannot fully replace all the InCenter CLI functions. However, it can perform a subset of CLI capabilities and provides node monitoring capabilities that are not possible with the CLI.
Controlling WebUI Access
The InCenter server has WebUI access enabled by default. Controlling WebUI access and changing the WebUI access settings is done using the InCenter CLI and is described in Section 3.3, WebUI Access The interface language used in the InCenter WebUI comes from the default language used in the web browser, but will only change from English if the browser's language is available in InCenter. Currently, the languages available in InCenter are:English (abbreviation: "en").
Japanese (abbreviation: "ja").
The WebUI language cannot be changed once the interface has opened. To switch language, the WebUI should be closed, the browser's default language changed and then the WebUI reopened.
Alternatively, the language can be selected by adding the parameter:
lng=<language-abbreviation>to the URL that opens the initial login page (it will not change the language mid-session, after login). The possible <language-abbreviation> values are given in the preceding language list.
For example, to open the login dialog in English:
https://<InCenter-URI>/overview?lng=en
To open the login dialog in Japanese:
https://<InCenter-URI>/overview?lng=ja
Note that once the WebUI is opened with a particular language, it will open for the next session with that same language if no language parameter is specified in the URL. The language can only be changed by explicitly specifying the language parameter at the end of the URL.
The WebUI is available through any modern web browser. The only prerequisite is that the browser can access the InCenter server using HTTPS.
Connecting to the WebUI
After opening a browser, the InCenter WebUI is started by entering the IP address of the InCenter server in the browser's navigation field.The IP address used for browser access is the same as the IP address used for InCenter SSH access and is displayed on the InCenter server console when it is started. Access is always using HTTPS and, like SSH access, the login credentials must match a previously defined user. The only user that is predefined in InCenter is the principle administration user that has the username admin.
An Exception Must Be Made for the Server Certificate
On initial connection, InCenter will send a self-signed certificate which the browser will not recognize. A security exception for this certificate must therefore be confirmed in the browser before the WebUI interface will be displayed. This only needs to be done once, unless the exception is removed from the browser later.The self-signed certificate is predefined in the InCenter server. However, it can be replaced by the administrator with any other suitable certificate. It is recommended to use a certificate that matches the server's FQDN.
Logging In
After successful connection to the InCenter server, a login dialog will be displayed in the browser, as shown below.The predefined administrator user on a freshly installed system has the following default credentials:
Username: admin
Password: admin
Note that the second time the administrator logs in with these credentials, they will be prompted to change the password to one that conforms to the system's password policy settings. The password policy is explained further in Section 9.3, User Password Policy.
If Multi Factor Authentication (MFA) is enabled in InCenter, the login dialog shown above will have an extra option to login using MFA. This is discussed further in Section 9.4, Setting Up MFA.
The Overview Page
After successfully logging into the WebUI, the Overview dashboard is displayed which provides a graphical summary of activity for all the nodes currently communicating with InCenter. An example is shown below.If no nodes have been added previously, the first step a new administrator will probably want to take is to add one or more InCenter. Doing this is described in Section 6.3.1, Adding NetWall Nodes with the WebUI
