Operating System - HP-UX
1820695 Members
2527 Online
109627 Solutions
New Discussion юеВ

CIFS Server and idmap config DOMAIN:backend = nss

 
Michael St. Laurent
Occasional Advisor

CIFS Server and idmap config DOMAIN:backend = nss

The distribution version of Samba has an nss backend for use with Winbind for those who have existing setups and want to retain the old account mapping behavior with an ADS member server. It doesn't look like this is available in A.02.03.04. Are there plans to include it any time soon in the HP-UX CIFS Server?
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: CIFS Server and idmap config DOMAIN:backend = nss

Shalom,

CIFS fully supports ads security setup right now

We are using it in product right now. All features available in Samba have been ported to CIFS as far as I know.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Michael St. Laurent
Occasional Advisor

Re: CIFS Server and idmap config DOMAIN:backend = nss

In version A.02.03.04?

I added the following to my smb.conf file:
idmap domains = MERCURY
idmap config MERCURY:backend = nss
idmap config MERCURY:readonly = yes

but Winbind complained about Unknown parameter encountered: "idmap domains". Those lines were key to getting ADS membership working on a Linux server here.

But perhaps I should take a step back and explain my goal. I am trying to get the same behavior with ADS that we have with the Domain model. That is, a local account is required, the Windows account name maps automatically to the same account name in Unix and password authentication is offloaded to the domain controller(s).
Michael St. Laurent
Occasional Advisor

Re: CIFS Server and idmap config DOMAIN:backend = nss

Here is a link to the function that I am hoping to see integrated:

http://us1.samba.org/samba/docs/man/manpages-3/idmap_nss.8.html
Michael St. Laurent
Occasional Advisor

Re: CIFS Server and idmap config DOMAIN:backend = nss

It looks like my only option is to setup the LDAP client, install SFU on the Active Directory server and migrate the UID & GID info into the LDAP directory on the Active Directory server.