InsightIQ 4.1.1 introduced integrated LDAP support, but there is a known issue regarding the level of flexibility in the LDAP lookup that IIQ is performing. Since there are variances in how RFC 2307 Unix extensions can be implemented in AD (that is, there is no formal compliance required), IIQ needs to be more flexible in its lookup.
Please file a bug report with the details of your experience. This will aid our investigations and efforts to create a fix for a future maintenance release.
I have had the same issue integrating InsightIQ 4.1.1.3 with Windows Server 2016 Active Directory.
The issues is the Default Attributes.
For LDAP implementations the defaults are:
posixAccount
posixGroup
For Active Directory you need to change them to:
Object Class for users: user
Object Class for groups: group
This will allow you to add AD groups to Read-Only and Administrator roles but I still cannot login to IIQ using my AD account. The scope for the user and group search and group membership is correct.
Just to clarify, AD is not technically supported (even with RFC2307 extensions), though there are ways to get it to work with IIQ. This forum is a good way to share experiences, so thanks for your post!
Thanks Mark, this has been very helpful...been struggling to get it to work for a few months now. Would be nice if changing the object class was in the install document somewhere.
I became curious about getting to enable AD authentication on the InsightIQ server working. A bit of googling got me to this article pointing to a similar issue with another LADP server and the shortcomings of InsightIQ’s LDAP configurations:
patrick_lynch
2 Posts
3777
0
Posted April 19th, 2017 15:00
InsightIQ 4.1.1 introduced integrated LDAP support, but there is a known issue regarding the level of flexibility in the LDAP lookup that IIQ is performing. Since there are variances in how RFC 2307 Unix extensions can be implemented in AD (that is, there is no formal compliance required), IIQ needs to be more flexible in its lookup.
Please file a bug report with the details of your experience. This will aid our investigations and efforts to create a fix for a future maintenance release.