Passing credentials using WS-Security headers
Requirements
User level
Beginning
When invoking a LiveCycle ES service using web services, you can use WS-Security headers to pass client authentication information that is required by LiveCycle ES. WS-Security defines SOAP extensions to implement client authentication, message confidentiality, and message integrity. As a result, you can invoke LiveCycle ES services when LiveCycle ES is deployed as stand-alone server or within a clustered environment.
How you pass WS-Security headers to LiveCycle ES depends on whether you are using Axis-generated Java classes or a .NET client assembly that consumes a service's native SOAP stack.
Note: As an example of invoking a service using WS-Security headers, this topic encrypts a PDF document with a password by invoking the Encryption service.
This document covers the following topics:
- Passing client authentication using Axis-generated Java classes
- Generating Axis library files required to invoke the Encryption service
- Invoking the Encryption service using a WS-Security header
- Passing client authentication using a .NET client assembly
- Invoking the Encryption service using a WS-Security header
Requirements
In order to make the most of this document, you need to have a solid understanding of the LiveCycle ES software.
Read the article:
Where to go from here
Visit the LiveCycle Developer Center for more resources.
