Is there ever going to be a Active Directory connector?
Don't get me wrong, I like LDAP, but it's a 'pain in the you know what' compared to if the appliance had some form of Active Directory connector to where you would be able to just browse and link to A.D. objects.
Anyone in the know?
Anyone in the know?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
airwolf
14 years ago
I don't see any downside to LDAP unless you would like write access to your AD objects. LDAP works fine if you've written proper queries. What functionality would you like from an AD connector that you can't accomplish with LDAP?
As to whether or not an AD connector is in the works, I'm not positive but I believe I remember some mention of it. I do know that there is an active feature request for LDAP cleanup (removing accounts no longer active in AD).
As to whether or not an AD connector is in the works, I'm not positive but I believe I remember some mention of it. I do know that there is an active feature request for LDAP cleanup (removing accounts no longer active in AD).
Posted by:
rgaudet
14 years ago
Posted by:
airwolf
14 years ago
Posted by:
GillySpy
14 years ago
You can also use the LDAP Browser to help write the Search Base and the Search Filter. See this FAQ for an example:
http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=55&id=738&artlang=en
One thing to note:
When setting up an authentication you will almost always use
When setting up an import you will almost always use
http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=55&id=738&artlang=en
One thing to note:
When setting up an authentication you will almost always use
samaccountname=KBOX_USER
as part of your filter.When setting up an import you will almost always use
samaccountname=*
as part of your filter
Posted by:
rgaudet
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.