As SSSD seems to work with others tools (SSH, SMTP auth...), as the OP doesn't described his error very clearly, I do think you can't say the error is SSSD for sure. You can expect the error is from SSSD, you can even be sure of that. But as this error is not clear, how dare be so sure? For 'we do not know, ask sssd' I'm not included in that "we". When I don't know, most generally I try to learn. 2016-10-12 14:34 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>:> On Wed, 12 Oct 2016 14:16:12 +0200 > mathias dufresne <infractory at gmail.com> wrote: > > > As he wrote that SSH and SMTP auth and others stuffs are working, I > > would say SSSD should work. > > As he wrote there is an issue with Samba, I'd like to understand how > > he is using Samba, what is the exact error and what he's doing to get > > that error. > > > > Samba should be able to live with other tools. We should be able to > > able to speak here about Samba working with other tools. But that > > certainly is because I'm sometimes radical in what represent open > > source world to me. > > > > I have nothing against sssd, but Samba recommends using winbind instead. > > This problem is very likely to be an sssd problem, users with numbers > instead of names work with winbind: > > rowland at devstation:~$ getent passwd samdom\\102220 > 102220:*:10011:10000:102220:/home/102220:/bin/false > > This is, of course, on AD, but the principal is the same, so the > question must be 'why doesn't this work with sssd' and the answer will > be 'we do not know, ask sssd' > > Rowland > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
On Wed, 12 Oct 2016 15:06:08 +0200 mathias dufresne <infractory at gmail.com> wrote:> As SSSD seems to work with others tools (SSH, SMTP auth...), as the OP > doesn't described his error very clearly, I do think you can't say the > error is SSSD for sure. You can expect the error is from SSSD, you > can even be sure of that. But as this error is not clear, how dare be > so sure? > > For 'we do not know, ask sssd' I'm not included in that "we". When I > don't know, most generally I try to learn. >When I said 'we' I meant the Samba team. sssd is not a part of Samba, so whilst it is possible to use it with Samba, Samba does not know all the nuances of using it, so hence, ask sssd-users for help with it. Rowland
2016-10-12 15:26 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>:> On Wed, 12 Oct 2016 15:06:08 +0200 > mathias dufresne <infractory at gmail.com> wrote: > > > As SSSD seems to work with others tools (SSH, SMTP auth...), as the OP > > doesn't described his error very clearly, I do think you can't say the > > error is SSSD for sure. You can expect the error is from SSSD, you > > can even be sure of that. But as this error is not clear, how dare be > > so sure? > > > > For 'we do not know, ask sssd' I'm not included in that "we". When I > > don't know, most generally I try to learn. > > > > When I said 'we' I meant the Samba team. sssd is not a part of Samba, > so whilst it is possible to use it with Samba, Samba does not know > all the nuances of using it, so hence, ask sssd-users for help with > it. >There are here other people than Samba team. Some could be interested in that issue, now or later, because they have the issue or because they want to learn something. That's the point of open source: sharing. Sharing the source, ok, but sharing the knowledge too.