PC SOFT

FOROS PROFESIONALES
WINDEVWEBDEV y WINDEV Mobile

Inicio → WINDEV 2024 → WD19 - webservice and https
WD19 - webservice and https
Iniciado por guest, 09,nov. 2015 16:47 - 5 respuestas
Publicado el 09,noviembre 2015 - 16:47
Hi everyone,

I need to communicate with a webservice over https. In this case both sides need a certificate. We already changed and installed the necessary certificates. At least i think so.

When I use a webbrowser all seems to work.

I did an import of the wsdl and put in the right address for the endpoint.

But when I try to use a webservice call from my WD-application, I get an error saying "Security Alert: the security certificate assigned to this site has not been released by a recognized or trusted company"

How can I get this to work?
Publicado el 09,noviembre 2015 - 17:15
Hi,

I think that there are several aproaches depending on the windev version, but you can try the following instructions before calling the Web Service:

HTTP.IgnoreError = HTTPErrorInvalidCertificate
HTTP.IgnoreError = HTTPErrorInvalidCertificateName

I hope it works.

Bruno
Publicado el 09,noviembre 2015 - 18:19
you can try to ignore the errors of the certificate in the Properties associated with the Webservice.

check IgnoreError in this help page:
http://doc.windev.com/en-US/…
Publicado el 09,noviembre 2015 - 19:41
Paulo,
I tried that with no luck before, but you put me in the right direction.
I read the help again (which I should have in the first place) and came across some other hints.
Like htis one

Quote
If the server that is hosting the Webservice requires a Windows authentication in HTTP, HTTPParameter must be called before consuming the Webservice (in order for Internet Explorer to be used for the HTTP requests).



Maybe it is also a combination of settings, I can't tell exactly. At least it works now.
Thanks!
Publicado el 09,noviembre 2015 - 19:57
Arie

Maybe a stupid question but do you import using , http of https??

Jan
Publicado el 09,noviembre 2015 - 20:21
Hi Jan,

the import was also through httpS.
But I did also try with a local copy of the wsdl file.
I don't think it has something to do with that, because afaik I put in all login-credentials, endpoint, etc at runtime.