P
Paul research
Guest
For objects in the same domain, I can bind like this:
DirectoryEntry de = new DirectoryEntry("LDAP://<GUID=" + objectguidInSameDomain + ">");
Then can access props like:
de.Properties[someProp].Value
This working with
de.directoryEntry.AuthenticationType = AuthenticationTypes.Secure | AuthenticationTypes.SecureSocketsLayer;
too.
An object in the sub domain I can bind the same way by access from parent domain:
new DirectoryEntry("LDAP://<GUID=" + objectguidInSubDomain + ">")
But if I enable
de.directoryEntry.AuthenticationType = AuthenticationTypes.Secure | AuthenticationTypes.SecureSocketsLayer;
and then try to access properties then I get an error.
If I add the subdomain to the path, then it works again:
new DirectoryEntry("LDAP://sub/<GUID=" + objectguidInSubDomain + ">")
Question: Why do the same path works for LDAP, but not for SLDAP? Do I have anyway to put subdomain or DC to the path if I access sub domains with SLDAP using a guid or is there are a workaround?
Thank you in advance!
Continue reading...
DirectoryEntry de = new DirectoryEntry("LDAP://<GUID=" + objectguidInSameDomain + ">");
Then can access props like:
de.Properties[someProp].Value
This working with
de.directoryEntry.AuthenticationType = AuthenticationTypes.Secure | AuthenticationTypes.SecureSocketsLayer;
too.
An object in the sub domain I can bind the same way by access from parent domain:
new DirectoryEntry("LDAP://<GUID=" + objectguidInSubDomain + ">")
But if I enable
de.directoryEntry.AuthenticationType = AuthenticationTypes.Secure | AuthenticationTypes.SecureSocketsLayer;
and then try to access properties then I get an error.
If I add the subdomain to the path, then it works again:
new DirectoryEntry("LDAP://sub/<GUID=" + objectguidInSubDomain + ">")
Question: Why do the same path works for LDAP, but not for SLDAP? Do I have anyway to put subdomain or DC to the path if I access sub domains with SLDAP using a guid or is there are a workaround?
Thank you in advance!
Continue reading...