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 1434845 - FreeIPA client <= 4.4 fail to parse 4.5 cookies
Summary: FreeIPA client <= 4.4 fail to parse 4.5 cookies
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 6.10
Assignee: IPA Maintainers
QA Contact: ipa-qe
Depends On:
Blocks: 1441160
TreeView+ depends on / blocked
Reported: 2017-03-22 13:16 UTC by Petr Vobornik
Modified: 2017-06-12 14:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1441160 1459153 (view as bug list)
Last Closed: 2017-06-12 14:02:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Proposed patch that can be applied after RHEL 6.9 upstream patches [0] (2.86 KB, patch)
2017-03-24 14:00 UTC, Standa Laznicka
no flags Details | Diff
Proposed patch that can be applied after RHEL 6.9 upstream patches [1] (1002 bytes, application/mbox)
2017-03-24 14:01 UTC, Standa Laznicka
no flags Details

Description Petr Vobornik 2017-03-22 13:16:19 UTC
Cloned from upstream: https://pagure.io/freeipa/issue/6774

Older clients are also affected by #6718. I noticed the problem when I was testing the vault with FreeIPA 4.4 client and FreeIPA 4.5 server. https://github.com/freeipa/freeipa/pull/532 needs to be backported.

ipa: ERROR: unable to parse cookie header 'ipa_session=MagBearerToken=MiIjMRJWMAl1%2bazkGlIRns2iysA7wxc%2bpSenQtZEMKXSsRAXEcnw2wHEyzOyh8RHgIm5K7YvX1k1tPotRM2ztegX4ODAmOe26%2fP4FLu68AupejDBNmNIENfasrNhUiPowugkkRXBOD%2b%2bsGFFMUZ%2bP7AYPHoW3bE3uN4ftRQwftE11EFTti4a9fVwB4SLKiuU&expiry=1489670819868611;Max-Age=1800;path=/ipa;httponly;secure;': unsupported operand type(s) for +: 'NoneType' and 'datetime.timedelta'

Comment 3 Standa Laznicka 2017-03-24 14:00:34 UTC
Created attachment 1266100 [details]
Proposed patch that can be applied after RHEL 6.9 upstream patches [0]

Comment 4 Standa Laznicka 2017-03-24 14:01:15 UTC
Created attachment 1266101 [details]
Proposed patch that can be applied after RHEL 6.9 upstream patches [1]

Comment 10 Simo Sorce 2017-05-10 11:43:38 UTC
We can probably remove the Max-Age attribute with a rewrite instruction in the apache configuration, but I wonder if we should leave this as a workaround for impacted customers rather than doing it by default.
Max-Age is used to tell the browser when to throw away the cookie, and it is not fundamental, worst case browsers send an expired cookie and they need to renegotiate and will get a new cookie.

Comment 12 Simo Sorce 2017-05-11 14:20:19 UTC
Petr, what do you think ?

Comment 13 Pavel Vomacka 2017-06-05 17:03:06 UTC
FreeIPA 4.5.0(1) server sends Set-Cookie header with Max-Age string, that is set by SessionMaxAge directive in httpd configuration. This is part of the header which older clients cannot parse. Older clients understand the cookie with expiration expressed this way: Expires=time_when_cookie_expires. In this format: Expires=Mon, 05 Jun 2017 17:10:07 GMT;

Note You need to log in before you can comment on or make changes to this bug.