How does JON integrate with external LDAP user repositories?
JON uses passwords to authenticate users. Authentication information, comprising user names and passwords, can be stored in an internal database (the default) or in an external LDAP repository. It is important to note that support for LDAP currently does not include storing attributes other than user names and passwords. In particular, authorization information such as roles used to control access to JON resources is persisted in the internal database. • Configuring JON to use LDAP for authentication • In order to configure JON to use LDAP for authentication, navigate to the Server Configuration page (Dashboard->Administration->Server Configuration). The following configuration parameters can be specified: • URL of the LDAP server: This defaults to ldap://localhost on port 389 (or port 636 if the SSL option is selected). • Username/Password: The username and password to connect to the LDAP server. The username is typically the full LDAP distinguished name (DN) of a manager user, e.g. “
JON uses passwords to authenticate users. Authentication information, comprising user names and passwords, can be stored in an internal database (the default) or in an external LDAP repository. It is important to note that support for LDAP currently does not include storing attributes other than user names and passwords. In particular, authorization information such as roles used to control access to JON resources is persisted in the internal database. • Configuring JON to use LDAP for authentication • In order to configure JON to use LDAP for authentication, navigate to the Server Configuration page (Dashboard->Administration->Server Configuration). The following configuration parameters can be specified: • URL of the LDAP server: This defaults to ldap://localhost on port 389 (or port 636 if the SSL option is selected). • Username/Password: The username and password to connect to the LDAP server.
JON uses passwords to authenticate users. Authentication information, comprising user names and passwords, can be stored in an internal database (the default) or in an external LDAP repository. It is important to note that JON support for LDAP currently does not include storing attributes other than user names and passwords. In particular, authorization information such as roles used to control access to JON resources is persisted in the internal database. • Configuring JON to use LDAP for authentication • In order to configure JON to use LDAP for authentication, navigate to the Server Configuration page (Dashboard->Administration->Server Configuration). The following configuration parameters can be specified: • URL of the LDAP server: This defaults to ldap://localhost on port 389 (or port 636 if the SSL option is selected). • Username/Password: The username and password to connect to the LDAP server. • Search Base: Base of the directory tree to search for usernames and passwords while
