New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Get the WS-Security issue sorted with PHP/node/ruby #1

Open

jacques opened this issue Nov 23, 2016 · 0 comments

Member

jacques commented Nov 23, 2016 •

edited

Loading

The ongoing saga with using SmartCall from a language other than Java.

Options for connecting to SmartCall:

Run SmartCall's Webservices Proxy on Windows (needs retrofitting to work on non-Unix machines) -- Cost +/- $98.00/mo (+/- R 1500 which will vary with the exchange rate).
Build our own Java Proxy (+/- R 40k in dev costs)
Modify the php c extension to support WS-Security and encrypted bodys in SOAP, etc.
Keep using a pinbank that we populate from orders from SmartCall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment