Hi,
We developed an application that’s running as FIX Acceptor.
The FIX Acceptor received a Logout with an unexpected TAG 554-Password, which it managed as a normal logout (ignoring the TAG 554).
This behavior is probably incorrect.
What is the correct behavior:
- refuse the Logout with an Admin Reject (keeping the session active)
- disconnect the Initiator without sending back the Logout Response
Is it a good practice to refuse a logout?
Thanks & regards
Pierangelo
It is good practice to be as FIX compliant as possible whilst tolerating non-compliant behaviour from your counterparties to avoid operational issues but logging such behaviour, adding a remark to Text(58) in your Logout(35=5) message and raising it as an issue afterwards. Password(554) is not part of the Logout(35=5) message and should not be sent in this message type.
The response for other message types would be to send a Reject(35=3) with SessionRejectReason(373)=2 (Tag not defined for this message type).
Hi, Hanno,
thanks for the quick and clear reply.
Pierangelo
1 Like