On 2014-04-10 17:20, Jakub Hrozek wrote:
our current HOWTO on connecting SSSD to an AD DC is outdated,
mostly because the page still only introduces the LDAP provider. Recently, me,
Sumit and Jeremy Agee wrote a new page that specifically advises to use
the AD provider and also use realmd for setup:
We started a new page and kept the old one around mostly because pre-1.9
versions still need the LDAP provider info.
I'd like to get some review and feedback from our community so we can
link the wiki page from the front page or the documentation section. In
addition to the lists, I also CC-ed the individual contributors to the
original page directly..I hope that's fine.
I've been pretty detached from all this during the past year but perhaps
that's only a good thing for the review..
In general all looks very nice and it was certainly a good move to write
a new document. I have few nitpick comments, please see below and
address/ignore them as you see appropriate (and please pardon me if any
of these are copypastes from something I wrote for the old document :).
- I'd add LDP/ldapsearch examples to the GC section
- for completeness sake I'd add dns_lookup_kdc = true and master_kdc =
to the krb5.conf example
- I'd add KRB5_TRACE=/dev/stdout kinit -V example somewhere, perhaps
after the krb5.conf example
- I would at least comment out password server in smb.conf
- a bit of grouping in smb.conf might make it more readable, e.g.
security/realm/workgroup could be the first block, then logging options
(location+level), then server options, then client options