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

ISPN-12617 Transport Security #9511

Merged

Conversation

tristantarrant
Copy link
Member

@tristantarrant tristantarrant commented Sep 8, 2021

@@ -667,6 +677,11 @@ private void buildChannel() {
throw CLUSTER.errorCreatingChannelFromConfigFile(DEFAULT_JGROUPS_CONFIGURATION_FILE, e);
}
}

if (props.containsKey(SOCKET_FACTORY)) {
Copy link
Member

Choose a reason for hiding this comment

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

I believe this is overwriting the SocketFactory set in line 620.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed. I really would like to avoid the silly Transport abstraction we have and use a proper configuration object to pass things to the JGroupsTransport

core/src/main/resources/schema/infinispan-config-13.0.xsd Outdated Show resolved Hide resolved
@@ -1596,4 +1596,13 @@
<xs:complexType name="security-realm-trust">
<xs:attribute type="xs:string" name="name"/>
</xs:complexType>

<xs:attribute name="security-realm" type="xs:string">
Copy link
Member

Choose a reason for hiding this comment

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

I believe this is not supposed to be here, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes it is. The security-realm is in the server namespace but it applies to the transport which is declared in the infinispan-config schema (look for <xs:anyAttribute/>)

@tristantarrant tristantarrant force-pushed the ISPN-12617/transport_security branch 3 times, most recently from ea69393 to c879e14 Compare September 18, 2021 14:01
@tristantarrant
Copy link
Member Author

@pruivo updated with the JGroups 4.2.17.Final release

throw ParseUtils.unexpectedAttribute(reader, attributeName);
}
} else {
throw ParseUtils.unexpectedAttribute(reader, attributeIndex);
Copy link
Member

Choose a reason for hiding this comment

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

should be element and not attribute.

Suggested change
throw ParseUtils.unexpectedAttribute(reader, attributeIndex);
throw ParseUtils.unexpectedElement(reader, org.infinispan.configuration.parsing.Element.forName(elementName));

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

</xs:attribute>
<xs:attribute name="cluster" type="xs:string">
<xs:annotation>
<xs:documentation>Defines the name for the underlying group communication cluster. If unspecified, the default-cluster name will be used.</xs:documentation>
Copy link
Member

Choose a reason for hiding this comment

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

if not specified, remote-sites.cluster will be used.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

@pruivo pruivo merged commit 8552588 into infinispan:main Sep 20, 2021
@pruivo
Copy link
Member

pruivo commented Sep 20, 2021

integrated! thanks @tristantarrant !

@tristantarrant tristantarrant deleted the ISPN-12617/transport_security branch July 5, 2022 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants