Title: Configure the Management Console for HTTPS in Standalone mode Title: Configure the Management Console for HTTPS in Domain mode https://issues.jboss.org/browse/EAP6-78 Add support for PKCS11 Keystores in security realms and HornetQ New keystore options were added in EAP 6.3.0.DR2. I didn't find them in documentation. It must be documented, please contact developers for details.
What we have added is PKCS#11 support according to the following documentation: - http://docs.oracle.com/javase/7/docs/technotes/guides/security/p11guide.html Most specifically the following section: - http://docs.oracle.com/javase/7/docs/technotes/guides/security/p11guide.html#JSSE What we have added is a 'provider' attribute for the key and trust store definitions in the security realms - the value specified here is passed into the relevant KeyStore.getInstance("PKCS11") calls where we initialise the key and trust stores so they can be backed by PKCS#11 implementation. The underlying PKCS#11 configuration is outside the scope of EAP, end users are responsible for the correct installation of their PKCS#11 hardware/software and adding the required entries to the java.security policy file. We are only facilitating the referencing of this configuration it is still their responsibility to define it correctly.
A note containing the explanation in comment 1 has been added to the 6.3.0 Security Guide. The new content was placed in the "About Security Token Service" chapter (as that seemed relevant to the general idea of using tokens) rather than the topics specified in the description in this ticket. If this is, for some reason, incorrect, leave a comment below and the note will be relocated.
Informal preview of the change is available here: http://docbuilder.usersys.redhat.com/22558/#Security_Token_Server_STS
This topic can be reviewed on DocStage here: http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Security_Guide/index.html#Security_Token_Server_STS
Scott: you are right, "About Security Token Service" chapter seems to be more relevant. verified during EAP 6.3.0.ER3 testing cycle
This is a beta-blocker so must be included in beta documentation. ER3 is going to be beta and therefore changing target milestone.