Yes, it support AD for LDAP.

If this is for Multiprotocol, more work is required as AD do not have unix uid/gid attributes by default. For unisphere user authentication, it will work as it is.

Hi,

could you clarifty what you want to use LDAP authentication for ?

management access ?

specific file protocols ?

@maniemc - using LDAP for multi-protocol mapping isnt really authentication - we still authenticate using the protocols native auth methods - LDAP is just a directory service there providing the info

Hi

I would like to use AD LDS for specific file protocols.

Thank you

which protocol ?

Multi protocol enviroment.

I want to  use following authentication.

CIFS is AD

NFS is AD LDS

for CIFS auth AD is automatically used by virtue of the CIFS server being joined to the domain - no extra LDAP setup needed

SMB/CIFS doesnt authenticate via LDAP - it uses either Kerberos or NTLM

for classic NFSv3 the client authenticates - the NFS server believes the UID/GID the client sends - no LDAP auth used at the Unity NFS server - as with any NFSv2/3 config

the client may authenticate the user any way it sees fit - whether via local file, NIS, LDAP, PAM, ...

for NFSv4 auth yes you could use a MS AD server as KDC with Kerberos

and yes we can use an AD server to get the multi-protocol mapping info - but that has nothing to do with authentication.

Hi

Sorry to slide in here myself, but i have a similar setup to do by setting up a NAS Server with multiprotocoll access.

The Join into AD worked, but the Unix Directory Service Part is still degraded.

i configured LDAP to point to the AD, which seems to work on Port 389 and used "my nas admin account" and the AD CN as Base DN.

I get the message that the binding to a user is not working properly. either account, pw or permissions etc...

Question: what kind of permission do i need and can i point to an OU-Structure where i can set those permissions?

My account isnt DOM-Admin and i need a config without claiming DOM-Admin permissions

thx

Martin

Martin,

If you MS AD as LDAP for unix directory service, please ensure all the parameters are defined in AD (netgroup will not be in AD by default, so you have to create)

Check /EMC/C4Core/log/c4_safe_ktrace.log (grep by the nas server name, case sensitive) for more info (try to make some changes to ldap to see new information about why it errors).