Java Web Service: Ws-secureconversation performance

Look at how the Web service stack ws-secureconversation performance compared to the other

Introduction: Ws-secureconversation enables you to guarantee the security of ongoing WEB service message exchanges while spending less processing overhead than ordinary ws-security. In this article, you will learn how to configure ws-secureconversation and use it for the three main open source Java™web service stacks: Apache Axis2, Metro, and Apache CXF. You will also see a comparison of the ws-secureconversation performance of these three stacks.

Ws-security provides the necessary features to ensure the security of business Web services, but often pays a heavy price for performance. In Ws-trust and ws-secureconversation, you learned how to construct ws-secureconversation on ws-security and Ws-trust Symmetric encryption is used to secure the continuous message exchange between the client and server side. In this article, you will learn how to configure Ws-secureconversation for the three main open source Java Web service stacks-apache Axis2, Metro, and Apache cxf-will also see the right sex in comparison to ws-security asymmetric encryption The effect of energy.

Configure Ws-secureconversation

As discussed in the previous article, a client in a ws-secureconversation message exchange first connects to the security Token Service (STS) terminal to establish a secure context that contains a shared secret key. The shared key is then used as an encryption and/or a signed message exchange with the target service. The security context is confirmed by the Token (SCT) and returned to the client by STS. The SCT is included in all requests for services by the client as part of a security conversation and is referenced by the service in all responses.

For ordinary ws-security, the security configuration is defined in the Ws-policy document. When using ws-secureconversation: Two separate security configurations appear in service policies, one with STS for message exchange, and another for target services. The STS security configuration is embedded in the policy definition of the security dialog token.

The different ws-secureconversation performance tests in this article are:

Signature only

Encryption only

Signature and encryption