SOAP to REST transformation

Kong / kong

🦍 The Cloud-Native API Gateway and AI Gateway.

https://konghq.com/install/#kong-community

Apache License 2.0

38.78k stars 4.77k forks source link

SOAP to REST transformation #330

Closed sonicaghi closed 3 years ago

lucamaraschi commented 9 years ago

:+1:

kyyberi commented 9 years ago

Might not be out of the box solution, but there's one implementation for REST-SOAP-REST conversion feature (in Estonian X-Road) created by Finnish developers. https://github.com/educloudalliance/xroad-rest-gateway

iopsthecloud commented 8 years ago

:+1:

AlexMikhalev commented 8 years ago

I am looking forward for it to become part of the kong solution!

BrianHutchison commented 8 years ago

Is it too late to +1 this?

Would be nice to specify apikey in wsse:Security, e.g.

<soapenv:Header>
                        <wsse:Security>
                                    <wsse:UsernameToken>
                                                <wsse:Username>fe7060ae-2907-4f90-9d60-f0ba9d9ec5e4</wsse:Username>
                                    </wsse:UsernameToken>
                        </wsse:Security>
</soapenv:Header>

willfarrell commented 8 years ago

lua starting point: https://github.com/tomasguisasola/luasoap

nodejs implementation by IBM: https://github.com/strongloop/loopback-connector-soap

mdan1eli commented 7 years ago

I would really start from a SOAP authentication plugin and keep Kong more as a gateway for exposure, more than an integration layer for consumption. We have camel routes runnning in containers behind Kong for that, though i know that technically a plugin can be built. Don't want functional stuff on this layer. I want policies only.

AlexMikhalev commented 7 years ago

Having it via plugin would be fine. Also that's why apigee bought by Google - this is important functionality for gateway to have to be able to serve in enterprise world.

mdan1eli commented 7 years ago

SOAP plugins for authentication (username, certificate and saml), backend protection (payload size limiting and payload validation) and monitoring (logging and auditing). They are very similar to stuff that already exists for generic HTTP services just a bit specialized. The soap to rest can also be seen as a specialization of the transformation plugins, but in truth soap-rest is a bit more than xml <> json to me. For example support for ws security and ws trust standards (how to map these standards in the transformation) and it gets more complicated and that is why i separate the two needsand I want to keep my gateway simple to operate and avoid being over ambitious). Having above soap capabilities as plugin would extend reach to scenarios where we employ tools like IBM DP as a SOA Gateway for B2B.

sonicaghi commented 7 years ago

Some discussed here https://github.com/Mashape/kong/issues/1536

willfarrell commented 7 years ago

SOAP plugins for authentication (applying digital signatures and encrypt/decrypt transformations) would be a great first step and be better suited to the scope of kong as @mdan1eli mentioned. I just implemented something very similar in node using https://github.com/yaronn/ws.js. @yaronn might be a good technical resource on this piece and would definitely be able to scope out the requirements needed to tackle this.