Message Logon Scenario base

SYNOPSIS: The logon message authenticates a user establishing a connection to a remote system. The logon message must be the first message sent by the application requesting to initiate a FIX session. The HeartBtInt (108) field is used to declare the timeout interval for generating heartbeats (same value used by both sides). The HeartBtInt value should be agreed upon by the two firms and specified by the Logon initiator and echoed back by the Logon acceptor. Upon receipt of a Logon message, the session acceptor will authenticate the party requesting connection and issue a Logon message as acknowledgment that the connection request has been accepted. The acknowledgment Logon can also be used by the initiator to validate that the connection was established with the correct party. The session acceptor must be prepared to immediately begin processing messages after receipt of the Logon. The session initiator can choose to begin transmission of FIX messages before receipt of the confirmation Logon, however it is recommended that normal message delivery wait until after the return Logon is received to accommodate encryption key negotiation. The confirmation Logon can be used for encryption key negotiation. If a session key is deemed to be weak, a stronger session key can be suggested by returning a Logon message with a new key. This is only valid for encryption protocols that allow for key negotiation. (See the FIX Web Site's Application notes for more information on a method for encryption and key passing.) The Logon message can be used to specify the MaxMessageSize supported (e.g. can be used to control fragmentation rules for very large messages which support fragmentation). It can also be used to specify the MsgTypes supported for both sending and receiving.

ID	MsgType	Abbr	Flow
11	A	Logon

Pedigree

Added	EP	Updated	EP	Deprecated	EP
FIX.2.7

Responses

None

Members

Logon base members

ID	Name	Abbr	Presence	Description
1024	StandardHeader	Hdr	required	SYNOPSIS: The standard FIX message header ELABORATION:
98	EncryptMethod	EncryptMethod	required	SYNOPSIS: Method of encryption
108	HeartBtInt	HeartBtInt	required	SYNOPSIS: Heartbeat interval (seconds)
95	RawDataLength	RawDataLength	optional	SYNOPSIS: Number of bytes in raw data field.
96	RawData	RawData	optional	SYNOPSIS: Unformatted raw data, can include bitmaps, word processor documents, etc.
141	ResetSeqNumFlag	ResetSeqNumFlag	optional	SYNOPSIS: Indicates that the both sides of the FIX session should reset sequence numbers.
789	NextExpectedMsgSeqNum	NextExpectedMsgSeqNum	optional	SYNOPSIS: Next expected MsgSeqNum value to be received.
383	MaxMessageSize	MaxMsgSz	optional	SYNOPSIS: Maximum number of bytes supported for a single message.
2098	MsgTypeGrp	MsgTypeGrp	optional	Specifies the number of repeating RefMsgTypes specified
464	TestMessageIndicator	TestMsgInd	optional	SYNOPSIS: Indicates whether or not this FIX Session is a "test" vs. "production" connection. Useful for preventing "accidents".
553	Username	Username	optional	SYNOPSIS: Userid or username.
554	Password	Password	optional	SYNOPSIS: Password or passphrase.
1025	StandardTrailer	Trlr	required	SYNOPSIS: The standard FIX message trailer ELABORATION: