[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/f1f9fc05 - PLEASE DO NOT REPLY BY MAIL.]
> Hi Bernt, > > the standard use case is described in the field comment "Specifies a new > password for the FIX Logon. The new password is used for subsequent > logons.", i.e. you want to change your current session password and have > to provide old and new password in a single message. > > I assume there is more to your question. The field is of no use for > marketplaces that do not allow the users to set their own passwords. > > Regards, Hanno. > > > Hi, > > > > What is the expected usage of the NewPassword (925) tag in the Logon > > message? Can anyone explain a use case? > > > > Best Regards, Bernt 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 [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.
