| Warning |
|---|
After upgrading from a version prior to Datameer 6.3: If authenticating with Active Directory or LDAP, users executing jobs must be listed in the authenticator. For added security, executing jobs as a users not present in the authenticator is no longer possible. |
Overview
The LDAP and Active Directory authenticators available in Datameer provide remote authentication services for Datameer users. Administrators can configure Datameer to use their existing LDAP or Active Directory systems as the authenticator of record allowing for centralized management of user accounts and credentials outside of Datameer. Users can authenticate with Datameer using existing credentials which are verified against the remote system on every login. If the remote system no longer sanctions the user, access to Datameer is denied. This simplifies Datameer administration and allows end-users to use familiar single sign-on credentials when accessing Datameer.
| Table of Contents |
|---|
Users and Groups
When using the LDAP Authenticator, credentials are authenticated at the time of login directly against the remote service. In order for Datameer to manage authorization and object permissions, a Datameer user entity is required to represent the remote user. It useful to think of users being imported into Datameer from LDAP with the remote server always ensuring that users have valid, active credentials. For details on how to add users from LDAP, see Importing Users. When a user is imported into Datameer, a user entity is created using the remote unique identifier as the Datameer username and populated with other account details, i.e email address.
During import, Datameer creates groups based on the groups contained in the LDAP directory. This allows the use of existing LDAP groups for Datameer access control as the group memberships are mirrored across systems. The users' group memberships and user details are updated on every login to ensure that any changes to authorization policies in LDAP are reflected in every Datameer session. Since we rely on LDAP groups when the LDAP Authenticator is in use, there is no facility to create groups within Datameer*. Datameer can handle at maximum 500 LDAP groups.
* See Using a Default LDAP Group for the one exception to this rule.
| Note | ||||
|---|---|---|---|---|
| ||||
Many times an all lowercase username is required for proper Unix group authentication. Instead of needing to change all user names to lowercase characters, Datameer has the following property file to transform a username into all lowercase before passing it to the hadoop client API(s) to account for this issue.
To enable this feature, add the above property file to the custom Hadoop properties. |
Configuration
| Note | |||||
|---|---|---|---|---|---|
| |||||
We strongly suggest that you have superuser mode enabled and that you have the password handy when making changes to the Datameer authentication system. This helps to prevent being locked out of the system should something go wrong. Make sure the deployment property das.superuser.enabled is true and that you are aware of the values of das.superuser.username and das.superuser.password. You need to set the following in
|
| Tip | ||
|---|---|---|
| ||
If you plan on accessing your LDAP service over SSL, read Configuring Secure LDAP (LDAPS) before continuing. |
To configure Datameer to use your LDAP or ActiveDirectory service, click the Admin tab, click Authentication on the left menu and click Edit. This presents you with the option to choose between the Internal Datameer User Management or a Remote Authentication System. Select Remote and pick ActiveDirectory/LDAP from the drop down list:
Next, you see the configuration settings for you remote authentication service:
The configuration settings are described below:
...
Setting
...
Description
...
Server URL*
...
The LDAP connection string used to access your server. This should be in the form ldap://server:port. See Configuring Secure LDAP (LDAPS) for details on connecting via LDAPS.
Port numbers: LDAP/S - 389/636 or Active Directory - 3268
...
User
...
The user account Datameer uses to connect to the remote service in order to perform authentication. For many LDAP services, this is a fully distinguished name of a user, for ActiveDirectory, this is username@domain.com
...
Password
...
The LDAP password for the user specified above
...
Search Base*
...
This is the LDAP location used as a search base. Datameer bases its LDAP queries from here only searching below this point, so it is a good way to partition the users who are available to Datameer. You can only specify one search base. In Active Directory it is possible to limit Datameer to users only contained in a specific domain or organizational unit using this setting. See Limiting LDAP User Results.
...
Pagination Control
...
Active Directory
Choosing the Active Directory service type configures the advanced query options with settings appropriate for most Active Directory installations. Also, a different strategy is used to list a user's groups which is required by Active Directory. If the default settings aren't appropriate for your installation they can be changed in the Query Options section. See Advanced Configuration.
| Warning |
|---|
Using Active Directory authentication for access to networked servers/services, like FTP/SFTP/SSH must ensure the primary group of the user doesn't contains a space. (E.g., The group "domain users" would fail. Change the primary group of the user to the single word "domain_users"). |
...
Advanced Configuration
To refine your authenticator configuration you can customize the settings Datameer uses when communicating with the remote service. Expand the Query Options form:
...
Setting
...
Description
...
User Definition *
...
The filter expression used when Datameer queries the remote system for available users. See Limiting LDAP User Results
...
Username Attribute *
...
The attribute that is mapped to the Datameer username. This must be unique across all users. For Active Directory this is the sAMAccountName, for other LDAP providers it varies: uid, cn, username, etc.
...
Email Attribute *
...
The attribute that is mapped to the Datameer user's email address. Most systems use 'mail'.
...
Group Name Attribute *
...
The attribute that is used as the group name in Datameer.
...
...
| Info |
|---|
Group Membership Attribute and Group Filter only apply to 'Other LDAP' installations as Active Directory installations use a different group listing strategy |
Configuration (As of Datameer version 6.3)
| Info |
|---|
Datameer has improved connecting and using authentication services.
|
...
The authentication configuration settings for Active Directory and LDAP are displayed.
The default user values can be set when accessing multiple LDAP servers as the same user. If a default user/password is set, check the box under Server Connections that the default user values should be used to authenticate.
Enter the server configuration settings.
Multiple LDAP server can be added. Click the Add Server Connection button after all values have been entered. Datameer validates the server and credentials and then provides a blank Server Connection settings form for additional servers.
...
Setting
...
Description
...
Server URL *
...
The LDAP connection string used to access your server. This should be in the form ldap://server:port. See /wiki/spaces/DAS60/pages/4620161148 for details on connecting via LDAPS.
Port numbers: LDAP/S - 389/636 or Active Directory - 3268
...
User
...
The user account Datameer will use to connect to the remote service in order to perform authentication. For many LDAP services this will be a fully distinguished name of a user, for ActiveDirectory, this is username@domain.com
...
Password
...
The LDAP password for the user specified above
...
Search Base*
...
This is the LDAP location used as a search base. Datameer bases its LDAP queries from here only searching below this point, so it is a good way to partition the users who are available to Datameer. You can only specify one search base. In Active Directory it is possible to limit Datameer to users only contained in a specific domain or organizational unit using this setting. See Limiting LDAP User Results.
...
Pagination Control
...
User and group query options.
...
Email Attribute *
...
The attribute that is mapped to the Datameer user's email address. Most systems use 'mail'.
...
The attribute that will be used as the group name in Datameer.
...
Group filters.
...
| Info | ||
|---|---|---|
| ||
The LDAP and Active Directory authenticators available in Datameer X provide remote authentication services for Datameer X users. Administrators can configure Datameer X to use their existing LDAP or Active Directory systems as the authenticator of record allowing for centralized management of user accounts and credentials outside of Datameer X. Users can authenticate with Datameer X using existing credentials which are verified against the remote system on every login. If the remote system no longer sanctions the user, access to Datameer X is denied. This simplifies Datameer X administration and allows end-users to use familiar single sign-on credentials when accessing Datameer. |
| Table of Contents |
|---|
| Tip | ||
|---|---|---|
| ||
For accessing your LDAP service over SSL, see Configuring Secure LDAP (LDAPS). |
Users and Groups
Users
| Info | ||
|---|---|---|
| ||
When using the LDAP Authenticator, credentials are authenticated at the time of login directly against the remote service. In order for Datameer X to manage authorization and object permissions, a Datameer X user entity is required to represent the remote user. It useful to think of users being imported into Datameer X from LDAP with the remote server always ensuring that users have valid, active credentials. When a user is imported into Datameer X, a user entity is created using the remote unique identifier as the Datameer X username and populated with other account details, i.e. the email address. |
| Info | ||
|---|---|---|
| ||
If authenticating with Active Directory or LDAP, users executing jobs must be listed in the authenticator. For added security, executing jobs as a users not present in the authenticator is not possible. |
Groups
| Info | ||
|---|---|---|
| ||
During import, Datameer X creates groups, based on the groups contained in the LDAP directory. This allows the use of existing LDAP groups for Datameer X access control as the group memberships are mirrored across systems. The users' group memberships and user details are updated on every login to ensure that any changes to authorization policies in LDAP are reflected in every Datameer X session. Since we rely on LDAP groups when the LDAP Authenticator is in use, there is no facility to create groups within Datameer. Datameer X can handle at maximum 500 LDAP groups. |
| Info | ||||
|---|---|---|---|---|
| ||||
Many times an all lowercase username is required for proper Unix group authentication. Instead of needing to change all user names to lowercase characters, Datameer X has the following property file to transform a username into all lowercase before passing it to the hadoop client API(s) to account for this issue:
To enable this feature, add the above property file to the custom Hadoop properties. |
Preparing the Authentication
| Info | |||||
|---|---|---|---|---|---|
| |||||
Make sure you have the superuser mode enabled in the 'live.properties' and have the password handy when configuring the authentication. For that, check if the deployment property 'das.superuser.enabled' is true and have the values for 'das.superuser.username' and 'das.superuser.password' handy. NOTE: If you are using a custom deploy mode via 'DAS_DEPLOY_MODE' then use the properties file for that mode, live.properties is the default).
|
Configuring an Active Directory and LDAP Authentication
To configure Datameer X to use your LDAP or Active Directory service:
- Click on the "Admin" tab and select "Authentication". The page 'Authentication' opens.
- Click "Edit". The authentication configuration page opens.
- Select "Remote Authentication System", select "ActiveDirectory/ LDAP" from the drop-down and click "Next".
- Enter the username and password for the default user.
- Enter the server URL.
INFO: The URL should have the form of 'ldap://server:port'. The port numbers are: LDAP/S - 389/636 or Active Directory - 3268.
- If needed, select "Use default user" if the server connection should use the default user to connect.
- If needed, enter the username and password.
- Enter the search base query.
- Enter the user definition query.
- If needed, enter the group definition query.
- If needed, define the pagination control.
- If you want to add multiple LDAP server, click "Add server connection". Another 'Server Connection' section opens and can be configured and deleted if non needed furthermore.
- Enter the username attribute that defines a username and must be unique across all users.
- Enter the email attribute.
- If needed, enter the attributes for impersonation and/ or salt.
- Enter the attribute for group names.
- If needed, enter further group related attributes as well as group relates fields, e.g. 'Virtual Group'.
INFO: The checkbox 'Mixed mode' is enabled by default and enables both internal user management as well as SAML. Having this disabled, the internal user management is disabled.
- If needed, enter group filters to include or exclude groups with regex.
- If needed, check the checkbox "Ignore Case" to perform a case sensitive match when filtering group names.
- Confirm the configuration with "Save". Configuring Datameer X to use LDAP or Active Directory authentication is finished.
Importing Users/Groups
Once you have successfully configured your LDAP connection, you can now import users into Datameer , X enabling users to access the system. Because AD/LDAP is active, Datameer's internal authentication method is disabled. Therefore, admins must create all groups needed in the AD and add the users there before importing them. To import, click Users from the Admin menu.
...
Select the user/group, assign a rolea role, and click Add. Each user must have a role. Once a user/group has been added, the name is greyed out from the list. That user/group has access to Datameer X once the cache has been refreshed.
| Note | ||
|---|---|---|
| ||
In order to have access to Group Authentication tab, the Datameer X license must support unlimited users. |
...
Highlight multiple users/groups to to perform bulk role updates or deletions. It is also possible to bulk import users from your LDAP authenticator.
| Info | ||
|---|---|---|
| ||
The username and email address aren't editable as they are provided bythe LDAP service. Only Enable/Disable, Roles, and comments are editable from this screen. |
Advanced Topics
Cache settings
Datameer X loads the entire set of LDAP users into a cache that is periodically refreshed from LDAP. This offers tremendous performance benefits and enables features like search and browse in the UI. By default, Datameer X refreshes this cache every hour. This means that modification to LDAP data might not be reflected until the cache is refreshed.
...
To change the cache refresh settings you can set the system property ldap.authenticator.available.users.refresh.interval.minutes to whatever minute value you desire. For most installations, the 60 minute setting makes sense.
Enabling and disabling remote authentication
While setting up the system or when doing maintenance, you might find it necessary to switch off the LDAP Authenticator. When the LDAP Authenticator is disabled, all user's which were imported from LDAP are automatically disabled and the cache is dropped. When the authenticator is re-enabled, all users are then re-enabled and ready for use. You don't have to re-import any users. Also note that the cache has been re-built.
Skipping users
Datameer X builds a list of all available users for import based on the authenticator configuration. During this process, Datameer X dropS users from this list if:
- The user doesn't have a username
- The user doesn't have an email address
- The user isn't a member of a group (see Using a Default LDAP Group for a workaround)
If you don't see users that you are expecting available for import to Datameer , X check your logs and look for WARN level message such as:
...
Seeing these types of messages often signifies a misconfiguration.
Using a default LDAP group
| Anchor | ||||
|---|---|---|---|---|
|
By default when constructing the list of users available for import, Datameer X skips any users that aren't members of a group in LDAP. This behavior is desirable since this is most likely a mis-configuration and Datameer X requires user to belong to a group. However, it is possible that your LDAP users haven't been assigned to a group or that for some reason the Datameer X authenticator can't resolve any. In this case, you can set a system property - ldap.authenticator.use.default.group=true - creating a default group for imported LDAP users. The group LDAP_USERS contains every user not assigned to another group, be aware of this when setting up group permissions.
Limiting LDAP user results
| Anchor | ||||
|---|---|---|---|---|
|
Many LDAP providers, Active Directory included, limit the number of results returned in most searches. When this limit it is reached, no more results are sent to the client in a single request. This is problematic, especially if you don't have the ability to configure the LDAP service to allow more results. If your LDAP installation is sufficiently large and your service is configured to limit results in this way, Datameer X might fail to load any users at all. To get around this issue, Datameer X offers several configuration options:
Use a more restrictive search base
In the Query Options section of the Authenticator configuration screen, you can define a search base that limits the scope of the LDAP query. For example, if we have a search base for a Datameer X LDAP server DC=datameer,DC=local and it contains 3,000 users which is over the limit of 1,000 results, we can refine it to include only the organizational unit we want, OU=BarUnit,DC=Datameer ,X DC=local which contains only 1,000 users.
Now we can successfully import users from the organizational unit BarUnit and below in the LDAP tree.
Add constraints to the user definition
The Query Options section also contains a field for configuring a User Filter. This is analogous to an SQL WHERE clause used when Datameer X queries for LDAP users. You can filter any attribute associated with a user in your LDAP server. As an example, we could filter users based on their membership in either the 'Finance' or 'IT' department. This would make only users matching the filter available for import into Datameer. The filter is defined using normal LDAP query syntax:
| Info | ||
|---|---|---|
| ||
The above query says, "Find objects which are of objectClass 'person' and have a department value of either 'Finance' or 'IT'". For more details about LDAP query syntax, go here. |
Set a custom MaxResults setting for the Datameer X LDAP user
If the Datameer X LDAP needs to list large numbers of users, a user specific setting can be applied in most LDAP providers. This would allow this specific user to exceed the default query result settings for this domain. In Active Directory, this is achieved by setting a MaxResults value for the Datameer X LDAP user.