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.

Current lasso release (2.4.0 on 6.6 and 2.4.1(?) on upcoming 7.1) needs xml xsd:choices patches for Microsoft ADFS interoperability. Without these attempts to authenticate using mod_auth_mellon against our ADFS setup result in "Error processing authn response. Lasso error: [-427] When looking for an assertion we did not found it., referer [...]"

Patches from upstream lasso git:

http://repos.entrouvert.org/lasso.git/commit/?id=4ad4b673940ef72de1a62d7589cd0d86290086b1

http://repos.entrouvert.org/lasso.git/commit/?id=a27d1686b387a045607b5f0802001ea8863342cb

(Above patches are to be included in upcoming lasso 2.4.2 release.)

Patches apply cleanly to current lasso 2.4.0 and and fix 'assertion not found' problem.

Please consider including in next lasso update,

Thanks !

Jarek

Thank you for reporting this issue.

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://rhn.redhat.com/errata/RHBA-2015-1253.html