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

WSDL url http auth #92

Closed
MpEliaz opened this issue May 24, 2018 · 6 comments
Closed

WSDL url http auth #92

MpEliaz opened this issue May 24, 2018 · 6 comments
Labels

Comments

@MpEliaz
Copy link

MpEliaz commented May 24, 2018

Hi guys, I have a problem getting the WSDL because the endpoint has to http basic auth. and i don't have idea where put the credentials for to generate the api. (in the model or datasource json file)

(sorry my english).

@gizmo84
Copy link

gizmo84 commented May 29, 2018

Hi @MpEliaz . From the doc at https://loopback.io/doc/en/lb3/SOAP-connector.html#security-property you have to set the security object in datasources.json.

@ilijaz
Copy link
Contributor

ilijaz commented Mar 28, 2019

I've spent 2 hours reading docs and debugging.
You should use "wsdl_headers" option in datasource config for sending custom http headers

    "wsdl_headers": {
      "Authorization": "Basic UGVyc29uYWwgYWNjb3VudDpORVdsazIwMTVAKSEl"
    },

By the way, security option object is used only for methods not for wsdl requests.

@Realetive
Copy link
Contributor

Add information about it to README.md — #107

@ilijaz
Copy link
Contributor

ilijaz commented Apr 2, 2019

@Realetive I'm not sure about #107. BasicAuth security scheme is supported. If your soap source has http basic auth you should use both wsdl_headers and security scheme options in the datasource config.

@stale
Copy link

stale bot commented Sep 17, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 17, 2019
@stale
Copy link

stale bot commented Oct 1, 2019

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants