Imported from previous forum
I’d like to suggest new msg types for handling trader logins to an exchange. I see several different useful msgs:
- Login Req Msg
- Login Resp Msg
- Logoff Req Msg
- Logoff Resp Msg
- Change Pwd Req Msg
- Change Pwd Resp Msg
Since data required for logins and password changes varies for different exchanges so would the required fields. Some that would probably be consistent might include member-ID, trader-ID, password, new password, login status, etc. Please let me know your thoughts on this. Thx
To clarify a bit…We have a need for sending application level trader login msgs internally via FIX. Some exchanges (eg LSE, XETRA, LIFFE) require individual traders or the member firm to log in before they can submit any orders. Although they each have their own API for sending/receiving msgs, we use FIX to communicate internally before sending these requests off the the exchange. To support sending login, logoff, and change password msgs internally via FIX, we will be implementing some new msg types (probably tags too) that will look something like the following:
Login/Logoff Req Msg
Req Type (int 1-LoginReq, 2-LogoffReq)
User ID (string)
Password (string)
Exchange (tag 100)
Login/Logoff Resp Msg
Resp Type (int 1-LoginResp, 2-LogoffResp)
User ID (string)
Exchange (tag 100)
Resp Sub Type (int For LSE: 1-interactive,
2-secure)
Login Status (int 1-loggedin, 2-loggedoff)
Text (tag 58, for any error msgs)
Change Pwd Msg
User ID (string)
Password (string)
New Password (string)
Exchange (tag 100)
Change Pwd Resp
User ID (string)
Exchange (tag 100)
Status (int 1-success, 2-failed)
Text (tag 58)
We have not yet finalized the exact layout of these msgs, so any feedback would be appreciated.
> I’d like to suggest new msg types for handling trader logins to an exchange. I see several different useful msgs:
> 1. Login Req Msg
> 2. Login Resp Msg
> 3. Logoff Req Msg
> 4. Logoff Resp Msg
> 5. Change Pwd Req Msg
> 6. Change Pwd Resp Msg
>
> Since data required for logins and password changes varies for different exchanges so would the required fields. Some that would probably be consistent might include member-ID, trader-ID, password, new password, login status, etc. Please let me know your thoughts on this. Thx
>
>
>
[ original email was from Kevin Houstoun - kevin.houstoun@ssmb.com ]
This has been assigned ID [PC20030417_8] and will be discussed by the global technical committee.
> To clarify a bit…We have a need for sending application level trader login msgs internally via FIX. Some exchanges (eg LSE, XETRA, LIFFE) require individual traders or the member firm to log in before they can submit any orders. Although they each have their own API for sending/receiving msgs, we use FIX to communicate internally before sending these requests off the the exchange. To support sending login, logoff, and change password msgs internally via FIX, we will be implementing some new msg types (probably tags too) that will look something like the following:
>
> Login/Logoff Req Msg
> Req Type (int 1-LoginReq, 2-LogoffReq)
> User ID (string)
> Password (string)
> Exchange (tag 100)
>
> Login/Logoff Resp Msg
> Resp Type (int 1-LoginResp, 2-LogoffResp)
> User ID (string)
> Exchange (tag 100)
> Resp Sub Type (int For LSE: 1-interactive,
> 2-secure)
> Login Status (int 1-loggedin, 2-loggedoff)
> Text (tag 58, for any error msgs)
>
> Change Pwd Msg
> User ID (string)
> Password (string)
> New Password (string)
> Exchange (tag 100)
>
> Change Pwd Resp
> User ID (string)
> Exchange (tag 100)
> Status (int 1-success, 2-failed)
> Text (tag 58)
>
> We have not yet finalized the exact layout of these msgs, so any feedback would be appreciated.
>
>
> > I’d like to suggest new msg types for handling trader logins to an exchange. I see several different useful msgs:
> > 1. Login Req Msg
> > 2. Login Resp Msg
> > 3. Logoff Req Msg
> > 4. Logoff Resp Msg
> > 5. Change Pwd Req Msg
> > 6. Change Pwd Resp Msg
> >
> > Since data required for logins and password changes varies for different exchanges so would the required fields. Some that would probably be consistent might include member-ID, trader-ID, password, new password, login status, etc. Please let me know your thoughts on this. Thx
> >
> >
> >
>
[ original email was from Kevin Houstoun - kevin.houstoun@ssmb.com ]
With a little effort on the design this could also be used to report statii of counterparties on a hub and spoke network. This issues has already been identified and assigned an ID of PC20030323_4
The text of that PC follows
Order Routing Network Monitoring Tool Messages
A combination of Session Level Messages, Logon/Logoff and Status Request messages would serve the needs of potential clients to monitor their own and their counter parties FIX connections.
As the options suggest, clients would have the ability of being notified when their trading partners connect to the network during market open. Once a client successfully connects to the network (whether network out to client or client initiated into the network) a logon message would be sent to the firms trading partners. As each counter party becomes connected, the respective parties are notified. In these scenarios, the network host would be entirely responsible for routing these messages. In addition, the party who has just logged on could receive a list of all trading partners that he/she is configured with.
Logoff requests would operate in a similar fashion. At the end of a trading session, a logoff message is sent to the network. Based on the message received, a firm’s connected trading partners are informed that Broker/Insitution X is no longer connected to the network.
The status request message allows a client to request an update on an ad-hoc basis. Ideally, the client could request to see all counter parties or a specific trading partner. By utilizing this option, it minimizes the total number of messages being sent over a network.
The monitoring requests would be ideally used for Order Routing related messages.
=============================================
> To clarify a bit…We have a need for sending application level trader login msgs internally via FIX. Some exchanges (eg LSE, XETRA, LIFFE) require individual traders or the member firm to log in before they can submit any orders. Although they each have their own API for sending/receiving msgs, we use FIX to communicate internally before sending these requests off the the exchange. To support sending login, logoff, and change password msgs internally via FIX, we will be implementing some new msg types (probably tags too) that will look something like the following:
>
> Login/Logoff Req Msg
> Req Type (int 1-LoginReq, 2-LogoffReq)
> User ID (string)
> Password (string)
> Exchange (tag 100)
>
> Login/Logoff Resp Msg
> Resp Type (int 1-LoginResp, 2-LogoffResp)
> User ID (string)
> Exchange (tag 100)
> Resp Sub Type (int For LSE: 1-interactive,
> 2-secure)
> Login Status (int 1-loggedin, 2-loggedoff)
> Text (tag 58, for any error msgs)
>
> Change Pwd Msg
> User ID (string)
> Password (string)
> New Password (string)
> Exchange (tag 100)
>
> Change Pwd Resp
> User ID (string)
> Exchange (tag 100)
> Status (int 1-success, 2-failed)
> Text (tag 58)
>
> We have not yet finalized the exact layout of these msgs, so any feedback would be appreciated.
>
>
> > I’d like to suggest new msg types for handling trader logins to an exchange. I see several different useful msgs:
> > 1. Login Req Msg
> > 2. Login Resp Msg
> > 3. Logoff Req Msg
> > 4. Logoff Resp Msg
> > 5. Change Pwd Req Msg
> > 6. Change Pwd Resp Msg
> >
> > Since data required for logins and password changes varies for different exchanges so would the required fields. Some that would probably be consistent might include member-ID, trader-ID, password, new password, login status, etc. Please let me know your thoughts on this. Thx
> >
> >
> >
>