Watch, Follow, &
Connect with Us

Please visit our new home
community.embarcadero.com.

Public Report
Report From: Delphi-BCB/SOAP    [ Add a report in this area ]  
Report #:  104755   Status: Open
Support for new Web Services - WS-Security 1.1, WS-Trust 1.3, WS-SecurityPolicy 1.2
Project:  Delphi Build #:  ALL
Version:    16.4 Submitted By:   Yucel Tepekoy
Report Type:  Suggestion / Enhancement Request Date Reported:  4/9/2012 12:11:28 PM
Severity:    Serious / Highly visible problem Last Updated: 5/9/2012 8:09:40 AM
Platform:    All platforms Internal Tracking #:  
Resolution: None (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (16 Total Ratings)
4.63 out of 5
Total Votes: 518
Description
In Turkey there are a lot of hospital management information systems and many other applications using the web services of the Turkish National ID System in order to obtain mandatory information which has to be processed by the hospital management information system.

With the new change done by the Turkish Census Department's access to the Turkish National ID System, hospital management software developed in Delphi in order to access the Turkish National ID System fails to communicate with the new web services.

The Census Department has announced that the following web service standards must be used in order to access the web services.

WS-Security 1.1
WS-Trust 1.3
WS-SecurityPolicy 1.2

Delphi XE2 and previous versions do not support the above Web Service protocols.

This situation is very urgent and is being requested by almost all developers in Turkey because they come up with situations where they must use the National ID System.

The problems arising from this and why it is so important can be given in such an example. For example in the USA, a lot of applications use Social Security Number to access credit berueue information about real persons from the 3 main credit berueues. Think of a situation where these berueues change their web service access protocols, and we are not able to support the new web service access protocol using Delphi. This is the criticality situation of this in Turkey, where Delphi completely fails in a business vital functionality.

Please note that in the Turkish Delphi Forum this issue is the most viewed issue by users (over 255 views). This Forum just opened by BTG Turkish Embarcadero Distributor 2 weeks ago.

http://delphiforumu.com/questions/14/delphi-ile-ws-standartlarini-kullanan-web-servislerine-erismek
Steps to Reproduce:
None
Workarounds
A service to access the National ID System service is written using c# via Visual Studio. And Delphi uses this intermediary solution to access the necessary solution. THis deterioriates Delphi credibility.
Attachment
None
Comments

Ilya S at 4/12/2012 9:06:11 AM -
Same here, in Russia. System of state electronic document interchange is being developed targeting ambitious goal for eGoverment. Each participant should implement SOAP client and server on their side using digital signature for each request/response (XMLDSig and XAdES). Unfortunately, documentation we have is mostly about signing, not about which WS-* are in use. WS-I Basic Profile 1.1 is mentioned only.
I've seen 2 choices so far: Java Axis and .NET/WCF. No Delphi and native code as you can see. Even WWSAPI header translation for Windows 7/2008R2 would be nice to start from.

Steffen Nyeland at 10/10/2012 7:40:36 AM -
You can add Denmark as well, the IRS and several other govermental web services uses WS* services. What could have been a "5 minute" task, now is very problematic. XE2 Enterprise user.

David Pedrelli at 10/19/2012 3:39:27 AM -
The Social Security Administration, in the United States, requires WS-Security.

Odd B. Børtveit at 1/22/2014 1:40:16 AM -
In Norway, those of the govermental services that require end to end encryption also require support for ws-*.

Roger Dunn at 3/5/2014 10:23:17 AM -
I added duplicate 122319 to the system hoping for the same thing.  Our state's court SOAP services now require WS authentication and Delphi XE5 Enterprise doesn't support it.  What's a developer to do that maintains a large application in Delphi which needs to connect to those SOAP services with a username and password?

I've tried using custom TSoapHeaders but it never seems to come out right.

Steffen Nyeland at 8/27/2014 12:35:46 AM -
A bit late - but I do now have Delphi project running against WS-Security services - I ended up at that time using Clever Components Clever Internet Suite. Works great but seems not to have been updated since XE5 - but since source is included not an issue.

Server Response from: ETNACODE01