Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2227308

Summary: [DDF] Is there any other way where I can display the user data without domain?
Product: Red Hat Enterprise Linux 8 Reporter: Direct Docs Feedback <ddf-bot>
Component: DocumentationAssignee: lmcgarry
Documentation sub component: DDF QA Contact:
Status: CLOSED MIGRATED Docs Contact:
Severity: medium    
Priority: high CC: cilmar, dcamilof, lmcgarry, rhel-docs, sbose
Version: 8.0Keywords: Documentation, MigratedToJIRA
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-08 13:49:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-07-28 16:33:30 UTC 
Is there any other way where I can display the user data without domain?

IPA:
[root@ipa-client ~]# ipa config-show
  Maximum username length: 32
  Maximum hostname length: 64
  Home directory base: /home
  Default shell: /bin/sh
  Default users group: ipausers
  Default e-mail domain: lab.example.net
  Search time limit: 2
  Search size limit: 100
  User search fields: uid,givenname,sn,telephonenumber,ou,title
  Group search fields: cn,description
  Enable migration mode: True
  Certificate Subject base: O=LAB.EXAMPLE.NET
  Password Expiration Notification (days): 4
  Password plugin features: AllowNThash
  SELinux user map order: guest_u:s0$xguest_u:s0$user_u:s0$staff_u:s0-s0:c0.c1023$sysadm_u:s0-s0:c0.c1023$unconfined_u:s0-s0:c0.c1023
  Default SELinux user: unconfined_u:s0-s0:c0.c1023
  Default PAC types: MS-PAC, nfs:NONE
  Default user authentication types: otp
  Enable adding subids to new users: False
  IPA masters: ipa-master.lab.example.net, ipa-replica.lab.example.net
  IPA master capable of PKINIT: ipa-master.lab.example.net, ipa-replica.lab.example.net
  IPA CA servers: ipa-master.lab.example.net, ipa-replica.lab.example.net
  IPA CA renewal master: ipa-master.lab.example.net
  IPA KRA servers: ipa-master.lab.example.net
  Domain resolution order: example.net:lab.example.net
  IPA DNS servers: ipa-master.lab.example.net, ipa-replica.lab.example.net

Env:
[root@ipa-master ~]# rpm -q ipa-server
ipa-server-4.9.10-9.module+el8.7.0+17437+cf46f77f.x86_64
[root@ipa-master ~]# rpm -q sssd
sssd-2.7.3-4.el8_7.3.x86_64


Actual Results:
# id aduser1
uid=1821401104(aduser1) gid=1821401104(aduser1) groups=1821401104(aduser1),1821400513(domain users)

Expected:
# id aduser1
uid=1821401104(aduser1) gid=1821401104(aduser1) groups=1821401104(aduser1),1821400513(domain users)



Reported by: rhn-support-dcamilof

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_identity_management/configuring-the-domain-resolution-order-to-resolve-short-ad-user-names_configuring-and-managing-idm#annotations:be86bee8-bc31-43db-a6ca-da3bcb9c7343
Comment 1 Daniel Filho 2023-07-28 16:35:59 UTC 
Additional Reference:

https://github.com/SSSD/sssd/issues/3879
Comment 7 RHEL Program Management 2023-09-08 13:48:44 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-08 13:49:51 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.