Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
1 reply
Subscribers
7 subscribers
Views
1202 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
We have a requirement where we have to communicate to another system using webse
roopeshr
over 9 years ago
We have a requirement where we have to communicate to another system using webservice but it is required to vaidate digital certificates and signatures , so how can we do this ?
Note: we have to follow XMLDSig standards . both signatures(signatures in the two systems) should be mutually accepted and replied in the soap body.
OriginalPostID-192972
OriginalPostID-192972
Discussion posts and replies are publicly visible
Parents
0
sayedh
over 9 years ago
Ideally, this should be architected with a middleware component if possible. Do you have a middleware team at your organization? If so, then you should have the middleware team provide a proxy service that Appian can call with UsernameToken (i.e. username and password).
1. Middleware provide a service that does the digital signature to the downstream service.
2. Appian calls the middleware service rather than the downstream service (using UsernameToken).
The above is the best approach.
If a middleware component is not an option, then you can write a plugin. To do the digital signature, you'll have to use something like:
1. axis2 and rampart
2. axis 1.3 and wss4j
3. jax-ws
I would use one of the older versions of Axis if I had to do this. The later versions have too many dependencies that often conflict with the classses/packages/jars that are made available via OSGI. With axis2 for example, you'll likely run into NoClassDefFoundError errors and that will take a while to resolve.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sayedh
over 9 years ago
Ideally, this should be architected with a middleware component if possible. Do you have a middleware team at your organization? If so, then you should have the middleware team provide a proxy service that Appian can call with UsernameToken (i.e. username and password).
1. Middleware provide a service that does the digital signature to the downstream service.
2. Appian calls the middleware service rather than the downstream service (using UsernameToken).
The above is the best approach.
If a middleware component is not an option, then you can write a plugin. To do the digital signature, you'll have to use something like:
1. axis2 and rampart
2. axis 1.3 and wss4j
3. jax-ws
I would use one of the older versions of Axis if I had to do this. The later versions have too many dependencies that often conflict with the classses/packages/jars that are made available via OSGI. With axis2 for example, you'll likely run into NoClassDefFoundError errors and that will take a while to resolve.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data