Feature #2687
add SSL support for the 4GL web services implementation
100%
History
#1 Updated by Greg Shah over 8 years ago
- Assignee set to Ovidiu Maxiniuc
Constantin: please post your thoughts about the work needed for this task. Consider also the #2181 which is being worked now.
#2 Updated by Ovidiu Maxiniuc over 8 years ago
At this moment I was able to communicate with a WSDL web-service but for the moment only over HTTP.
The problem is that, for accessing web-services, we rely on AXIS2 library. I checked the AXIS2 documentation and it should be very simple to switch to SSL, just by selecting the "https" in transportSender
/ CommonsHTTPTransportSender
. However, I don't think this is what we really need since we loose access to customizations noted in #2181. The same stands for the sever-side. For the moment, AXIS2 is handling low-level transport in background, using dedicated classes that are different than ours.
I will try to find a solution/API that would allow us to use our socket implementation (replacing its transportSender
with our own implementation of sockets), but I hardly doubt we can use the same classes we are using on the client-side when working with P4GL networking.
#3 Updated by Ovidiu Maxiniuc over 8 years ago
- the factory callback does not provides all information I need when instantiating the socket. The solution could be the properties, but I must investigate if and where they can be set.
- have to avoid an eventual double handshake in the case of secure connections.
#4 Updated by Greg Shah over 8 years ago
- Status changed from New to WIP
#5 Updated by Ovidiu Maxiniuc about 8 years ago
The final update for this task was committed to trunk with task branch 2181a as revision 10995.
Task can be closed.
#6 Updated by Greg Shah about 8 years ago
- % Done changed from 0 to 100
- Status changed from WIP to Closed
#7 Updated by Greg Shah over 7 years ago
- Target version changed from Milestone 12 to GUI Support for a Complex ADM2 App