Authentication Backends
Mint Service Desk 3.4.2 user manual.
Azure Ad
Registering the application
First go to https://portal.azure.com Sign in and go to Microsoft Entra ID services.
Go to “App” and ‘App registration’
The following form will appear.
Complete the registration form:
-
in ‘Name’ field type your preferred name
-
‘Supported Account Types’: leave it as it is
-
‘Redirect URL’: fill it with https://{your.mintsd.domain}/external/signin-{your-scheme}
- Replace {your.mintsd.domain} with your domain name
- Replace {your.scheme} with schema name which will be needed later on
-
After the registration go to the Authentication tab
In ‘Implicit Grant’ section check ID tokens
Claims and API permissions
Go to Token Configuration tab.
Click on Add optional claim.
Check ID token type and email, given_name, family_name claims.
In case of a need to configure group mapping, click on Add groups claim. Now select all check-boxes and click on Add.
Go into API permissions section.
- click on Add a permission
- select Microsoft Graph
- select Delegated permission and check email and profile
Client secret
Go to Certificates & secrets tab.
Add new client secret by clicking on New Client secret.
Copy the client secret using the copy button.
Provider configuration in Mint
In the Authentication Backends section go to OpenID Providers click on button, the following form will appear.
Complete the provider form:
- value from Name will appear on Login screen
- in Scheme field type value from one of the previous steps ({your.scheme})
- in Type field select AzureAd
- in Client secret field paste the value from previous step (‘Cerificates & secrets’ tab)
- in Client id field paste the value from registered app overview
- in Tenant Id field paste the value from registered app overview
- in Groups claim field, enter the name: ‘groups’. The new fields will appear below in Group mapping section. Paste ID of Azure group to Groups and select Agent role from Role to connect Azure group with Agent role. You can combine more groups under one claim by pressing Add button.
You will find the group ID in Azure AD under the path: Home > Microsoft Entra ID > Manage (sidebar) > Groups (sidebar) > All groups (sidebar)
Ldap
LDAP integration allows automatic login using domain accounts and synchronization of user data (e.g., first name, last name, email address, groups).
The table lists saved LDAP configurations. Add, edit or delete a configuration, and use Search and Add column as on the ticket dashboard.
To add a new configuration, click the button. A page containing configuration fields will open.
Complete the following connection and mapping fields.
Configuration Fields
The first section describes the connection and authentication settings required for the Mint Service Desk system to communicate with the LDAP directory. It defines where the LDAP server is (host, port, security), how the system connects to it (Bind DN, credentials, certificates), and what user data should be retrieved (search base, search filter, synchronization property). The basic information required to establish a connection is the host name (Host), the relevant port (Port) and the security method (Security). There are two ways to configure configuration fields below. One option is to connect to the domain directly using a user account, which only requires the Search base and Search filter. The other option is to use a domain account to search the directory, which also requires a Bind DN and Bind credentials.
| Field | Description | Example (Active Directory) |
|---|---|---|
| Host | LDAP server address. | ldap.example.com |
| Port | LDAP port (389) or LDAPS (636) | 636 |
| Active | Enables/disables LDAP integration | ✓ |
| Security | Connection type: None, StartTLS, SSL/TLS | SSL/TLS |
| Trust all certificates | Accept all SSL certificates (including untrusted) | ✓ |
| Turn off referrals | Disable LDAP referrals between servers | ✓ |
| Bind DN | Technical account used to read data from LDAP | CN=ldapuser,OU=ServiceAccounts,DC=example,DC=com |
| Bind credentials | Password for the Bind DN account | •••••• |
| Search base | Starting point in the directory tree for user lookups | OU=Users,DC=example,DC=com |
| Search filter | LDAP filter defining which objects are retrieved | (&(objectClass=user)(sAMAccountName={0})(memberOf=CN=Helpdesk,OU=Groups,DC=example,DC=com)) |
| Synchronization property | Unique attribute to identify and sync users (User name or Email) | Select User name or Email |
User Data Mapping
The User Data Mapping section defines how user information from LDAP attributes (e.g., sAMAccountName, mail, givenName) is mapped to the corresponding fields in the Service Desk system (e.g., username, email, first name, last name, groups). There is also possibility to map group parameters to specific User Roles and additional attributes from LDAP to specific custom fields in User Profile
| Service Desk Field | LDAP Attribute | Description |
|---|---|---|
| User name | sAMAccountName | User login (used for domain authentication) |
mail | User’s email address | |
| First name | givenName | First name |
| Last name | sn | Last name |
| Manager | manager | LDAP attribute name where manager value is held |
| Groups | memberOf | Attribute name where user groups are held |
| Group mapping (visible if the Groups field is filled in) | OU=Users | Selected parameter from the Groups field to map with Mint Service Desk user roles |
| Attribute mapping (visible if the Groups field is filled in) | telephoneNumber | Additional attribute from LDAP to map with custom user fields |
Remember that when the role mapping option is configured, the appropriate roles are set for each user when they log in and their groups are retrieved. This means that any changes made to roles in the administration panel will not take effect, as the roles retrieved from LDAP take priority.