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 is created as a clone of upstream ticket:
https://fedorahosted.org/ipsilon/ticket/157
Configure an SP for the Kerberos NameID and configure the IdP to support GSSAPI and form (--ipa yes --form yes for example) and ensure that Kerberos is allowed for the SP.
Now log in without a Kerberos ticket. The GSSAPI auth will fail and fall back to form.
You'll always be denied access.
The only server-side logging is a DEBUG level message:
Unavailable Name ID type [urn:oasis:names:tc:SAML:2.0:status:AuthnFailed]
Which isn't all that useful.
It should say something that the proper NameID was not satisfied, regardless of proper authentication.
Verified.
Version ::
Results ::
FIRST ON IDP:
[root@idp httpd]# vim /etc/ipsilon/idp/ipsilon.conf
# set these:
# debug = True
# tools.log_request_response.on = True
# ...
# db.conn.log = True
# log.screen = True
[root@idp httpd]# systemctl restart httpd
THEN ON SP:
[root@client1 httpd]# ipsilon-client-install --saml-auth /secure --saml-idp-url https://idp.testrelm.test/idp/ --saml-sp-name $(hostname -s) --saml-nameid kerberos
Generating a 2048 bit RSA private key
........................................+++
........+++
writing new private key to '/etc/httpd/saml2/client1.testrelm.test/certificate.key'
-----
admin password:
[root@client1 httpd]# systemctl restart httpd
[root@client1 httpd]# vim /etc/httpd/conf.d/ipsilon-saml.conf
# added MellonSamlResponseDump on
[root@client1 httpd]# systemctl restart httpd
Accessed https://client1.testrelm.test/secure from web browser and was presented login form. Entered testuser1 info and got this:
"Unauthorized
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required."
Then on IDP, check /var/log/httpd/error_log:
error_log:[Wed Sep 02 18:20:55.102605 2015] [:error] [pid 2722] [02/Sep/2015:18:20:55] ERROR: Authentication succeeded but it was not provided by NameID urn:oasis:names:tc:SAML:2.0:nameid-format:kerberos
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/RHEA-2015-2319.html