HP CIFS Server 3.0a Release Note version A.02.01

HP CIFS Server Release Note

What’s in the HP CIFS Server A.02.01

Chapter 1 7

UNIX and Microsoft Windows NT have different models to represent

user and group information and use different technologies for

implementing them. Winbind is a component of the Samba suite of

programs that resolve Windows users and groups to HP-UX UIDs and

GIDs. Winbind provides the NSS routine,

/etc/lib/libnss_winbind.1, which interfaces to the winbind daemon,

winbindd, to resolve ID mappings.

Winbind maintains a database called winbind_idmap.tdb where it

stores mapping data between HP-UX UIDs/GIDs and Windows SIDs

(Security Identiﬁers). It stores the UID and GID allocated from idmap

uid/gid range that it has mapped to the Windows SID. If you have

speciﬁed the idmap backend as ldap:ldap://<ldap server name>,

then winbind obtains this information from the LDAP directory server

instead of using a local mapping ﬁle.

When the HP CIFS Server joins to a Windows domain as a member

server with Windows NT or Windows 200x domain controllers, HP CIFS

Server supports winbind to provide UID and GID generation and

mappings for Windows users. For larger Windows NT or ADS domain

deployment environment, you can use winbind and conﬁgure multiple

CIFS Servers to store ID maps in an LDAP directory. Making use of an

LDAP server and conﬁguring HP CIFS Servers with the ldmap backend

parameter in smb.conf ensure that all UIDs and GIDs are unique

across the domain.

For detailed information on how to set up and conﬁgure an HP CIFS

Server with winbind support, refer to Chapter 9, “Winbind Support” in

the HP CIFS Server A.02.01 Administrator’s Guide

New

Authentication

Systems Support

New Authentication Systems

In addition to continued support for smbpasswd and LDAP

authentication backends, HP CIFS Server includes support of new

account storage databases, ldapsam and tdbsam.HP CIFS Server

A.02.01 authentication backends consist of the following:

• smbpasswd: Flat ﬁle format that is compatible with A.01.* versions.

It is the default conﬁguration.

• tdbsam: Attribute rich database intended as an smbpasswd

replacement for standalone servers.

• ldapsam: Attribute rich account storage and retrieval backend

utilizing an LDAP directory. This makes use of a different schema

than what had been provided with A.01.* versions.