Skip to content

Conversation

chrjohn
Copy link
Member

@chrjohn chrjohn commented May 2, 2020

Adds possibility to specify tags via setting LogonTag or LogonTag<n>.
Example:

LogonTag=553=user
LogonTag1=554=password 

It is checked whether a data dictionary is present to determine whether the specified tag is a header field. Otherwise it is put into the body of the message.

@chrjohn chrjohn added the please review asking for a review label May 2, 2020
@chrjohn
Copy link
Member Author

chrjohn commented May 2, 2020

LGTM JavaScript analysis failing. This is somewhat expected and triggered by changing the configuration html page. See #277 (comment)

Copy link
Contributor

@the-thing the-thing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Useful.

I know one or two venues requiring this. So far everybody has probably been intercepting Logon message in quickfix.Application#toAdmin and setting these fields manually (user + password).

I think somebody could "override" existing fields, but since this is optional functionality, they must ensure they know what they are doing anyway.

@chrjohn
Copy link
Member Author

chrjohn commented May 13, 2020

@the-thing , thanks for the review.
You are right, I feel like one of the most asked questions is "how do I set username and password on the Logon message". ;)

@chrjohn chrjohn removed the please review asking for a review label May 13, 2020
@chrjohn chrjohn added this to the QFJ 2.2.0 milestone May 13, 2020
@chrjohn chrjohn merged commit c73c4c7 into master May 13, 2020
@chrjohn chrjohn deleted the custom-logon-tags branch May 13, 2020 21:56
@the-thing
Copy link
Contributor

the-thing commented May 14, 2020

@chrjohn

BTW. I think you can close QFJ-177.

jli8000 pushed a commit to jli8000/quickfixj that referenced this pull request Sep 22, 2020
Adds possibility to specify tags via setting `LogonTag` or `LogonTag<n>`.

Example:
```
LogonTag=553=user
LogonTag1=554=password 
```

It is checked whether a data dictionary is present to determine whether the specified tag is a header field. Otherwise it is put into the body of the message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants