[
https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2227:
--------------------------------
2 issues:
* You need to place AUTH *below* GMS, not *above*, or else it cannot check JOIN requests
and responses. In your jgroupsCommandChannel.xml, this is incorrect
* {{AUTH.auth_coord}} needs to be set to {{false}}, or else the JOIN-RSP with the
rejection is not sent up the stack
When I do this, everything works fine.
Use of AUTH does not result in a SecurityException, but instead nodes
create separate clusters with the same name
-----------------------------------------------------------------------------------------------------------------
Key: JGRP-2227
URL:
https://issues.jboss.org/browse/JGRP-2227
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.6
Reporter: Robert Cernak
Assignee: Bela Ban
Fix For: 4.0.13
Attachments: jgroupsDoesNotThrowSecurityExceptionWithJgroups4012.zip,
jgroupsLogs.zip, traceLogs.zip
I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message
msg) in my class and its body contained only one line: return false;
In this way authentication should be false and I should get SecurityException.
When I started joining of nodes together to form a cluster, instead of getting
SecurityException, nodes formed 2 different clusters with the same name.
I am sure method was evaluated, since I tried to run it also with breakpoint, which was
triggered during joining process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)