Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFLY-13828] remote+tls is not supported by EJBClient and remote-outb… #388

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tadamski
Copy link
Contributor

@tadamski tadamski commented May 3, 2021

Copy link
Contributor

@darranl darranl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is still evolving so just added some minor comments.

[source]
----
<subsystem xmlns="urn:jboss:domain:remoting:4.1">
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this RFE is more about being able to specify the protocol but as this is a TLS configuration I think it would be good to also have an example referencing Elytron capabilities as the legacy security realm will be deleted at some point in the upcoming WildFly releases.

:idseparator: -

=== Issue
* https://issues.redhat.com/browse/WFLY-13828
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment the analysis is only mentioning changes which would need to be applied to the Remoting subystem which lived in WildFly Core so we probably need a WFCORE as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants