Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor changes to 'Release' section

...

LDAP configuration information is stored out in the [main] section of the JOC Cockpit's shiro.ini file, whose overall configuration is described in the Authentication and Authorization - Configuration article. A general introduction to authentication and authorization with JOC Cockpit is provided with the JOC Cockpit - Authentication and Authorization article.

LDAP configuration can only be edited by system administrators using a text editor to update the shiro.ini file. There is no web-based editing feature available.

A restart of JOC Cockpit is not required after changing changes are made to the shiro.ini configuration file either by using the JOC Cockpit Account Manager or a text editor.

Release 1.12.1 and Newer

...

  • All authentication and authorization information is stored in the Reporting database.
  • A form based editor which users can use to configure LDAP authentication is available in the JOC Cockpit. This editor is only available for users with the necessary permissions such as the default root user with the all role and . This editor is accessed via the "Manage Accounts" menu.
  • Automatic import and backup functions for the authentication and authorization information are available. Both the import and backup functions use Shiro files and are triggered by :
    • The import function automatically imports a file named shiro.ini to the Reporting database and the contents of this file will overwrite the authentication and authorization information in the Reporting database.
    • The backup function automatically stores the authentication and authorization information in a file named shiro.ini.active. At the same time an existing shiro.ini.active file will be renamed shiro.ini.backup and any already existing file with that name will be overwritten.

...