Bug 185313 - Samba doesn't include "idmap backend = ad" or "winbind nss info = sfu"
Summary: Samba doesn't include "idmap backend = ad" or "winbind nss info = sfu"
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: samba
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Simo Sorce
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-13 17:10 UTC by Shannon Johnson
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2007-11-21 23:56:56 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shannon Johnson 2006-03-13 17:10:32 UTC 
Description of problem:
When integrating Samba into a Windows domain, it helps to keep consistent
UID/GID's for users. That's where the idmap backend comes in... unfortunately,
the RPM for Samba doesn't include the options for Active Directory-held
UID/GID's or Home Directories... thereby making integration very difficult.
Also, this is required for integration with Windows 2003 R2, which all new
servers now come with.


Version-Release number of selected component (if applicable): 3.0.10-1.4E.6


How reproducible: Always


Steps to Reproduce:
1. Install Windows 2003 R2 as a Domain Controller
2. Attempt to set up Samba with "idmap backend = ad" and/or "winbind nss info = sfu"
3.
  
Actual results:
Fails with error "could not load remote backend 'ad'" in winbindd.log and/or
"ignoring unknown parameter 'winbind nss info'".

Expected results:
It should load the backend, then retrieve the UID & GID and/or Home Directory /
Profile from the AD server.

Additional info:
This functionality was added in the official Samba release of 3.0.20 back in
August of 2005.
Note You need to log in before you can comment on or make changes to this bug.