Details
-
Bug
-
Resolution: Done
-
Major
-
11.0.0.Alpha1
-
None
Description
When setting up AUTH protocol and starting two servers, they fail to establish a view, because they never authenticate to each other:
Server 1:
12:21:59,348 WARN [org.jgroups.protocols.AUTH] (thread-2) rjanik: failed to validate AuthHeader (token: SimpleToken) from node2; dropping message
Server 2:
12:23:17,370 WARN [org.jgroups.protocols.AUTH] (thread-1) node2: failed to validate AuthHeader (token: SimpleToken) from node2; dropping message 12:23:17,371 WARN [org.jgroups.protocols.AUTH] (thread-1) node2: failed to validate AuthHeader (token: SimpleToken) from node2; dropping message 12:23:17,372 WARN [org.jgroups.protocols.AUTH] (thread-2) node2: failed to validate AuthHeader (token: SimpleToken) from rjanik; dropping message 12:23:22,370 WARN [org.jgroups.protocols.pbcast.GMS] (MergeTask,ee,node2) node2: merge is cancelled: did not get any merge responses from partition coordinators
AUTH does not set up the auth_value field for the SimpleToken and MD5Token when creating them and it looks like setAuthToken is not called later. Those tokens then fail when authenticating, referencing the auth_value field.
AUTH:
public void setAuthClass(String class_name) throws Exception { Object obj=Class.forName(class_name).newInstance(); auth_token=(AuthToken)obj; auth_token.setAuth(this); }
MD5Token:
return (this.auth_value != null) && (serverToken.auth_value != null) && (this.auth_value.equalsIgnoreCase(serverToken.auth_value));
Attachments
Issue Links
- clones
-
JBEAP-10285 AUTH fails to validate AuthHeader
- Verified