====== TraderLogonResponse ======

Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User.

The FIX API responds to Trader Logons with the Trader Logon Response message. With this message, the FIX API client can determine the success or failure of the Trader Logon attempt by the Master User.

===== Relevant Tags =====

The Trader Logon Response indicates the success or failure of the Trader Logon attempt in the Text tag (Tag 58). The Trader/User (whose attempt would apply to) is indicated in the UserName tag (Tag 553).

^ Tag Name ^ Tag Number ^ Description ^
| UserName | 553 | T4 User |
| Text | 58 | Description of Trader Logon attempt |

A successful authentication of a Trader Logon is acknowledged with a Trader Logon Response that contains a Success description in the Text tag (Tag 58). Failure to provide the correct parameters in the Trader Logon message will result in a Trader Logon Response failure.

A failed Trader Logon Response does not result in a physical disconnection. The FIX Session continues with the participation of the Master User and other traders that were previously authenticated and remained logged in.

===== Trader/User Configuration =====

For a successful Trader Logon, the T4 FIX API requires the Trader/User to have previously assigned accounts and exchanges. Before FIX API usage, the Trader/User is required to complete Market Data Requirements through its firm setup page. Lack of proper configuration will result in a failed Trader Logon Response — indicating the lack of account or exchange assignment for the violating User.

This requirement is not applied for Chart data logins (Tag 372=V).

===== Message Dictionary =====

^ Tag ^ Field Name ^ Req'd ^ Comments ^
| Standard Header | | Y | MsgType = UCI |
| 49 | SenderCompID | Y | T4 Application Name (inbound), T4 Firm Name (outbound) |
| 56 | TargetCompID | Y | T4 Firm Name (inbound), T4 Application Name (outbound) |
| 553 | UserName | Y | T4 User |
| 58 | Text | Y | Description of Trader Logon Result |
| Standard Trailer| | Y | |

===== Sample =====

In this example, the T4 FIX API client requests the start of a FIX Session with Multi-Trader mode enabled (Tag 372=UCG). The Trader Logon attempt initially fails due to an incorrect password, and later succeeds with the correct one.

==== Login Request from T4 FIX API Client ====
<code>
[FIXLOGIN]
34=1|49=T4Test|56=test|50=MasterUser|52=20150612-15:34:35.865|91=64768859-3ACF-4224-A4E9-DA66901AFC63|90=36|98=None|108=25|553=MasterUser|554=good_password|384=3|372=BB|372=d|372=UCG|
</code>

==== Successful Login Response from T4 FIX API ====
<code>
[FIXLOGIN]
34=1|49=test|56=T4Test|50=T4FIX|52=20150612-15:34:35.993|98=0|108=30|553=MasterUser|554=***|1408=4.3.34.5|
</code>

==== Trader Logon Request - Bad Password ====
<code>
[FIXTRADERLOGIN]
34=2|49=T4Test|56=test|52=20150612-15:34:50.182|91=64768859-3ACF-4224-A4E9-DA66901AFC63|90=36|553=Trader1|554=bad_password|
</code>

==== Failed Trader Logon Response ====
<code>
[FIXTRADERLOGINRESPONSE]
34=2|49=test|56=T4Test|50=T4FIX|52=20150612-15:34:50.261|553=Trader1|58=Login failed: most likely incorrect trader and password combination|
</code>

==== Trader Logon Request - Good Password ====
<code>
[FIXTRADERLOGIN]
34=3|49=T4Test|56=test|52=20150612-15:35:03.186|91=64768859-3ACF-4224-A4E9-DA66901AFC63|90=36|553=Trader1|554=good_password|
</code>

==== Successful Trader Logon Response ====
<code>
[FIXTRADERLOGINRESPONSE]
34=3|49=test|56=T4Test|50=T4FIX|52=20150612-15:35:03.725|553=Trader1|58=Success|
</code>

==== Logout Request from Client ====
<code>
[FIXLOGOUT]
34=4|49=T4Test|56=test|52=20150612-15:35:09.786|
</code>

==== Successful Logout Response ====
<code>
[FIXLOGOUT]
34=4|49=test|56=T4Test|52=20150612-15:35:09.787|58=Successful logout upon request|
</code>