OpenSAML user discussion

My fault, I haven't notice that winzip stripped the path from the config.xml 
when the file was updated in the xmlsec-1.0.5.jar - that caused the problem.

After I made it more carefully OpenSAML works with updated config.xml without 
problems.

Another question:
I am looking for documentation on configuring OpenSAML to use different JCE 
providers, specifically for signatures. Could you confirm that the right 
thing to do is to modify config.xml as following:

1) Add new provider to the  JCEAlgorithmMappings, i.e.
         <Provider Id="JsafeJCE"
                   Class="com.rsa.jsafe.provider.JsafeJCE"
                   Info="JsafeJCE Provider"
                   ProviderURL="http://java.rsa.com/"; />

position doesn't matter, new provider can be added as the last one

2) Add new provider as the 1st provider to 2 Signature Algorithms 
under <!-- Signature Algorithms -->

<Algorithm URI="http://www.w3.org/2000/09/xmldsig#dsa-sha1";;
Description="Digital Signature Algorithm with SHA-1 message digest"
            <ProviderAlgo ProviderId="JsafeJCE"
                          JCEName="DSAWithSHA1" />

<Algorithm URI="http://www.w3.org/2000/09/xmldsig#rsa-sha1";;
Description="RSA Signature with SHA-1 message digest"
            <ProviderAlgo ProviderId="JsafeJCE"
                          JCEName="SHA1withRSA" />


It seems to work but I can't verify that OpenSAML is actually using new 
provider for signature and have no control over which one it is using. There 
are many more signature algorithms defined in config.xml

Is there any documentation on how to configure JCE provider in OpenSAML? In 
the above configuration how can I actually confirm that new JCE provider is 
used for signatures?
 

Thanks!

Konstantin