PicketLink module parsing exception

Solution Unverified - Updated -

Issue

The Identity Provider (IDP) Entity descriptor XML generated by our IDP infrastructure (based on Novell Access Manager (NAM)) produces a parsing exception while being processed by picketlink.
This parsing exceptions come from a couple of tags and attributes that PicketLink seems to get stuck into.
The troublesome tags are:

<md:SPSSODescriptor AuthnRequestsSigned="true" ID="id92GPKNKlFZk7.cvYVWEyL8QtWWw" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

The attribute AuthnRequestsSigned="true" is mandatory.

<md:IDPSSODescriptor ID="iduJi627sd6xPmFRXzCmY8zRXGu7U" WantAuthnRequestsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

The attribute WantAuthnRequestsSigned="true" is mandatory.

<md:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc" />

The entire tag produces a parsing exception.

<md:AssertionIDRequestService Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP" Location="https://lab.test.net/idp/saml2/soap" />

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.0.1, 6.1.0
    • PicketLink 2.1.3.Final, 2.1.6.Final

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.