[
https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin....
]
Robert Cernak commented on JGRP-2227:
-------------------------------------
Sorry, my fault. I sent you original version of AbstractInfinityAuthToken class which I
was using before. For testing reasons I changed it now to following:
{code:java}
public boolean authenticate(final AuthToken token, final Message arg1) {
return false;
}
{code}
With this version of authenticate method I did not receive exception you are showing. I
did not catch any exception at all. I observed, that jgroups communication channels are
being started when I start infinispan cache, so my catch block was following:
{code:java}
Cache<Object, Object> cache;
try{
cache = cacheManager.getCache(cacheName);
} catch (Exception e) {
System.out.println("Here should I catch SecurityException");
}
//cacheManager is org.infinispan.manager.DefaultCacheManager
{code}
After executing this line in try block, I see that authenticate method is being called
with only line "return false". But no exception is thrown and I get fully
functional instance of cache.
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.12
Attachments: jgroupsDoesNotThrowSecurityExceptionWithJgroups4012.zip,
jgroupsLogs.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)