RE: Web Service Call in 4Dv15

[Timothy Penner via 4D_Tech]

> The test at Site B was successful and the only difference appears to be that 
> the soapURL for Site B is a non-secured HTTP connection.
> For the site that I am having issues with, the soapURL is a secured HTTPS 
> connection.
> In your opinion, would that have any effect on the success/failure of the Web 
> Service Call command?

Yes. If site B connects via HTTP (not HTTPS) then it is not using SSL/TLS at 
all.
So in that case, it wouldn’t matter what level of encryption the server 
supports; because you are not using it.

> How may I verify if the SOAP server we are connecting to support TLS versions 
> above TLS 1.0?

You can try SSL Labs:
https://www.ssllabs.com/ssltest/analyze.html

Then look under the Configuration/Protocols section of the report.

-Tim



**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Web Service Call in 4Dv15

[Ronnie Teo via 4D_Tech]

Hi Tim,

Thanks for your heads up. 

FWIW, I have also tested the Web Service Call command at any another site (call 
this SiteB) using the same version 4Dv15.5 running on Windows 2012r2.

The test at Site B was successful and the only difference appears to be that 
the soapURL for Site B is a non-secured HTTP connection.
For the site that I am having issues with, the soapURL is a secured HTTPS 
connection.

In your opinion, would that have any effect on the success/failure of the Web 
Service Call command?

> Is it possible that the SOAP Server you are connecting to is older, and does 
> not understand current TLS versions above TLS 1.0?
> v11 supported SSLv2/SSLv3 while v15 does not.

How may I verify if the SOAP server we are connecting to support TLS versions 
above TLS 1.0?

Regards,
Ronnie
Tarawerkz




> On 12 May 2018, at 1:32 am, Timothy Penner  wrote:
> 
> Is it possible that the SOAP Server you are connecting to is older, and does 
> not understand current TLS versions above TLS 1.0?
> 
> v11 supported SSLv2/SSLv3 while v15 does not.
> 
> Reminders,
> SSLv3 and SSLv2 is disabled at the network layer in 4D as of v13 & v14
> http://forums.4d.com/Post/EN/15389376/1/15389377#15389377
> http://forums.4d.com/Post/FR/15389373/1/15389374#15389374
> 
> I think that TLS 1.0 is disabled at the network layer in 4D as of v15 leaving 
> only TLS 1.1 and 1.2 as an option in v15, but I am have not found a public 
> reference for this yet.
> 
> TLS 1.2 is set as the minimum TLS version at the network layer in 4D as of 
> v16R5
> https://blog.4d.com/more-security-for-your-4d-server/
> http://kb.4d.com/assetid=77901
> 
> -Tim
> 
> 
> Timothy Penner
> Senior Technical Services Engineer
> 
> 4D Inc
> 95 S. Market Street, Suite #240
> CA 95113 San Jose
> United States

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: Web Service Call in 4Dv15

[Timothy Penner via 4D_Tech]

Is it possible that the SOAP Server you are connecting to is older, and does 
not understand current TLS versions above TLS 1.0?

v11 supported SSLv2/SSLv3 while v15 does not.

Reminders,
SSLv3 and SSLv2 is disabled at the network layer in 4D as of v13 & v14
http://forums.4d.com/Post/EN/15389376/1/15389377#15389377
http://forums.4d.com/Post/FR/15389373/1/15389374#15389374

I think that TLS 1.0 is disabled at the network layer in 4D as of v15 leaving 
only TLS 1.1 and 1.2 as an option in v15, but I am have not found a public 
reference for this yet.

TLS 1.2 is set as the minimum TLS version at the network layer in 4D as of v16R5
https://blog.4d.com/more-security-for-your-4d-server/
http://kb.4d.com/assetid=77901

-Tim



**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Web Service Call in 4Dv15

[Ronnie Teo via 4D_Tech]

Hi All, 

I raised this question almost a month ago now and am still stuck on the same 
problem. 
I have raised a case with 4D but the reply ahas been very generic, with 
references to the web services section of the manual (of which I have read 
numerous times).

A quick refresh, I am unable to consume a web service from a 4Dv15.5 
application (converted from 4Dv11). 
The Windows environment is Windows 2012 server.
The same v11 app running on the same server is able to call the same web 
service to transmit an XML document successfully. 

Just to be clear…..my app is not hosting the web service, only consuming a 
service hosted by an external system.  
The application calls a web service and sends out an XML document (outgoing 
only, no incoming).

In both applications (v11 and v15), the same web service call is made : 
WEB SERVICE 
CALL($txtSOAP_URL;$txtSOAP_Action;txtSOAP_Method;$txtSOAP_Namespace; Web 
Service manual) 
….where the $txtSOAP_URL is a secured “https://“ connection.

To date, this is what we have tried…. 

1.  Used the Web Service Get Info command to capture the error code returned.  
That’s confirmed to be a 9913, soap server unreachable error.
2.  The “server not reachable” state is not caused by any long timeout duration 
because the failure is instantaneous once the Web Service Call command is 
called.
3.  I have tried using the both the hostname and the actual IP address for the 
soap URL; both failed.
4.  Have tried all the options available for the last parameter in the Web 
Service Call command with no success. 
5.  Ensured that the outgoing port number “8787” is open.  (it has to be open 
since transmission works with v11 on the same machine)
6.  Set up a new test server.  the same results were replicated.  Successful 
transmission with v11, failure with v15.


Could it be a security certificate issue for the v15 app that cause the soap 
server to be deemed not reachable every time the web service call is made? 
I’m desperately short of ideas as to what to try next.
If anyone has any suggestions, please help.  Thanks.


Regards, 
Ronnie 
Tarawerkz 

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: Web Service Call in 4Dv15

[Epperlein, Lutz (agendo) via 4D_Tech]

Not sure, but maybe there is an issue with the certificates on the v15 server. 
If I remember correctly, it isn't necessary to have a pub key file in the 
database folder, it could even be harmful to https connections.

HTH
Regards
Lutz Epperlein
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Web Service Call in 4Dv15

[Ronnie Teo via 4D_Tech]

Hi All,

I raised this question a week ago and am still stuck on the same problem.
A quick refresh, I am unable to consume a web service from a 4Dv15.5 
application (converted from 4Dv11).
The v15 application is running on a Windows 2012 server, say Server1.

The 4D v11 application running on the same server (Server1) is able to call the 
web service to transmit an XML document with no issues.

I have also verified with a separate v15 application running at another 
installation (Server2) that is able to transmit successfully.
So it seems not to be an issue with any v15 coding issue.

In all applications (v11 and v15), the same web service call is made :
WEB SERVICE 
CALL($txtSOAP_URL;$txtSOAP_Action;txtSOAP_Method;$txtSOAP_Namespace;Web Service 
manual)
 

The only difference between the soap URL on Server1 and Server2 is that on 
Server 1, the URL begins with “https://“ - a secured connection, while on 
Server2, it starts with “http://“.   

On Server1, however v11 does not have any problem with the “https://“ 
connection. 
Could it be s security certification issue for the v15 app, that’s why the soap 
server is deemed not reachable every time the web service call is made?

Seems like there is very little left to be done on the 4D-end.  
Does anyone have any other ideas how to troubleshoot and solve this?  

Regards,
Ronnie
Tarawerkz




> On 11 Apr 2018, at 1:57 pm, Ronnie Teo  wrote:
> 
> Hi All,
> 
> I would like to seek some help/advise on an XML issue in 4Dv15 on Windows.
> 
> I have an app that is currently running in v11.  XML transmission via the 
> consumption of a hosted web service is working well.
> User decides to upgrade their server from Windows Server 2008r2 to 2012 and 
> from v11 to v15.
> 
> XML transmission from the v11 database when ported over to the new staging 
> server continues to work well.  For the converted v15 application, running on 
> the same staging server, everything works except the XML transmission.  Same 
> server, same port, soap URL, same web service yet it works on v11 works but 
> not v15.
> 
> On v15, the Web Service Call command returns with the OK variable not equal 
> to 1  and a soap server not reachable response.
> 
> Have tried comparing all the settings between the two 4D versions to make 
> them similar but to no avail.  Does anyone have any encounters with this 
> issue or what could possibly have gone awry with the Web Service Call command 
> in v15?
> 
> 
> Thanks,
> Ronnie
> Tarawerkz

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Web Service Call in 4Dv15

[Ronnie Teo via 4D_Tech]

Thanks Patrick, I’ll check it out.
> Did you check preference in 4D about security. There is some improvement on

> it. It may be the cause.

> For that, there is an article on the 4D Blog (blog.4d.com 
> )

> 

> Patrick



Julio, the web service is not hosted by 4D, so a 4D web service license is not 
required.
In any case, the same call from v11 works from the same server station calling 
the same port, but not v15.
> 4D WebServices license perhaps?




Regards,
Ronnie
Tarawerkz




**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Web Service Call in 4Dv15

[Julio Carneiro via 4D_Tech]

4D WebServices license perhaps?

> On Apr 11, 2018, at 2:57 AM, Ronnie Teo via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Hi All,
> 
> I would like to seek some help/advise on an XML issue in 4Dv15 on Windows.
> 
> I have an app that is currently running in v11.  XML transmission via the 
> consumption of a hosted web service is working well.
> User decides to upgrade their server from Windows Server 2008r2 to 2012 and 
> from v11 to v15.
> 
> XML transmission from the v11 database when ported over to the new staging 
> server continues to work well.  For the converted v15 application, running on 
> the same staging server, everything works except the XML transmission.  Same 
> server, same port, soap URL, same web service yet it works on v11 works but 
> not v15.
> 
> On v15, the Web Service Call command returns with the OK variable not equal 
> to 1  and a soap server not reachable response.
> 
> Have tried comparing all the settings between the two 4D versions to make 
> them similar but to no avail.  Does anyone have any encounters with this 
> issue or what could possibly have gone awry with the Web Service Call command 
> in v15?
> 
> 
> Thanks,
> Ronnie
> Tarawerkz
> 

--
Julio Carneiro
jjfo...@gmail.com



**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Web Service Call in 4Dv15

[Ronnie Teo via 4D_Tech]

Hi All,

I would like to seek some help/advise on an XML issue in 4Dv15 on Windows.

I have an app that is currently running in v11.  XML transmission via the 
consumption of a hosted web service is working well.
User decides to upgrade their server from Windows Server 2008r2 to 2012 and 
from v11 to v15.

XML transmission from the v11 database when ported over to the new staging 
server continues to work well.  For the converted v15 application, running on 
the same staging server, everything works except the XML transmission.  Same 
server, same port, soap URL, same web service yet it works on v11 works but not 
v15.

On v15, the Web Service Call command returns with the OK variable not equal to 
1  and a soap server not reachable response.

Have tried comparing all the settings between the two 4D versions to make them 
similar but to no avail.  Does anyone have any encounters with this issue or 
what could possibly have gone awry with the Web Service Call command in v15?


Thanks,
Ronnie
Tarawerkz
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**