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

No means of accessing authenticated/secured services #2

Open
wonea opened this issue Feb 27, 2014 · 5 comments
Open

No means of accessing authenticated/secured services #2

wonea opened this issue Feb 27, 2014 · 5 comments

Comments

@wonea
Copy link

wonea commented Feb 27, 2014

I'm trying to access a secured SOAP service, however I cannot find anywhere to put username and password credentials.

@dylanmei
Copy link
Owner

Are we talking about basic-auth while trying to download the wsdl?

@wonea
Copy link
Author

wonea commented Feb 28, 2014

Yes, I get the following null reference exception:

2014_02_28_10_40_43_linqpad_4

I can confirm the WSDL does work, tested in SOAPUI 4.6.4

@john-mills-nz
Copy link

I have a WCF service secured with Windows authentication and I agree, there is no way to provide credentials.

@SmithPlatts
Copy link

Talk about issue revival, but I have just hit this with basic auth to a WSDL service; any chance the maintainers are interested?

@canichols2
Copy link

I am able to connect to our SOAP service, but each method is individually locked down to specific user groups or users. this requires authentication. Is there any way to set the user these services use, or is it ALWAYS going to be unauthenticated?

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

5 participants