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 2063224 - Unable to lookup AD user if the request is not redirected to correct domain
Summary: Unable to lookup AD user if the request is not redirected to correct domain
Keywords:
Status: CLOSED DUPLICATE of bug 2033347
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: sssd
Version: 9.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: sssd-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-11 14:33 UTC by Abhijit Roy
Modified: 2022-04-07 14:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-07 14:06:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-115359 0 None None None 2022-03-11 14:50:19 UTC

Description Abhijit Roy 2022-03-11 14:33:50 UTC 
Description of problem:

Unable to lookup AD user if the request is not redirected to correct domain

Workaround: Use ad_enabled_domains

(2022-03-03 10:51:30): [be[example.com]] [get_server_status] (0x1000): Status of server 'RHEL.example.com' is 'name resolved'
...
(2022-03-03 10:51:30): [be[example.com]] [ad_sasl_log] (0x0040): SASL: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (KDC has no support for encryption type) <--
(2022-03-03 10:51:30): [be[example.com]] [sasl_bind_send] (0x0020): ldap_sasl_interactive_bind_s failed (-2)[Local error] <--
(2022-03-03 10:51:30): [be[example.com]] [sasl_bind_send] (0x0080): Extended failure message: [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (KDC has no support for encryption type)]
(2022-03-03 10:51:30): [be[example.com]] [child_sig_handler] (0x1000): Waiting for child [379042].
(2022-03-03 10:51:30): [be[example.com]] [child_sig_handler] (0x0100): child [379042] finished successfully.
(2022-03-03 10:51:30): [be[example.com]] [sdap_cli_connect_recv] (0x0040): Unable to establish connection [1432158227]: Authentication Failed<--

As a result, sssd is segfaulting.

Mar  3 07:46:05 RHELbox dbus-daemon[1255]: [system] Successfully activated service 'org.freedesktop.sssd.infopipe'
Mar  3 07:46:05 RHELbox systemd[1]: Started SSSD IFP Service responder.
Mar  3 07:46:05 RHELbox sssd_be[227946]: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (KDC has no support for encryption type)
Mar  3 07:46:05 RHELbox sssd_be[227946]: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (KDC has no support for encryption type)
Mar  3 07:46:05 RHELbox kernel: sssd_be[227946]: segfault at 0 ip 00007f60a807fb7e sp 00007ffc937aa888 error 4 in libc-2.28.so[7f60a7f27000+1bc000]
Mar  3 07:46:05 RHELbox kernel: Code: c8 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 <c5> fe 6f 0f c5 f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9
Mar  3 07:46:05 RHELbox systemd[1]: Started Process Core Dump (PID 277472/UID 0).
Mar  3 07:46:05 RHELbox systemd-coredump[277473]: Resource limits disable core dumping for process 227946 (sssd_be).
Mar  3 07:46:05 RHELbox systemd-coredump[277473]: Process 227946 (sssd_be) of user 0 dumped core.
Mar  3 07:46:05 RHELbox systemd[1]: systemd-coredump: Succeeded.
Mar  3 07:46:05 RHELbox sssd_be[277476]: Starting up
Mar  3 07:46:05 RHELbox sssd_be[277476]: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (KDC has no support for encryption type)

Version-Release number of selected component (if applicable):

sssd-2.5.2-2.el8_5.4.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Alexey Tikhonov 2022-03-11 14:45:57 UTC 
(In reply to Abhijit Roy from comment #0)
> 
> GSSAPI Error: Unspecified GSS failure.  Minor code may provide more
> information (KDC has no support for encryption type) <--

Is the system in FIPS mode?


> As a result, sssd is segfaulting.
> Mar  3 07:46:05 RHELbox systemd-coredump[277473]: Resource limits disable
> core dumping for process 227946 (sssd_be).

Can you reproduce this?
If yes, please enable coredump and provide it.
Comment 3 Abhijit Roy 2022-03-11 18:48:00 UTC 
Hi,

Cus is not able to share coredump. But I have logs with and without `ad_enabled_domains`.
Comment 4 Alexey Tikhonov 2022-03-11 19:09:33 UTC 
(In reply to Abhijit Roy from comment #3)
> Hi,
> 
> Cus is not able to share coredump. But I have logs with and without
> `ad_enabled_domains`.

Is it reproducible? Maybe at least a backtrace?

And there is no answer about FIPS mode.
Note You need to log in before you can comment on or make changes to this bug.