<div dir="ltr">Afraid it's hardcoded to use Bouncycastle as the provider. You can open a JIRA for it though.</div><div class="gmail_extra"><br><div class="gmail_quote">On 14 April 2016 at 13:22, Akshay Kini <span dir="ltr"><<a href="mailto:kga.official@gmail.com" target="_blank">kga.official@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Folks,<br><br><b>Does Keycloak adhere to the JCA (Java Cryptography Architecture)? i.e. if I change the JVM's cryptography provider to a custom one, Keycloak should use that provider for all cryptography operations.</b><br><br></div><div>Some context for this:<br></div>In our use case, our entire JVM runs with a FIPS compliant Cryptography Provider being available. If code that is running, on it is using the JCA correctly, then that code will also be FIPS ready.<br><br></div>Thanks,<br></div>Regards,<br></div>Akshay<br><div><div><div><br><br></div></div></div></div>
<br>_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br></blockquote></div><br></div>