LDAP Settings
Last updated
Was this helpful?
Last updated
Was this helpful?
ARKSSPR is Active Directory integrated software. See: Roadmap. User accounts in Active Directory can perform password and account unlocking operations via ARKSSPR. Supports multiple Active Directory domains. All Active Directory domains for which accounting transactions are required should be added to the list from this screen.
One of the most important issues in SMS integration is mobile phone information. From this screen, the attribute containing the mobile phone number must be selected.
UserPrincipalName and samAccountName information can be used in user login operations. In addition to these 2 pieces of information, a different attribute can be used as username information. Users can also use custom attribute information in login operations.
Active Directory domain FQDN address is entered. This field supports entering the server name. It is recommended to enter Domain FQDN information. Example: domain.com
LDAP port information is entered. By default, Unsecure LDAP connection is TCP 389, Secure LDAP connection is TCP 636. If a special port is used, it must be entered in this field.
The Secure option determines the use of LDAP/Secure LDAP.
In the username field, the user account that will be connected to the Active Directory domain and has the privileges of unlocking the account, resetting the password, reading mobile phone information, and reading alternative username attribute information is entered. This user account is also preferred to be given Replicate Directory Changes authority at the domain root level. Thanks to this authority, password history checks become applicable in password reset operations.
Test buttons are used to perform LDAP connection testing.
Click the edit button to determine the mobile phone and alternative username field and make changes to the LDAP connection.
The attribute to be used for the mobile phone is selected. If this attribute is protected, the account used for the ldap connection needs read permission for this attribute.
An alternative attribute other than UserPrincipalName and samAccountName can be used as an alternative username field.
When the Authentication option is selected, it is stated that a user account will be used for LDAP transactions. If the Authentication option is not selected, the user account specified for the is used for the operations specified below.
