Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certains characters (&, <, ?, etc) are not allowed for user information at SOAP sender #706

Closed
rbeckman-nextgen opened this issue May 11, 2020 · 2 comments
Milestone

Comments

@rbeckman-nextgen
Copy link
Collaborator

In the SOAP sender, some characters (ej: ?) can't be used int password (event if it's url-encoded) It works in the WSDL string, but not into the SOAP call .

Imported Issue. Original Details:
Jira Issue Key: MIRTH-698
Reporter: albertosaez
Created: 2008-01-08T10:47:19.000-0800

@rbeckman-nextgen rbeckman-nextgen added this to the 1.7.0 milestone May 11, 2020
@rbeckman-nextgen
Copy link
Collaborator Author

With this patch, you can add special chars to the userInfo field (this should be addes url-encoded, but at least it works).

Example, to use 'w?at' as password (%3F is '?'):

http://domain%5Clogin:w%3fat@server/dir/wsname.asmx

This works in the same way for WSDL uri and for Service Endpoint URI

Imported Comment. Original Details:
Author: albertosaez
Created: 2008-01-08T10:50:54.000-0800

@rbeckman-nextgen
Copy link
Collaborator Author

Thanks for the patch Alberto!

Imported Comment. Original Details:
Author: chrisl
Created: 2008-01-10T16:25:44.000-0800

pladesma pushed a commit that referenced this issue Jul 4, 2023
…ommendations

Merge in MC/connect from bugfix/ROCKSOLID-10865-switch-xstream-to-use-whitelist-for-api-serialization to development

* commit 'e0d2eac8db982cc5e5bc9fc9f0dc1d93816cb6ab':
  Now including Java 9+ JVM options by default.
  Fixing unit test.
  Adding XStream recommendations to denylist.
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

No branches or pull requests

1 participant