DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40826>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40826 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-10 09:51 ------- (In reply to comment #15) > Thought about this again... > And I don't think this solution is valid. > By convention all crypto functions throughout the SDK API accept explicit > provider. > If you can find another exception to this rule I may understand and drop > this... > But if xmlsec is the only exception, than it should sync up. xmlsec/jsr 105 are at a higher layer than the JCE APIs. I still think there should be a workaround to your problem. Something is happening in your code that causes the PrivateKey's provider to be different than what is in the JRE's list of Providers. Have you tried the solution in this bug report, that is: Security.addProvider(p); KeyStore.getInstance("PKCS11"); -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
