[This message was posted by Bernt Sanden of Cinnober Financial Technology <bernt.san...@cinnober.com> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/81bc6aef - PLEASE DO NOT REPLY BY MAIL.]
> > Hi Hanno, > > > > I was thinking about a case that popped up today. It was about a > > customer that wants to give FIX clients a temporary initial password > > and when the FIX client logs on the first time requesting the clients > > to submit a new password replacing the temporary one. How should the > > use case look like for this case? > > > > Regards, Bernt > > In this case, the marketplace needs to keep track whether the FIX client > has successfully changed the temporary password or not. The Rules of > Engagement would make NewPassword conditionally required for the first > logon (until successful) and reject any attempts on subsequent logons to > change the password again (or simply ignore the field NewPassword). The > Logon response should indicate whether the password has been changed. Thanks Hanno. Regards, Bernt [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-proto...@googlegroups.com. To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
