<div dir="ltr"><div>Hi,</div><div><br></div><div>I'm Marek Zupnik. It's my first message for this list but for some time I've been keeping my eyes on what's happening in wildfly development. </div><div><br>
</div><div>I'm writing regarding to the issue about lack of support for PKCS12 keystores in security realms (<a href="https://issues.jboss.org/browse/WFLY-2229">https://issues.jboss.org/browse/WFLY-2229</a>). I wanted to migrate my system to Wildfly but in my case it is a blocking issue. I have to use keystore in PKCS12 format in which I'm storing, among others, https private key.</div>
<div><br></div><div>I forked Wildfly on github and made a simple fix for this issue which consists in additional parameter "keystore-type" for keystore configuration. Based on this parameter I'm able to create appropriate keystore type.</div>
<div><br></div><div>Config sample:</div><div><keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx" keystore-type="PKCS12" alias="https"/></div>
<div><br></div><div>The changes are in my fork on github (keystore_type branch):</div><div><a href="https://github.com/mzupnik/wildfly/tree/keystore_type">https://github.com/mzupnik/wildfly/tree/keystore_type</a></div><div>
<br></div><div>Before I will try to do push request, could you answer me if it is acceptable solution according to your architecture concept? If not, could you give me some tips how to resolve it in other way? I care about this fix before 9. release.</div>
<div><br></div><div>Kind Regards,</div><div>Marek Zupnik</div></div>