Class AUTH
- All Implemented Interfaces:
Lifecycle
GMS in the configuration.Note that some of the AuthTokens (such as MD5Token, SimpleToken etc) cannot prevent rogue members from joining a cluster, and are thus deprecated. Read the manual for a detailed description of why.
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected AuthTokenUsed on the coordinator to authentication joining member requests againstprotected booleanprotected static final shortFields inherited from class org.jgroups.stack.Protocol
after_creation_hook, down_prot, ergonomics, id, local_addr, log, policies, stack, stats, up_prot -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoiddestroy()This method is called on aJChannel.close().A message is sent down the stack.protected static GMS.GmsHeadergetGMSHeader(Message msg) protected static JoinRspgetJoinResponse(Message msg) protected booleanhandleAuthHeader(GMS.GmsHeader gms_hdr, AuthHeader auth_hdr, Message msg) Handles a GMS headervoidinit()Called after a protocol has been created and before the protocol is started.protected booleanneedsAuthentication(Message msg, GMS.GmsHeader hdr) protected voidsendJoinRejectionMessage(Address dest, String error_msg) protected voidprotected voidsendRejectionMessage(byte type, Address dest, String error_msg) voidsetAuthClass(String class_name) setAuthCoord(boolean authenticateCoord) setAuthToken(AuthToken token) voidstart()This method is called on aJChannel.connect(String); starts work.voidstop()Called on aJChannel.disconnect(); stops work (e.g.An event was received from the layer below.voidup(MessageBatch batch) Sends up a multiple messages in aMessageBatch.Methods inherited from class org.jgroups.stack.Protocol
accept, addPolicy, addr, addr, afterCreationHook, down, down, enableStats, getAddress, getComponents, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getPolicies, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, isErgonomics, level, parse, policies, providedDownServices, providedUpServices, removePolicy, requiredDownServices, requiredUpServices, resetStatistics, resetStats, setAddress, setDownProtocol, setErgonomics, setId, setLevel, setPolicies, setProtocolStack, setSocketFactory, setUpProtocol, setValue, statsEnabled, toString, up
-
Field Details
-
GMS_ID
protected static final short GMS_ID -
auth_token
Used on the coordinator to authentication joining member requests against -
authenticate_coord
protected volatile boolean authenticate_coord
-
-
Constructor Details
-
AUTH
public AUTH()
-
-
Method Details
-
setAuthCoord
-
setAuthClass
- Throws:
Exception
-
getAuthClass
-
getAuthToken
-
setAuthToken
-
getPhysicalAddress
-
init
Description copied from class:ProtocolCalled after a protocol has been created and before the protocol is started. Attributes are already set. Other protocols are not yet connected and events cannot yet be sent. -
start
Description copied from class:ProtocolThis method is called on aJChannel.connect(String); starts work. Protocols are connected ready to receive events. Will be called from bottom to top. -
stop
public void stop()Description copied from class:ProtocolCalled on aJChannel.disconnect(); stops work (e.g. by closing multicast socket). Will be called from top to bottom. -
destroy
public void destroy()Description copied from class:ProtocolThis method is called on aJChannel.close(). Does some cleanup; after the call, the VM will terminate -
up
An event was received from the layer below. Usually the current layer will want to examine the event type and - depending on its type - perform some computation (e.g. removing headers from a MSG event type, or updating the internal membership list when receiving a VIEW_CHANGE event). Finally the event is either a) discarded, or b) an event is sent down the stack usingdown_prot.down()or c) the event (or another event) is sent up the stack usingup_prot.up(). -
up
Description copied from class:ProtocolSends up a multiple messages in aMessageBatch. The sender of the batch is always the same, and so is the destination (null == multicast messages). Messages in a batch can be OOB messages, regular messages, or mixed messages, although the transport itself will create initial MessageBatches that contain only either OOB or regular messages.The default processing below sends messages up the stack individually, based on a matching criteria (calling
Protocol.accept(Message)), and - if true - callsProtocol.up(org.jgroups.Event)for that message and removes the message. If the batch is not empty, it is passed up, or else it is dropped.Subclasses should check if there are any messages destined for them (e.g. using
MessageBatch.iterator(Predicate)), then possibly remove and process them and finally pass the batch up to the next protocol. Protocols can also modify messages in place, e.g. ENCRYPT could decrypt all encrypted messages in the batch, not remove them, and pass the batch up when done. -
down
Description copied from class:ProtocolA message is sent down the stack. Protocols may examine the message and do something (e.g. add a header) with it, before passing it down. -
needsAuthentication
-
handleAuthHeader
Handles a GMS header- Returns:
- true if the message should be processed (= passed up), or else false
-
sendRejectionMessage
-
sendJoinRejectionMessage
-
sendMergeRejectionMessage
-
getGMSHeader
-
getJoinResponse
-