-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The SSSD team is proud to announce the bugfix release 1.2.2 of the
System Security Services Daemon. As usual, it can be downloaded from
https://fedorahosted.org/sssd/
== Highlights ==
* The LDAP provider no longer requires access to the LDAP RootDSE.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached are the patches to fix the initgroups performance issue for the
master branch. Patches 0001-0004 applied trivially to the master,
patches 0005 and 0006 had to be rewritten to take advantage of the
synchronous sysdb interface, but this has made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2010 11:40 AM, Patrik Martinsson wrote:ugh, it takes around 30
secs before i get "validated", is
> this normal ?
> sssd is printing alot of
> '[sdap_fill_memberships] (7): member #726 xx'
>
> before it finally seems to stop and validate m
Ah, thanks. Sometimes it goes a little bit fast.
Yes that part (local console) works, and yes, alot more output is being
printed.
Question though, it takes around 30 secs before i get "validated", is
this normal ?
sssd is printing alot of
'[sdap_fill_memberships] (7): member #726 xx'
before
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2010 11:26 AM, Patrik Martinsson wrote:
> Ok, thanks again for the patience.
>
> I've realized that I misunderstood that part about the authentication
> and the binding against ldap, thanks very much for the explanation.
>
> Now it works co
Ok, thanks again for the patience.
I've realized that I misunderstood that part about the authentication
and the binding against ldap, thanks very much for the explanation.
Now it works correctly with the lookup of the users, however i cant get
it to work with pam, i havent digged that deep yet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2010 10:38 AM, Patrik Martinsson wrote:
> If i change, auth_provider to ldap instead of krb5 and add,
> ldap_default_bind_dn = cn=xx,ou=People,dc=xx,dc=xx,dc=xx
> ldap_default_authtok_type = password
> ldap_default_authtok = xx
>
> Then i got
Ok, thanks fior quick reply.
Changed to, sssd --debug-to-files instead. Barely nothing shows up in
those logs, if i don't use it with the -d10 option.
Even thou -d10 is used, nothing is printed to the krb5_child.log, so i
guess maybe the kerberos part is ok.
Here's the ldap part
ldap_uri = lda
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2010 10:06 AM, Patrik Martinsson wrote:
> Hello,
>
> I've successfully setup'ed sssd on our systems to connect to our
> Microsoft AD with ldap
> authentication, now i want to use kerberos instead, and have I of course
> ran into some proble
Hello,
I've successfully setup'ed sssd on our systems to connect to our
Microsoft AD with ldap
authentication, now i want to use kerberos instead, and have I of course
ran into some problems :)
To start with, I'm not to familiar with kerberos so go easy on me here.
I've successfully created a
10 matches
Mail list logo