Using base64 encoding/decoding

[Brent Putman]

On 4/23/15 9:04 AM, Doug Carter wrote:
> Hi All,
>
> 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.

Probably not.  As Peter already said, how the binding works is dictated
by the spec, there's nothing to configure.

> Has anyone got Shibboleth working with Cornerstone? Using base64
> encoding/decoding?

All the front-channel SAML bindings use mandatory Base64 encoding one
way or another.  It's inherent to the defined SAML 2 bindings. So this
is really a red herring.


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

The most likely problem is you/they are using the wrong binding.  Looks
like it's being delivered to the IdP's HTTP-Redirect DEFLATE binding
endpoint.  If they're sending using the HTTP POST binding, then they
would need to use a different IdP endpoint.  Or possibly tell them (or
configure if you have access) to switch to Redirect binding - many
vendors support a choice of either.  Fwiw, the Shib SP generally
prefers the Redirect binding by default.

The other likely problem is they simply have a bug in their binding
implementation.  I don't know anything about them, but if their SAML
implementation is widely used, that's unlikely.  But possible.


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