On Fri, Apr 21, 2017 at 07:58:53AM +0200, Troels Hansen wrote:
> Thanks both Jakub and Stephen
>
> That explains it. It didn't seem really clear from the man pages
But that's wrong, ideally there should be no things you 'need to know'.
Let's fix the man page with:
https://pagure.io/SSSD/
Ubuntu 16.04.2
samba 4.3.11+dfsg-0ubuntu0.16.04.6
sssd 1.13.4-1ubuntu1.2
Windows Server 2008 R2 Standard
Have 2 sites with the above setup.
Each site has 1 ubuntu/samba server authenticating to 1 Windows Server 2008 R2
server running Active Directory
Site 1 works as expected. Traditional linux s
Thanks both Jakub and Stephen
That explains it. It didn't seem really clear from the man pages and
looking at the SSSD log's didn't seem to reveal it either, so I guess its just
one of those things that you need to know.
- On Apr 20, 2017, at 5:18 PM, Jakub Hrozek jhro...@redhat.com
On 04/20/2017 11:08 AM, Troels Hansen wrote:
> I'm trying to force SSSD to only communicate encrypted, because of company
> rules.
> I think i'm missing something:
>
> SSSD configured with: id_provider = ad
>
> and DNS service resolution is enabled (default)
>
> I have tried about every combina
On Thu, Apr 20, 2017 at 05:08:02PM +0200, Troels Hansen wrote:
> I'm trying to force SSSD to only communicate encrypted, because of company
> rules.
> I think i'm missing something:
>
> SSSD configured with: id_provider = ad
>
> and DNS service resolution is enabled (default)
>
> I have tri
I'm trying to force SSSD to only communicate encrypted, because of company
rules.
I think i'm missing something:
SSSD configured with: id_provider = ad
and DNS service resolution is enabled (default)
I have tried about every combination of:
ldap_id_use_start_tls = true
ldap_service_port
