When calling migrate on web with defined https connector as
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true"> <ssl key-alias="javaserver" password="tomcat" certificate-key-file="${jboss.server.config.dir}/server-cert-key-rsa.jks" certificate-file="${jboss.server.config.dir}/server-cert-key-rsa.jks" ca-certificate-file="${jboss.server.config.dir}/ca-cert.jks" keystore-type="JKS" truststore-type="JKS"/>
it fails on migrating Web subystem ssl config password attribute to keystore-password in security realms, see
"migration-error" => {"operation" => {"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "jbossweb-migration-security-realm1"),("authentication" => "truststore")],"keystore-path" => expression "${jboss.server.config.dir}/ca-cert.jks","keystore-password" => undefined,"keystore-provider" => "JKS","operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"}},"result" => {"outcome" => "failed","failure-description" => "WFLYCTL0155: keystore-password may not be null","rolled-back" => true}}},"failure-description" => "WFLYWEB0005: Migration failed, see results for more details.","rolled-back" => true}
Marking as blocker as this operation fails for migrating of critical part of Web subsystem configuration as is HTTPS ssl configuration.
- is cloned by
-
WFLY-5226 [Migration operation] [Web to Undertow] Web subsystem attribute "password" should be migrated as "keystore-password" for both
-
- Closed
-
