Azure Active Directory supports the LDAP interface when properly configured, and therefor LDAP can be used to sync the ExacqVision Enterprise Manager software with the Azure AD instance. Background Information: Lightweight Directory Access Protocol (LDAP) is an application protocol for working with various directory services. Directory services, such as Active Directory, store user and account… Continue reading Enterprise Manager supports LDAP authentication with Azure Active Directory
Tag: Active Directory and LDAP
Enable Local Users Accounts is Disabled Within the exacqVision Client
Description The Enable Local User Accounts check box is grayed out (Disabled) on the Enterprise or Configure System ActiveDirectory/LDAP tabs. Product Steps to Reproduce Expected Results Actual Results Solution
AES Encryption Methods Supported For LDAP Connection
AES-128 and AES-256 encryption support for LDAP communication was added with the release of exacqVision Server 21.12.3. Versions older than that must use RC4 encryption. To determine if you are using the AES encryption or not. Check the logs from Exacq server for the StreamPi plugin, and if you are using the AES encryption and… Continue reading AES Encryption Methods Supported For LDAP Connection
Setting a primary group to an LDAP user
Issue If you have an LDAP group listed on the ExacqVision server, and you set this group as a primary group for a specific user. The Active Directory will not authorize this user to log in on ExacqVision software. Solution Remove this group from being the primary group of the user, or add this user… Continue reading Setting a primary group to an LDAP user
Setting the listed LDAP group on Exacq as the primary group for a specific user will not allow the user to log in
If you have an LDAP group that is listed on Exacq and set this group as the primary group for a specific user, this user will not be able to log in on Exacq Software. The workaround for this issue: <br>
Does exacqVision Work with Nested Active Directory Groups?
Yes with server version 6.8 and later. The admin needs to select Active Directory (Nested) as the schema in the AD/LDAP configuration screen. <br>