Error on signing outbound SAML message

[Bogdan Albei]

Let me tell you a bit about my set up, which is a bit non-standard. I am
not using Shibboleth as a standalone webapp, I am integrating Shibboleth
via maven into our own webapp and there are internal architectural reasons
for that. However, I am using Shibboleth and Opensaml with their own
dependencies, I'm not overriding anything.
Your last email prompted me to have a look at the difference between the
dependencies of my app and those of the standard Shibboleth webapp. Nothing
major besides this: I was using xmlsec-1.5.7.jar while Shibboleth 3.2.1 was
using xmlsec-2.0.5.jar. I had a look at opensaml-security-api 3.2.0 and
that is what it's pulling, xmlsec-1.5.7. So I excluded that dependency and
included explicitly xmlsec-2.0.5.
And it works fine :).
Thank you Scott for putting up with my non-standard implementation and for
guiding me to the solution.

Cheers,
Bogdan

On 6 January 2016 at 16:44, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 1/6/16, 11:39 AM, "users on behalf of Bogdan Albei" <
> users-bounces at shibboleth.net on behalf of bogdan.albei at callsign.com>
> wrote:
>
>
>
> >Indeed, I tried that previously and it made no difference. By the way,
> the metadata is the idp part from testshib.org <http://testshib.org>
> slightly adapted to use localhost for the initial development phase.
>
> Right, and you can see that obviously this makes no sense. Nobody else is
> having the problem out of the box, ergo this is an environmental issue of
> some kind.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Bogdan Albei
Senior Platform Engineer
Callsign Inc.
[C] bogdan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160106/1a7680cb/attachment.html>