Message-ID: <466148719.16967.1711613984567.JavaMail.root@ovh3sttqfj1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16966_112630563.1711613984567" ------=_Part_16966_112630563.1711613984567 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Custom Logon Configuration in Config File

Custom Logon Configuration in Config File

Rather than requiring custom Java code to accomplish the common = use case of passing userID/passwords in SenderSubID and RawData fields in t= he Logon message (as is described in Implementing Custom Logons), it would be much cleane= r to allow these fields to be specified in the configuration file.  Fo= r example, config options such as LogonSenderSubID and LogonRawData could b= e used:

=20

LogonSenderSubID=3DMyUserId
LogonRawData=3DMyPassword

=20

(... and then the RawDataLength field would be calculated automatically)= .

=20

This would make it possible to use Quickfix via the Apache Synapse / the= WSO2 ESB (Enterprise Service Bus).  As it stands, it is impossible to= use Quickfix and Synapse/WSO2ESB with counterparties that require custom l= ogons because the logon process happens before it is possible to mediate (c= hange) the contents of the messages that QuickFIX is emitting.  There = is no way on those platforms (except possibly writing some complex wrapper = code around Quickfix, or modifying the Quickfix source and rebuilding the j= ar) to interface with Quickfix's callbacks and allow custom logons.  S= o, it is absolutely essential that these custom options can be specified in= the configuration file rather than via java callbacks.

------=_Part_16966_112630563.1711613984567--