Problems with validating signatures in OpenSAML 3.0

[Brent Putman]

On 9/12/16 8:52 AM, Rod Widdowson wrote:
>> Any idea what's going on here?
>> org.opensaml.xmlsec.signature.support.SignatureException: Could not load a
> signature validation provider implementation via service API
>> at
> org.opensaml.xmlsec.signature.support.SignatureValidator.getSignatureValidat
> ionProvider(SignatureValidator.java:70)
>
> You need a
> META-INF\services\org.opensaml.xmlsec.signature.support.SignatureValidationP
> rovider
>
> File somewhere in your path with a single line which is the name of a class
> that implements
> org.opensaml.xmlsec.signature.support.SignatureValidationProvider
>
> http://svn.shibboleth.net/view/java-opensaml/trunk/opensaml-xmlsec-impl/src/
> main/resources/META-INF/services/org.opensaml.xmlsec.signature.support.Signa
> tureValidationProvider?view=log
>
> Rod

What Rod says is indeed nominally the root cause of the error: it
apparently sees/finds no META-INF/services entry on your classpath for
that services API interface.

But: do you already have opensaml-xmlsec-impl as a dependency within
your project, and on your runtime classpath?  If not: you should add
it.  If so (and I think you must have, otherwise you would not have
gotten this far): then for some reason the Services API call is not
working, and you have to figure out why.  This would be a new problem. 
That should always work, I don't know of any reason why it shouldn't.

If you do add a META-INF/services entry to your own jar file or project
classpath and it fixes things, I'd be interested to know that.  The one
in opensaml-xmlsec-impl should have been sufficient.  If the services
API were completely broken in your environment for some reason, then
lots and lots of other stuff should have failed long before you got to
the point of validating the signature.  All the XMLObject provider
stuff would have been non-functional, for example.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160912/b0f29ad6/attachment.html>