When trying to connect with CLI to server using PKCS11 (and FIPS):
- CLI can connect with the old workaround described in 7.0 documentation
- When providing -Dwildfly.config.url, no matter what's in the path (even if it's non-existent file), CLI throws following error:
- If I set up BOTH the JAVA_OPTS and wildfly-config.xml, the config is parsed properly (throwing errors in case of wrong path, malformed xml etc.) and CLI connects successfully.
I'm marking it as a blocker now, since this is basically the functionality required by EAP7-610. But the old workaround still works just fine, so I think this isn't high priority if we're ok to postpone the RFE.