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.
+++ This bug was initially created as a clone of Bug #1791262 +++
Description of problem:
With Chrome 80 in February, Chrome will treat cookies that have no declared SameSite value as SameSite=Lax cookies. Only cookies with the SameSite=None; Secure setting will be available for external access, provided they are being accessed from secure connections.
In mellon, this could prevent 3rd party IDPs from being accessed, see the upstream commit: https://github.com/latchset/mod_auth_mellon/pull/8
The upstream commit also links to an excellent Chromium blog post.
Version-Release number of selected component (if applicable):
whatever we ship in RHEL now
How reproducible:
unknown
Steps to Reproduce:
1. inspect the mellon cookie
2.
3.
Actual results:
SameSite=Lax
Expected results:
SameSite=None
Additional info:
(In reply to Roshan from comment #6)
> Hi Guys,
>
> What's the status of this? Has this been fixed for RHEL 7.8?
>
> Thanks,
> Roshan
No, this is so far not fixed in RHEL-7.
Hi Guys,
I see some activity here. Are we going to have the mellon package updated soon for RHEL 7? What can we do as a customer to get this patch released faster as the issue is getting more noticeable day by day?
Thanks,
Roshan
(In reply to Roshan from comment #31)
> Hi Guys,
>
> I see some activity here. Are we going to have the mellon package updated
> soon for RHEL 7? What can we do as a customer to get this patch released
> faster as the issue is getting more noticeable day by day?
>
> Thanks,
> Roshan
It is targetting 7.9.1. If you'd like to get access to test packages before the fix is QA-d and released, I can upload them somewhere.
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 (mod_auth_mellon bug fix and enhancement update), 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-2020:5036