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 1430723

Summary:	Git is unable to use HTTP(S)-SSO because of wrong check of libcurl
Product:	Red Hat Enterprise Linux 6	Reporter:	Petr Stodulka <pstodulk>
Component:	git	Assignee:	Petr Stodulka <pstodulk>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:	Lenka Špačková <lkuprova>
Priority:	unspecified
Version:	6.9	CC:	pstodulk
Target Milestone:	rc	Keywords:	FastFix
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Git cannot be used with HTTP or HTTPS and SSO Git provides the `http.delegation` configuration variable, which corresponds to the cURL `--delegation` parameter, for use when delegation of Kerberos tickets is required. However, Git included in Red Hat Enterprise Linux 6 contains irrelevant checks of the version of the libcurl library while required fixes are provided by a different version of libcurl on RHEL 6 systems. As a consqeuence, using Git with Single Sign-On on HTTP or HTTPS connections fails. To work around this problem, use the Git version provided by the _rh-git29_ Software Collection from Red Hat Software Collections.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:46:51 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:
Bug Depends On:	1368384
Bug Blocks:

Description Petr Stodulka 2017-03-09 12:26:55 UTC

Description of problem:
The last build git-1.7.1-8.el6 contains irrelevant checks of version of libcurl library. These were relevant for upstream versions, however the required fixes are provided in different version of libcurl on RHEL 6 systems. According to this problem, the new http.delegation option (provided in the last build of git) doesn't work and prints warning message when it is used instead of any other functionality.


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


How reproducible:


Steps to Reproduce:
1. git config --global http.delegation policy
2. git clone http://<your-repository>

Actual results:
warning about old libcurl that doesn't support delegation option


Expected results:
set delegation parameter for libcurl correctly.

Additional info:

Comment 1 Jan Kurik 2017-12-06 10:46:51 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/