- If you are using Azure Active Directory as your authentication provider, you must configure Azure Active Directory Domain Services. To learn how, read LDAP authentication with Azure Active Directory.
This guide explains how to configure Matillion ETL to use Active Directory for authentication and authorization.
Matillion supports three authentication models:
- INTERNAL (default)
By default, Matillion ETL users are authenticated against an internal user file. However, it is possible to authenticate users against an Active Directory or another LDAP directory server.
To configure external settings for Okta LDAP integration, please follow the steps in this document until you reach Configuring Matillion, then follow Configuring Matillion ETL in Okta LDAP Configuration.
Authorization in Matillion
Matillion ETL authorization supports four roles that allow users to access specific aspects of the product:
- Emerald: this role allows access to the Matillion ETL interface. Typically, all users have this role.
- Server Admin: this role allows a user to access the Admin menu.
- Global Project Admin: this role allows a user to access every project.
- API: this role allows a user to use the Matillion ETL API.
In the context of LDAP integration, four user groups will be created that can be mapped to the above roles. For this example, four user groups have been created in Active Directory:
- Emerald Admin
- Emerald Project Admin
- Emerald API
Provide names or a valid naming convention for the above groups (the names above are used as an example). Also, having four separate user groups is not necessary. Depending on requirements, a single user group may be mapped to all four roles.
Take a backup of the following five files to ensure the previous configuration can be restored, if required:
Alternatively, a snapshot of the instance can also be taken before making any changes.
- Switch back to the Instance-database via the Admin menu:
Click Internal, then click Save Configuration and restart Tomcat/Ec2-Instance.
- If access to the Admin menu is unavailable:
Restore the server.xml and tomcat-users.xml files from the backups made earlier, and restart Tomcat.
- Restore from a snapshot:
When choosing to restore from a snapshot, keep in mind that if the snapshot is too old, any changes to jobs or configurations made before the snapshot will be lost.
Below, find the details required from the LDAP/Domain:
- LDAP server:
test.mtln.com is accessible on port 389 or 636 for SSL (Use an IP address if a domain is not accessible by name)
When issuing queries to the Global Catalogue for larger Active Directories (or when experiencing timeouts waiting for Active Directory to respond), it can be beneficial to use Port 3268 (LDAP) or 3269 (LDAPS)
Emerald, Emerald Admin, Emerald Project Admin, Emerald API
Four users have been created and added to the usergroups as shown below
Username Usergroup ec2-user Emerald, Emerald Admin, Emerald Project Admin, Emerald API etl-admin Emerald Project Admin etl-user Emerald api-user Emerald API
Users and user groups in Active Directory are held in containers or organizational units (OU) managed by the domain administrator. The above setup ensures the users and user groups are in the users' containers, however, any number of different configurations may be applied. Ideally, try to keep the users and user groups in the same containers/OU.
The distinguished name of the container/OU in which users and user groups are categorized will need to be provided. For example, the distinguished name for the Users container in this setup is
To configure Okta LDAP integration, refer to Configuring Matillion ETL in Okta LDAP Configuration.
1. Click Admin Menu → User Configuration in the top right corner of the Matillion ETL.
2. Select EXTERNAL from Security Configuration at the top of the User Configuration pop-up window.
3. Provide details as described in the table below:
|Connection Name||The name of a user to make the initial bind to the directory. This could be any AD user. For active directory, that will include a realm using the form "user@REALM":
|Connection Password||The password for the user to make the initial bind to the directory.
Warning: we advise against using "special characters" in passwords—any character above #128 in either of these lists may cause issues:
|Connection URL||The location of the directory server, using one of the forms below:
For non SSL:
|User Base||The part of the directory tree to begin searching for users. Typically users are created in the Users Container/OU. Change this as appropriate if Matillion ETL users are held in a different container:
|User Search||The attribute to search for user names (leave this unchanged):
|Role Base||The part of the directory tree to begin searching for groups/roles— similar to User Base above, change this appropriately if Matillion user groups are in a different container to users:
|Role Name||The name of the attribute containing the role name (leave this unchanged):
|Role Search||How to find all the roles for a user (leave this unchanged):
|METL Access||The role to gain access to the Matillion ETL application:
|METL Server Admin||The role to gain access to the Matillion ETL administration page - this maybe different to the METL Access role name:
|METL Global Project Admin||This role allows a user to access every project::
|API||The role to gain access to the Matillion ETL API - this maybe different from the METL Access role name:
4. Click Save Configuration.
5. Restart Tomcat.
Log in to Matillion
Once Tomcat is restarted, users may now use the assigned Active Directory username and password to log in.
The domain does not need to be specified as part of the username—for example, "domain\\username" or "firstname.lastname@example.org".