|
LDAP
OMERO LDAP AuthenticationLDAP is an open standard for querying and modifying directory services that is commonly used for authentication, authorization and accounting (AAA). OMERO.server supports the use of an LDAP server to query (but not modify) AAA information for the purposes of automatic user creation. This allows OMERO users, ''Experimenters'' or ''Scientists'' in OMERO parlance, to be automatically created and placed in groups according to your existing institution policies. This can significantly simplify your user administration burden. The OMERO.server LDAP implementation can handle a number of use cases. For example,
LDAP PropertiesThe LDAP plugin is configured via several configuration properties, all starting with "omero.ldap.". The default values for these properties is set in the file etc/omero.properties.
These properties are the base requirements for logging in to LDAP. After having configured your connection, you can turn the LDAP on and off between restarts by setting "omero.ldap.config" to false.
These two user properties are used to look up users by login name and, if necessary, create new users based on the information in LDAP. "omero.ldap.user_filter" will be AND'ed to the username query, and can contain any valid LDAP filter string. The username query is taken from the LDAP attribute which gets mapped to "omeName" by "omero.ldap.user_mapping". Here, the "cn" is mapped to omeName, so the username query is
The final set of properties are all concerned with what groups a user will be placed in on creation. The group filter and group mapping work just as the user filter and mapping do, but may not be used depending on the value of "new_user_group", which can have five separate meanings:
LDAP ConfigurationLike many pieces of OMERO.server configuration, LDAP-specific configuration is done by specifying extra properties during installation. The default values for the LDAP properties are listed in the etc/omero.properties file inside your OMERO installation directory. NOTE: Please remember that once a change has been made, a server restart will be needed. Change any settings that are necessary via bin/omero config.
LDAP over SSLIf you are connecting to your server over SSL, that is, if your URL is of the form "ldaps://ldap.example.com:636" you will need to configure a key and trust store for Java. See the Security page for more information. See also
If you have LDAP requirements that are not covered by the above configuration, please see the forum discussion "What are your LDAP requirements?" Document Actions |