Hello,
I think the Developer Guide may need some updates regarding the configuration for the remote EJB functionality between 2 server instances which currently describe only the "old" approach with the security subsystem. Username and security realm are used there and if I follow this approach, server complains that these are deprecated:
WFLYCTL0028: Attribute 'username' in the resource at address '/profile=xyz/subsystem=remoting/remote-outbound-connection=xyz-remote-ejb-connection-1' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=xyz/subsystem=remoting/remote-outbound-connection=xyz-remote-ejb-connection-1' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
I mean chapter EJB invocations from a remote server instance:
https://docs.wildfly.org/16/Developer_Guide.html#EJB_invocations_from_a_remote_server_instance
In particular:
Create a security realm on the client server
https://docs.wildfly.org/16/Developer_Guide.html#create-a-security-realm-on-the-client-server
Create a "remote-outbound-connection" which uses this newly created:
https://docs.wildfly.org/16/Developer_Guide.html#create-a-remote-outbound-connection-which-uses-this-newly-created-outbo…
And perhaps Contents on jboss-ejb-client.xml
https://docs.wildfly.org/16/Developer_Guide.html#contents-on-jboss-ejb-client.xml
{by the way, I can't find there an example for the case of cluster like here for example: Chapter 8. Clustered Enterprise JavaBeans - Red Hat Customer Portal }
Could you please provide the complete description of how this should be configured making use of the "new" elytron subsystem?
