problem with quickstart ejb multi server on WildFly 26.0.1

[Sascha Janz]

Hello,

i try to get the quickstart ejb multiserver to work on wildfly 26.0.1

but when i execute jboss-cli -c --file=install-domain.cli

i get

   "outcome" => "success",
    "response-headers" => {"warnings" => [{
        "warning" => "WFLYCTL0449: Operation stop against the resource at address /host=master/server-config=server-two is deprecated, and it might be removed in future version. See the the output of the read-operation-description operation to learn more about the deprecation.",
        "level" => "WARNING",
        "operation" => {
            "address" => [
                ("host" => "master"),
                ("server-config" => "server-two")
            ],
            "operation" => "stop"
        }
    }]},
    "result" => "STOPPED"
}

...

org.jboss.as.cli.CommandFormatException: Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [
    ("host" => "master"),
    ("core-service" => "management"),
    ("security-realm" => "ejb-security-realm-1"),
    ("server-identity" => "secret")
]": Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [
    ("host" => "master"),
    ("core-service" => "management"),
    ("security-realm" => "ejb-security-realm-1"),
    ("server-identity" => "secret")
]"

what needs to be changed?

thanks for help.

regards 

Sascha

[cf...@redhat.com]

Looks like it's due to the removal of legacy security config. Since WildFly 25, standard configuration no longer include management/security-realm. Elytron subsystem resources are now used instead.

[Sascha Janz]

yes, the reason is the change to the Elytron subsystem. 

but how to make it work with the Elytron subsystem? 

will the quickstart be updated to work on WildFly 26.0.1

[cf...@redhat.com]

Please see https://docs.wildfly.org/26/WildFly_Elytron_Security.html#Using_the_Elytron_Subsystem

[Diana Krepinska]

Yes the quickstarts will be migrated to work on Wildfly 26, here is the jira issue that tracks it : https://issues.redhat.com/browse/WFLY-16195 

[Sascha Janz]

thanks for replies. 

fortunately i solved my problem which i hoped to get help from quickstart example.

the problem was how to configure server identity and secret from wildfly 13 in wildfly 26 with elytron to use remoting between wildfly servers.

the remoting subsystem i configured 

<subsystem xmlns="urn:jboss:domain:remoting:4.0">
            <http-connector name="http-remoting-connector" connector-ref="https2" sasl-authentication-factory="application-sasl-authentication"/>
            <outbound-connections>
                <remote-outbound-connection name="storage-manager-connection" outbound-socket-binding-ref="storage-manager" authentication-context="remote_authentication">
                    <properties>
                        <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
                        <property name="SSL_ENABLED" value="true"/>
                    </properties>
                </remote-outbound-connection>
            </outbound-connections>
        </subsystem>

the elytron authentication context i configured

            <authentication-client>
                <authentication-configuration name="auth-conf" authentication-name="myuser" protocol="remote+https" realm="ApplicationRealm" forwarding-mode="authentication" sasl-mechanism-selector="DIGEST-MD5">
                    <credential-reference store="credential" alias="74h1xni74v"/>
                </authentication-configuration>
                <authentication-context name="remote_authentication">
                    <match-rule match-host="SERVER16" authentication-configuration="auth-conf"/>
                </authentication-context>
            </authentication-client>

            <credential-stores>
                <credential-store name="credential" relative-to="jboss.server.config.dir" location="mycredstore.cs" create="true">
                    <credential-reference clear-text="mypassword"/>
                </credential-store>
            </credential-stores>

and finally the socket binding 

        <outbound-socket-binding name="storage-manager">
            <remote-destination host="SERVER16" port="40100"/>
        </outbound-socket-binding>

may be this helps someone