sssd - GDM login
by Roberts Klotiņš
Hi,
I did send them to the list, but at debug level 7 sssd_PEOPLE.log file they
were about 15s KB in total and I sent them as an attachment. I was told to
await till the post is approved by moderator because size over 40KB.
I now put this same file edited for usernames and more descriptive host
names on
http://pastebin.com/ZRkmMgi6
sssd_PEOPLE.log was 15 KB
krb5_child.log was empty - 0 bytes.
With thanks,
Roberts
10 years, 6 months
Re: [SSSD-users] sssd-users Digest, Vol 18, Issue 25
by Roberts Klotiņš
Hi Thanks a lot for looking into this.
As you suspected - there is something that enterprise simple login added
into the config file file:
[sssd]
services = nss, pam
config_file_version = 2
domains = PEOPLE
[nss]
filter_users = root
filter_groups = root
[pam]
[domain/PEOPLE]
description = PEOPLE AD domain
id_provider = ad
auth_provider = ad
access_provider = ad
chpass_provider = ad
ad_server = srv1.people.local
ad_hostname = client1.people.local
ad_domain = PEOPLE.LOCAL
case_sensitive = false
enumerate = true
cache_credentials = true
simple_allow_users = usr1, usr2
However when I deleted the last line in this file I got the same result.
/var/log/secure
datet:42:54 robbie gdm-password]: pam_unix(gdm-password:auth):
authentication failure; logname=(unknown) uid=0 euid=0 tty=:1 ruser
= rhost= user=PEOPLE\usr2
datet:42:54 robbie gdm-password]: pam_sss(gdm-password:auth):
authentication failure; logname=(unknown) uid=0 euid=0 tty=:1 ruser=
rhost= user=PEOPLE\usr2
datet:42:54 robbie gdm-password]: pam_sss(gdm-password:auth): received for
user PEOPLE\usr2: 6 (Permission denied)
datet:42:59 robbie gdm-password]: pam_unix(gdm-password:auth): conversation
failed
datet:42:59 robbie gdm-password]: pam_unix(gdm-password:auth): auth could
not identify password for [PEOPLE\usr2]
datet:42:59 robbie gdm-password]: pam_sss(gdm-password:auth):
authentication failure; logname=(unknown) uid=0 euid=0 tty=:1 ruser=
rhost= user=PEOPLE\usr2
datet:42:59 robbie gdm-password]: pam_sss(gdm-password:auth): received for
user PEOPLE\usr2: 7 (Authentication failure)
It appears I may need to configure something in pam, but maybe that is not
the case??
Your help is much appreciated.
Roberts
On 24 October 2013 13:00, <sssd-users-request(a)lists.fedorahosted.org> wrote:
> Send sssd-users mailing list submissions to
> sssd-users(a)lists.fedorahosted.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.fedorahosted.org/mailman/listinfo/sssd-users
> or, via email, send a message with subject or body 'help' to
> sssd-users-request(a)lists.fedorahosted.org
>
> You can reach the person managing the list at
> sssd-users-owner(a)lists.fedorahosted.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sssd-users digest..."
>
>
> Today's Topics:
>
> 1. GDM login (Roberts Klotiņš)
> 2. Re: GDM login (Jakub Hrozek)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 24 Oct 2013 09:59:50 +0100
> From: Roberts Klotiņš <roberts.klotins(a)gmail.com>
> To: sssd-users(a)lists.fedorahosted.org
> Subject: [SSSD-users] GDM login
> Message-ID:
> <
> CALr2nHs9s41VbMVECCLrUQx1mfJYgsQFcLAxzT-0QzudHuaW8g(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> After 2 days of reading on Samba4 SSSD and AD login I am running into
> problems. I have set up
> - AD server with Samba 4.2 (CentOS 6.3) - domain PEOPLE.LOCAL
> - Fedora 19 machine
> - Windows XP machine joined the domain without problems, I can run
> dsa.msc successfully
>
> I want to achieve AD user login from gdm. I understand that I should create
> used with dsa.msc and then I don't know if I should add it through Fedora
> 19 user control panel. I tried it anyhow (was useful in debugging) but
> changes do not persist.
>
> I set up sssd (ver 1.11.1) it seems alright with AD options:
> - id and getent work for passwords and groups
>
> In my sssd.conf I have specified domain as [domain\PEOPLE]
> as all the correct server addresses etc are given there and it is easier to
> refer to the domain just by one name.
> sssd loads fine, getent passwd 'PEOPLE\user' works
>
> - realm discover gives this result
> realm discover --verbose PEOPLE.LOCAL
> * Resolving: _ldap._tcp.people.local
> * Performing LDAP DSE lookup on: 192.168.1.74
> ! Received invalid or unsupported Netlogon data from server
> people.local
> type: kerberos
> realm-name: PEOPLE.LOCAL
> domain-name: people.local
> configured: no
>
> I can add previously defined domain user via Settings - User : Enterprise
> with correct username and password, however this does not persist - if I
> close the user admin panel and then re-open it, the added user is gone.
>
> If I try to log on from GDM (user not listed so I use PEOPLE\user) I get
> authentication failure
> /var/log/secure gives these messages:
>
> date:00:19 host gdm-password]: pam_unix(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr1
> date:00:19 host gdm-password]: pam_sss(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr1
> date:00:19 host gdm-password]: pam_sss(gdm-password:auth): received for
> user PEOPLE\usr1: 6 (Permission denied)
> date:00:48 host gdm-password]: pam_unix(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr1
> date:00:48 host gdm-password]: pam_sss(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr1
> date:00:48 host gdm-password]: pam_sss(gdm-password:auth): received for
> user PEOPLE\usr1: 6 (Permission denied)
> date:01:40 host gdm-password]: pam_unix(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr2
> date:01:40 host gdm-password]: pam_sss(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr2
> date:01:40 host gdm-password]: pam_sss(gdm-password:auth): received for
> user PEOPLE\usr2: 6 (Permission denied)
> date:01:46 host gdm-password]: pam_unix(gdm-password:auth): conversation
> failed
> date:01:46 host gdm-password]: pam_unix(gdm-password:auth): auth could not
> identify password for [PEOPLE\usr2]
> date:01:46 host gdm-password]: pam_sss(gdm-password:auth): authentication
> failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> user=PEOPLE\usr2
> date:01:46 host gdm-password]: pam_sss(gdm-password:auth): received for
> user PEOPLE\usr2: 7 (Authentication failure)
> date:01:46 host gdm-password]: gkr-pam: no password is available for user
>
> Could someone point me in the right direction as to what is wrong with my
> setup. I have sorted some problems out by myself, but here I feel out of
> depth.
>
> Many thanks,
>
> Roberts
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.fedorahosted.org/pipermail/sssd-users/attachments/20131024/...
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 24 Oct 2013 12:01:11 +0200
> From: Jakub Hrozek <jhrozek(a)redhat.com>
> To: sssd-users(a)lists.fedorahosted.org
> Subject: Re: [SSSD-users] GDM login
> Message-ID: <20131024100111.GD4240(a)hendrix.redhat.com>
> Content-Type: text/plain; charset=utf-8
>
> On Thu, Oct 24, 2013 at 09:59:50AM +0100, Roberts Klotiņš wrote:
> > Hello,
> >
> > After 2 days of reading on Samba4 SSSD and AD login I am running into
> > problems. I have set up
> > - AD server with Samba 4.2 (CentOS 6.3) - domain PEOPLE.LOCAL
> > - Fedora 19 machine
> > - Windows XP machine joined the domain without problems, I can run
> > dsa.msc successfully
> >
> > I want to achieve AD user login from gdm. I understand that I should
> create
> > used with dsa.msc and then I don't know if I should add it through Fedora
> > 19 user control panel. I tried it anyhow (was useful in debugging) but
> > changes do not persist.
> >
> > I set up sssd (ver 1.11.1) it seems alright with AD options:
> > - id and getent work for passwords and groups
> >
> > In my sssd.conf I have specified domain as [domain\PEOPLE]
> > as all the correct server addresses etc are given there and it is easier
> to
> > refer to the domain just by one name.
> > sssd loads fine, getent passwd 'PEOPLE\user' works
> >
> > - realm discover gives this result
> > realm discover --verbose PEOPLE.LOCAL
> > * Resolving: _ldap._tcp.people.local
> > * Performing LDAP DSE lookup on: 192.168.1.74
> > ! Received invalid or unsupported Netlogon data from server
> > people.local
>
> ^^^ This is a Samba bug. I've seen it reported by another user, but I'm
> not sure if it's reported to Samba upstream.
>
> > type: kerberos
> > realm-name: PEOPLE.LOCAL
> > domain-name: people.local
> > configured: no
> >
> > I can add previously defined domain user via Settings - User : Enterprise
> > with correct username and password, however this does not persist - if I
> > close the user admin panel and then re-open it, the added user is gone.
>
> This sounds like Enterprise Logins bug, but let's resolve the Permission
> Denied first.
>
> >
> > If I try to log on from GDM (user not listed so I use PEOPLE\user) I get
> > authentication failure
> > /var/log/secure gives these messages:
> >
> > date:00:19 host gdm-password]: pam_unix(gdm-password:auth):
> authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr1
> > date:00:19 host gdm-password]: pam_sss(gdm-password:auth): authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr1
> > date:00:19 host gdm-password]: pam_sss(gdm-password:auth): received for
> > user PEOPLE\usr1: 6 (Permission denied)
> > date:00:48 host gdm-password]: pam_unix(gdm-password:auth):
> authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr1
> > date:00:48 host gdm-password]: pam_sss(gdm-password:auth): authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr1
> > date:00:48 host gdm-password]: pam_sss(gdm-password:auth): received for
> > user PEOPLE\usr1: 6 (Permission denied)
> > date:01:40 host gdm-password]: pam_unix(gdm-password:auth):
> authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr2
> > date:01:40 host gdm-password]: pam_sss(gdm-password:auth): authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr2
> > date:01:40 host gdm-password]: pam_sss(gdm-password:auth): received for
> > user PEOPLE\usr2: 6 (Permission denied)
> > date:01:46 host gdm-password]: pam_unix(gdm-password:auth): conversation
> > failed
> > date:01:46 host gdm-password]: pam_unix(gdm-password:auth): auth could
> not
> > identify password for [PEOPLE\usr2]
> > date:01:46 host gdm-password]: pam_sss(gdm-password:auth): authentication
> > failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
> > user=PEOPLE\usr2
> > date:01:46 host gdm-password]: pam_sss(gdm-password:auth): received for
> > user PEOPLE\usr2: 7 (Authentication failure)
> > date:01:46 host gdm-password]: gkr-pam: no password is available for user
> >
> > Could someone point me in the right direction as to what is wrong with my
> > setup. I have sorted some problems out by myself, but here I feel out of
> > depth.
> >
> > Many thanks,
> >
> > Roberts
>
> Can you attach your sssd.conf? I suspect that realmd/enterprise logins
> set up the simple access provider and the user is not included in the
>
>
> ------------------------------
>
> _______________________________________________
> sssd-users mailing list
> sssd-users(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/sssd-users
>
>
> End of sssd-users Digest, Vol 18, Issue 25
> ******************************************
>
--
==
Roberts Klotins
10 years, 6 months
GDM login
by Roberts Klotiņš
Hello,
After 2 days of reading on Samba4 SSSD and AD login I am running into
problems. I have set up
- AD server with Samba 4.2 (CentOS 6.3) - domain PEOPLE.LOCAL
- Fedora 19 machine
- Windows XP machine joined the domain without problems, I can run
dsa.msc successfully
I want to achieve AD user login from gdm. I understand that I should create
used with dsa.msc and then I don't know if I should add it through Fedora
19 user control panel. I tried it anyhow (was useful in debugging) but
changes do not persist.
I set up sssd (ver 1.11.1) it seems alright with AD options:
- id and getent work for passwords and groups
In my sssd.conf I have specified domain as [domain\PEOPLE]
as all the correct server addresses etc are given there and it is easier to
refer to the domain just by one name.
sssd loads fine, getent passwd 'PEOPLE\user' works
- realm discover gives this result
realm discover --verbose PEOPLE.LOCAL
* Resolving: _ldap._tcp.people.local
* Performing LDAP DSE lookup on: 192.168.1.74
! Received invalid or unsupported Netlogon data from server
people.local
type: kerberos
realm-name: PEOPLE.LOCAL
domain-name: people.local
configured: no
I can add previously defined domain user via Settings - User : Enterprise
with correct username and password, however this does not persist - if I
close the user admin panel and then re-open it, the added user is gone.
If I try to log on from GDM (user not listed so I use PEOPLE\user) I get
authentication failure
/var/log/secure gives these messages:
date:00:19 host gdm-password]: pam_unix(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr1
date:00:19 host gdm-password]: pam_sss(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr1
date:00:19 host gdm-password]: pam_sss(gdm-password:auth): received for
user PEOPLE\usr1: 6 (Permission denied)
date:00:48 host gdm-password]: pam_unix(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr1
date:00:48 host gdm-password]: pam_sss(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr1
date:00:48 host gdm-password]: pam_sss(gdm-password:auth): received for
user PEOPLE\usr1: 6 (Permission denied)
date:01:40 host gdm-password]: pam_unix(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr2
date:01:40 host gdm-password]: pam_sss(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr2
date:01:40 host gdm-password]: pam_sss(gdm-password:auth): received for
user PEOPLE\usr2: 6 (Permission denied)
date:01:46 host gdm-password]: pam_unix(gdm-password:auth): conversation
failed
date:01:46 host gdm-password]: pam_unix(gdm-password:auth): auth could not
identify password for [PEOPLE\usr2]
date:01:46 host gdm-password]: pam_sss(gdm-password:auth): authentication
failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost=
user=PEOPLE\usr2
date:01:46 host gdm-password]: pam_sss(gdm-password:auth): received for
user PEOPLE\usr2: 7 (Authentication failure)
date:01:46 host gdm-password]: gkr-pam: no password is available for user
Could someone point me in the right direction as to what is wrong with my
setup. I have sorted some problems out by myself, but here I feel out of
depth.
Many thanks,
Roberts
10 years, 6 months
Problems with sssd 1.11.1 on ubuntu 13.10
by Melvin Williams
I have installed sssd 1.11.1 from the repository on Ubuntu 13.10. First of
all when I tried to start sssd with the "emurate = true" option in the
domain section I get the following error:
[sssd] [confdb_get_domain_internal] (0x0010): Invalid value for enumerate
So I commented this out. Now I tried to start via command line: sssd -d
0xFFF0 -f
Doing so I found this in my error logs:
[load_backend_module] (0x0010): Unable to load ad module with path
(/usr/lib/x86_64-linux-gnu/sssd/libsss_ad .so), error:
/usr/lib/x86_64-linux-gnu/sssd/libsss_ad .so
There is a space in the library name "libsss_ad .so". Is this the name the
program is looking for? If so there must be a typo or something like this
in the code. If not and it is a configuration matter could someone please
tell me how to fix this issue.
Regards
10 years, 6 months
RHEL 6 ldap client can query a group, but cannot traverse groups of groups.
by ted.rush@faa.gov
Hi!
We have been working this problem for two weeks debugging. We have 389-ds running and multi-master with 3 RHEL6 servers and
a RHEL5. The RHEL5 ldap clients authenticate correctly to the RHEL6 389-ds directory server and with 'id' command can see
all groups a user belongs too.
The same command in a RHEL6 ldap client using sssd shows ONLY the primary group. If we change the ldap clients to point at
the RHEL5 389-ds directory server the same results occur. The one consistency is any RHEL6 ldap client we setup will
authenticate to either RHEL5 or RHEL6 but the entire list of groups that user belongs to do not transfer independent of
server version. We have enumerate set to true and we have ldap_group_member set to uniqueMember. These seems to point to the
ldap client as RHEL5 client works just fine and both RHEL5 and RHEL6 389-ds servers react the same but we're not sure how to
correct or is it a bug. HELP?
We had this posted in 389-users but were referred to the sssd list. id of
a user(id JSmith) only returns the primary group, not a complete list of
the groups that user belongs too. The getent group MyGroup lists the
subgroups by names but not the members. On a RHEL5 ldap client the same
entries provide a complete list of groups the user belongs to when entering
id JSmith. The getent group MyGroup also burrows down through subgroups to
list all users that belong to that group either directly or because a group
they belong to belongs to the group MyGroup. Any ideas? The problem seems
to be with RHEL 6 ldap client and some settings in sssd but not sure where
to go from here.
Thanks,
Ted
Ted Rush
Common ARTS Information System Security ISSO/POC
Common ARTS Software Development System Lead
(609) 485-5917
10 years, 6 months
authconfig and moving from ldap to sssd on redhat6 boxes
by Olivier OLG
Hello there,
two observations about using authconfig to switch from ldap to
sssd on redhat6 :
1- why does authconfig stops sssd when it's launched with
"--enablesssd --enablesssdauth" flags (rather than restarting
the service) ?
2- I also use "--disableldap --disableldapauth --enablepamaccess"
flags and it appears that authconfig has updated properly all
files in /etc/pam.d/* except for /etc/pam.d/sudo :
# grep ldap /etc/pam.d/sudo
auth sufficient pam_ldap.so use_first_pass
account [default=bad success=ok user_unknown=ignore] pam_ldap.so
password sufficient pam_ldap.so use_authtok
session optional pam_ldap.so
Nothing critical in all that (to me at least), since I found workarounds,
however may be this should be fixed with next authconfig versions ?
Best regards
---
Olivier
10 years, 6 months
Re: [SSSD-users] authenticating against all sub-domains in AD forest
by a t
Hi Jakub,
I sent the logs you requested directly to you as you suggested so I didnt need to obfuscate thrm. However, I am not sure you received the email?
Thanks,
Matthew
--- Original Message ---
From: "Jakub Hrozek" <jhrozek(a)redhat.com>
Sent: 1 October 2013 19:44
To: sssd-users(a)lists.fedorahosted.org
Subject: Re: [SSSD-users] authenticating against all sub-domains in AD forest
On Sun, Sep 29, 2013 at 02:41:11PM +0100, a t wrote:
> Hi,
>
> That user, test.user, is in the subdomain a.domain.org.
>
> Thr logs mark domain.org as a subdomain of b.domain.org. however, this is not correct - domain.org is the root domain of which b.domain.org is a subdomain. We do not have users in the root domain. All users are in other subdomains.
>
> I believe the user I tested in another subdomain, mhunt.test(a)a.domain.org did not show in the logs. When I tried to log in with mhunt.test(a)a.domain.org the logs show that sssd believes that domain "a" is a subdomain if b.domain.org rather than another subdomain of domain.org.
>
> I might have to ask if I can send un-obfuscated incase I am adding in confusion!
>
> Thanks,
>
> Matthew
Interesting, I see no fatal erorr in the domain log, then. Could you
also paste the tail of /var/log/secure after the auth and also put
debug_level directive into the [pam] section as well?
If you prefer, you can send the logs directly to me without obfuscation.
_______________________________________________
sssd-users mailing list
sssd-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-users
10 years, 6 months
ldap_group_search_base filtering
by Bright, Daniel
Hello,
I am migrating from pam_ldap to sssd and previously in my ldap.conf I was able to use this to filter out groups based on the "host" attribute using the nss_base_group feature:
nss_base_group ou=Groups,dc=some,dc=company,dc=com?one?|(host=\2A)(host=somehost.test.com)(host=test)
I am trying to do the same thing in SSSD and can't figure it out, I have added everything past the first ? above to my ldap_group_search_base stanza but it doesn't work as expected, is it a syntax thing or is there a different way of doing this (or am I out of luck?)?
Thanks in advance!
-DBright
10 years, 6 months
Dynamic DNS update with AD backend using wrong hostname for nsupdate
by Chris Hartman
Hi guys,
I've noticed that dynamic DNS updates aren't working with my setup. Client
is Ubuntu 12.04 using SSSD 1.11.1. Server 2008 AD on backend.
Here's my config:
[sssd]
config_file_version = 2
debug_level = 0
reconnection_retries = 3
sbus_timeout = 30
services = nss, pam
domains = DOMAIN
[pam]
debug_level = 0
[nss]
debug_level = 10
filter_users =
root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm
filter_groups =
root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm
reconnection_retries = 3
[domain/DOMAIN]
debug_level = 10
ad_domain = DOMAIN.local
id_provider = ad
auth_provider = ad
chpass_provider = ad
access_provider = ad
enumerate = true
cache_credentials = true
# Will check unixHomeDirectory LDAP attribute for a value first
fallback_homedir = /home/%u
ldap_user_home_directory = unixHomeDirectory
dyndns_update = true
dyndns_update_ptr = true
dyndns_refresh_interval = 30
ldap_schema = ad
ldap_id_mapping = true
When viewing debug output, I saw this under the domain log:
(Mon Oct 14 10:33:01 2013) [sssd[be[wysu]]] [be_nsupdate_create_fwd_msg]
(0x0400): -- Begin nsupdate message --
server milkdud.DOMAIN.local
realm DOMAIN.LOCAL
update delete snickers. in A
send
update delete snickers. in AAAA
send
update add snickers. 3600 in A 10.11.12.41
send
When I try to perform this update manually using `nsupdate -g` it will fail
with the following error:
tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor
code may provide more information, Minor = Server not found in Kerberos
database.
However, if I replace 'snickers.' with the FQDN 'snickers.DOMAIN.local' the
update will happen fine.
I'm assuming this is an SSSD configuration error since the FQDN is not
being used during the update. Any ideas how to solve this?
Thanks!
-Chris
10 years, 6 months