FIX 5.0 SP1 User Request (35=BE)
Logs a user on or off, changes a user password, or requests a user status. It works at user level, separate from the session Logon.
- MsgType (tag 35)
- BE
- Name in FIX 5.0 SP1
- UserRequest
- Category
- Application
- Required body fields
- 3
Fields in FIX 5.0 SP1
Body fields in the order the FIX 5.0 SP1 definition lists them. A repeating group starts with its counter field (NoXxx), followed by the fields of each entry, indented. A field inside an optional component or group is required only when that component or group is present.
| Tag | Field | Required |
|---|---|---|
| 923 | UserRequestID | Required |
| 924 | UserRequestType | Required |
| 553 | Username | Required |
| 554 | Password | Optional |
| 925 | NewPassword | Optional |
| 1400 | EncryptedPasswordMethod | Optional |
| 1401 | EncryptedPasswordLen | Optional |
| 1402 | EncryptedPassword | Optional |
| 1403 | EncryptedNewPasswordLen | Optional |
| 1404 | EncryptedNewPassword | Optional |
| 95 | RawDataLength | Optional |
| 96 | RawData | Optional |
Every message also carries the FIX 5.0 SP1 standard header (BeginString, BodyLength, MsgType, SenderCompID, TargetCompID, MsgSeqNum, SendingTime and others) and ends with CheckSum (10).
Also in other versions
User Request across all FIX versions
Decode a User Request messageField and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.