Using base64 encoding/decoding

Doug Carter dcarter at mercycorps.org
Thu Apr 23 09:04:49 EDT 2015


Hi All,

I’m fairly new to Shibboleth and SAML, so my apologies for the naive
question.

I’m running Shibboleth IDP 2.4.3 on CentOS 5, Tomcat 5, Java 1.6.  My
initial testing was setting up a Google Apps domain as an IDP for SSO,
which was successful. I am currently working on a new setup with an
application called Cornerstone. It has turned out to be much more
complicated than the Google setup. I think the problem is related to base64
encoding/decoding, as it’s mentioned in the Cornerstone documentation, but
I have yet to find a good example of how this configuration would look. The
idp-process log looks pretty good until Cornerstone calls the IDP for the
first time, which generates this exception:

07:15:32.468 - ERROR
[org.opensaml.ws.message.decoder.BaseMessageDecoder:208] -
Encountered error parsing message into its DOM representation
org.opensaml.xml.parse.XMLParserException: Unable to read XML from input
stream
        at
org.opensaml.xml.parse.StaticBasicParserPool.parse(StaticBasicParserP
ool.java:239) ~[xmltooling-1.4.4.jar:na]
        at
org.opensaml.ws.message.decoder.BaseMessageDecoder.unmarshallMessage(
BaseMessageDecoder.java:186) [openws-1.5.4.jar:na]
        at
org.opensaml.saml2.binding.decoding.HTTPRedirectDeflateDecoder.doDeco
de(HTTPRedirectDeflateDecoder.java:102) ~[opensaml-2.6.4.jar:na]
        at
org.opensaml.ws.message.decoder.BaseMessageDecoder.decode(BaseMessage
Decoder.java:79) [openws-1.5.4.jar:na]
        at
org.opensaml.saml2.binding.decoding.BaseSAML2MessageDecoder.decode(Ba
seSAML2MessageDecoder.java:70) ~[opensaml-2.6.4.jar:na]
        at
edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandl
er.decodeRequest(SSOProfileHandler.java:386)
~[shibboleth-identityprovider-2.4.3
.jar:na]
        at
edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandl
er.performAuthentication(SSOProfileHandler.java:211)
~[shibboleth-identityprovid
er-2.4.3.jar:na]
.
.
.
(full exception truncated for brevity)

I’m not 100% sure this is base64 related, but since I’m not explicitly
configuring it and since la parser is throwing an exception, I’m just
assuming that it is related. Has anyone got Shibboleth working with
Cornerstone? Using base64 encoding/decoding?

And tips, pointers or other advice would be greatly appreciated.

TIA,

Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150423/748aa9f6/attachment.html>


More information about the users mailing list