Logon ID and password in Logon message

, ,
1

Imported from previous forum

2

Hi All!

If possible, please inform where will be the User name and Password fields be written in the Logon message? An obvious answer seems to be the RawData field and its length in the RawDataLength field.

  1. So the User name and Password should be always encrypted or not?
  2. In what form will they reside in one field? As user name and password are two separate Strings? What separator will be there in between in order to distinguish between them?

Any help is highly appreciated.

Regards,
Murad.

3

[ original email was from Ian Orford - ian.orford@ubs.com ]
FIX is typically a B2B protocol, so it’s unusual to login at a user level. In my experience, authentication between buy and sell-sides is handled using PGP-DES-MD5 encryption or is handled outside the FIX layer (perhaps SSL encryption at the TCP layer). This is typically a key-based authentication rather than username/password.

However, I have seen username/password used as you suggested in the RawData fields when connecting to some exchanges.

If you decide to use the RawData field, the format you decide on is between you and your counterparty since it’s not defined in the standard.

Hope this helps.

> Hi All!
>
> If possible, please inform where will be the User name and Password fields be written in the Logon message? An obvious answer seems to be the RawData field and its length in the RawDataLength field.
> 1. So the User name and Password should be always encrypted or not?
> 2. In what form will they reside in one field? As user name and password are two separate Strings? What separator will be there in between in order to distinguish between them?
>
>
> Any help is highly appreciated.
>
> Regards,
> Murad.
>

4

[ original email was from Jeremy Sutton - jezza.sutton@patsystems.com ]
I believe RawData is a suitable mechanism for doing what you want - we use it in Patsystems. The format is a counterparty negotiation and we chose to separate username and password by a slash "/"

5

I believe RawData is a suitable mechanism for doing what you want - we
use it in Patsystems. The format is a counterparty negotiation and we
chose to separate username and password by a slash “/”

we are using this way of doing to connect to Fixtgw of you.
but the gateway responds: “Reject logon: failed to create broker session: Logon failed: (code 7): invalid login, username or password incorrect”

any suggestions why this happens.

why is the sendersubId means