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.

Description of problem:
Unable to use ldapsearch -Y GSSAPI to obtain TGT based on machine credentials via gssproxy

How reproducible:
always

Steps to Reproduce:
1. join machine to AD domain using "net ads join" command, storing machine credentials in /etc/krb5.keytab

2. Configure GSSPROXY to impersonate user trying to run ldapsearch:

[service/myimpersonator]
   mechs = krb5
   debug = yes
   krb5_principal = MYHOST$@EXAMPLE.COM
   cred_store = ccache:FILE:/var/lib/gssproxy/clients/krb5cc_%U
   cred_store = keytab:/etc/krb5.test.keytab
   cred_usage = initiate
   euid = 1000

3. Use ldapsearch:
bash$ export GSS_USE_PROXY=yes
bash$ ldapsearch -h dcduba.dublin.ad.s3group.com
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Local error (-2)
	additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (No Kerberos credentials available)


Actual results:
ldapsearch fails

Expected results:
ldapsearch should succeed

Additional info:
running 'gssproxy -i -d' does not provide enough debug information to troubleshoot the problem

Update: it starts to work if I replace:

   cred_store = keytab:/etc/krb5.test.keytab
with
   cred_store = client_keytab:/etc/krb5.test.keytab


Also note that krb5_principal parameter is still being ignored, i.e. if keytab also contains SPNs, it is quite a big chance it won't work.

Can we fix it?

Fixed merged upstream.

Ok, will the fix be available in RHEL7 at some stage, too?

(In reply to Ondrej from comment #3)
> Ok, will the fix be available in RHEL7 at some stage, too?

Hopefully.  We're not sure when yet.

krb5_principal option still not working, hence marking as FailedQA.

[root@dhcp207-130 ~]# rpm -q gssproxy
gssproxy-0.4.1-13.el7.x86_64
[root@dhcp207-130 ~]# 

Please find the attached file for verification steps with console output for reference.

Verified using gssproxy :: gssproxy-0.7.0-3.el7.x86_64

Marking BZ as verified. See attachment for console.log.

Created attachment 1284111 [details]
console.log

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/RHBA-2017:2033