Bug 1750516

Summary: GDM initial setup fails to identify that it is connected to an IPA server
Product: Red Hat Enterprise Linux 8 Reporter: Joe Wright <jwright>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0CC: cww, hdegoede, jkoten, modehnal, tpelka
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: accountsservice-0.6.50-8.el8 gdm-3.28.3-27.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:09:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joe Wright 2019-09-09 19:03:12 UTC
Description of problem:
- GDM initial setup fails to identify that the system is connected to an IPA server

Version-Release number of selected component (if applicable):
- gdm-3.28.3-20.el8.x86_64

How reproducible:
- 100%

Steps to Reproduce:
1. Install normal redhat 8 release
2. register to redhat network with subscription-manager
3. install ipa client ("yum install ipa-client")
4. connect to network authentication (IDM):
ipa-client-install --hostname xxx.our.network --mkhomedir --enable-dns-updates
5. Observe that after reboot, on the console, the redhat welcome screen will appear and ask for user creation.

Actual results:
GDM forces you to create a local user

Expected results:
- System should identify that it is connected to centralized authentication and skip local user creation

Additional info:

Comment 5 Michal Odehnal 2020-01-14 15:01:46 UTC
New versions do not force me to create the user if I have ipa-client setup done. Switching to VERIFIED.

Comment 7 errata-xmlrpc 2020-04-28 16:09:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1766