SmarterTrack LDAP Authentication - Proper LDAP String Syntax Question
Question asked by Chris Kluener - 8/10/2015 at 1:25 PM
Hi all,
I'm trying to accomplish getting SmarterTrack to allow Active Directory authentication for my users.  I understand this is supported via the "External Providers" settings in SmarterTrack.  I've read over:
http ://portal.smartertools.com/kb/a2516/configure-external-providers.aspx
http ://portal.smartertools.com/community/a2785/configuring-smarter-track-with-ldap-authentication-active-directory-integration.aspx
And I'm unable to get it to work.  My immediate question is what is the format of the LDAP string that is expected for SmarterTrack to do this?  I've tried as many different formats as I can think or / the documentation / nomenclature brings to mind -- the one thing I can't seem to wrap my head around is how authentication to the DC happens in the fields provided.   
My previous experience working with LDAP indications that something like:
LDAP://DC.DOMAIN.ORG/OU=UsersOU,DC=DOMAIN,DC=ORG should do the trick IF there are lines for username / password to work.  It doesn't for me.
I've tried:
I even started down the route of Active Directory Web Services and played around with the:
 net.tcp: //dc_server_name:9389/ActiveDirectoryWebServices/Windows/ User/
 Nomenclature / Connection String options but I felt like I was getting farther and father away at a point.  Also, on the same machine another application is connecting to Active Directory and reading Users information fine.  
Any direction on the proper syntax / settings to get Active Directory authentication working would be much appreciated.
I also tried the format:
And the password for the user in the Web Services Password to no luck.

1 Reply

Reply to Thread
Chris Kluener Replied
Marked As Answer
Follow-Up -- According to sales SmarterTrack doesn't support this feature out of the box.  There isn't a straight forward way to bind SmarterTrack to Active Directory to either import the users in bulk and/or upon first login. It sounds like the built in option is to manually key in the users that then can use AD to authenticate -- or the other option is to write your own External Provider to bridge the gap. Neither of which my shop will commit to. 
Hope that helps anyone with the same question.  
ps - there appears to be an example LDAP External Provider that I can download but I can't tell if it is actually functional or more of a template. Even if it is functional I can't find any documentation on how to actually put it into production - but I didn't spend much time pilling through the documentation.  

Reply to Thread