Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

AD LDS Problem with User Proxy

$
0
0

Questions based on following the article: Understanding Proxy Authentication in AD LDS by Ken St Cyr (Please google it since this forum complains about links in submissions)

Here is where I get stuck under setting up a proxy authentication lab:

After the AD LDS instance is installed, the next step is to disable the SSL requirement for proxy authentication. In the ADSI Edit snap-in (adsiedit.msc), you should connect to the configuration partition of the AD LDS instance using the administrator account you specified during the install. If you don't know the DN of the configuration partition, you can choose "Configuration" from the "Select a well known naming context" dropdown list in the connection settings dialog in ADSI Edit.

Browse to the container "CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,CN={guid}"....

After I use ADSI edit (from the domain controller where AD LDS is also installed) to connect to config partition which happens to be port 50002  (50003 is LDAPS), I do not seem to have a container by the name: CN=Directory Service

What could be wrong?

A reCN=Directory Servicelated question is when I use ldp to connect to localhost:50002 and do a simple  bind as a proxy object  I get:

res = ldap_simple_bind_s(ld, 'CN=Joe Smith,CN=appdirJoeS,DC=aspect,DC=com', <unavailable>); // v.3

Error <49>: ldap_simple_bind_s() failed: Invalid Credentials

Server error: 8009030C: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 202d, v1db0

Error 0x8009030C The logon attempt failed

 

Is this because I have not solved the first problem?

 

Can I look at the DC somehow to see what creds are being passed?

Thanks


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>