included in 4D 2004 is an older (0.9.8 or thereabouts) version of OpenSSL,
so it is not capable of elevating to TLS 1.2 which is the default minimum for
v17.
https://blog.4d.com/more-security-for-your-4d-server/
of course you could lower the security level but that's probably the wrong way
to
Keisuke and Lutz,
Thank you again for your comments. I have now worked out what is not working...
I was dumb enough to think that all SOAP clients would be equal. In fact when
I tried from SOAPUI the HTTTPS call worked fine. When I tried from 4D v17 the
HTTPS call also worked fine.
My
Sorry, I was bit too fast with my answer. Especially about the configuration of
the web service on the side of 4D. This was my from remembering of using a 4D
web service for testing purposes in the past. At this time we built this test
service as a mockup of another external web service, that
Keisuke and Lutz,
Thank you for your comments.
Lutz said:
"is not only necessary to access the endpoint with https:// you have to offer
the service as a https:// service, e.g. you have to adjust the settings in 4D
to modify the wsdl in the proper way."
This sounds like the key, so I will look
: Freitag, 26. Oktober 2018 11:19
An: 4d_tech@lists.4d.com
Cc: Douglas Cryer
Betreff: SOAP over HTTPS
Hi folks,
I need some advice on what I need to do to make 4D Web Services accept HTTPS
calls. I am using v17 64bit server.
In my naivety I assumed that it would just be a case of changing the URL
sounds like you have done everything right. does the URL include the port
number, or is the server published via port other than 443?
**
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options:
Hi folks,
I need some advice on what I need to do to make 4D Web Services accept HTTPS
calls. I am using v17 64bit server.
In my naivety I assumed that it would just be a case of changing the URL in the
SOAP calls to point at the https endpoint. But this does not work and returns
"SOAP
7 matches
Mail list logo
