To access the Interface, you must point your Web Browser to the URL provided during installation.
This chapter explain how to configure the Visualization UI
The UI can be now protected by an HTTPS access.
In the webui.cfg,
| The files default files /etc/shinken/certs/server.cert and /etc/shinken/certs/server.key are just samples that are provided with the installation and MUST be changed by your own certificates. |
Accessing to the UI will still use the default dedicated port 7766 (but in HTTPS).
You must Sign in to access the Administration Tool :
If Shinken is connected to an active directory, please use your usual active directory account (without the DOMAIN\ part). You can also use your active dorectory email address as your login. |
If an error occurred (wrong login or password), you will be prompted again |
Edit the auth_active_directory.cfg in /etc/shinken/modules:
| Property | Example | Description |
|---|---|---|
| ldap_uri | ldaps://myserver | The address of the Active Directory server. |
| user | user | The user name to connect to the lapd server |
| password | password | The password |
| DC | DC =google,DC=com | Base OU for the users. |
Edit the webui.cfg file in /etc/shinken/modules
| Property | Example | Description |
|---|---|---|
modules | Cfg_password, auth-active-directory, Mongodb, webui-enterprise, sla | By default, auth-active-directory should be present in the line. If missing, add it to activate the module. |
| It will first try to identify the login/pass provided in the via the active directory module, then check in the synchronizer database, and then reject it if not found or valid. |