You can request SAML tokens with the sender-vouches subject
confirmation method from an external Security Token Service (STS).
After obtaining the SAML sender-vouches token, you can then send these
tokens with web services request messages using the Java API for XML-Based Web Services (JAX-WS)
programming model and Web Services Security APIs (WSS API) with message
level protection.
Before you begin
This task assumes that you are familiar with the JAX-WS
programming model, the WSS API interfaces, SAML concepts, SSL transport
protection, X.509 security token, and the use of policy sets to configure
and administer web services settings.
About this task
You can request a SAML token with the sender-vouches subject
confirmation method from an external STS and then send the SAML token
in web services request messages from a web services client using
WSS APIs with message level protection.
This product does not
provide a default policy set that requires SAML tokens with sender-vouches
subject confirmation method. Read about configuring client and provider
bindings for the SAML sender-vouches token to learn more about how
to create a Web Services Security policy to require SAML tokens with
sender-vouches subject confirmation and how to create a custom binding
configuration. You must attach the policy and binding to the web
services provider. The code sample described in this task assumes
that the web services provider policy requires that both the SAML
tokens and the message bodies are digitally signed by using an X.509
security token.
The web services client application used in
this task is a modified version of the client code that is contained
in the JaxWSServicesSamples sample application that is available for
download. Code examples from the sample are described in the procedure,
and a complete, ready-to-use web services client sample is provided.
Procedure
- Identify and obtain the web services client that you want
to use to invoke a web services provider.
Use this client
to insert SAML tokens in SOAP request messages programmatically using
WSS APIs.
The web services client used in this procedure is
a modified version of the client code that is contained in the JaxWSServicesSamples
web services sample application.
To obtain and modify the sample
web services client to add the Web Services Security API to pass SAML
sender-vouches tokens in SOAP request messages programmatically using
WSS APIs, complete the following steps:
- Download the JaxWSServicesSamples sample application. The JaxWSServicesSamples sample is not installed by default.
- Obtain the JaxWSServicesSamples client code.
For
example purposes, this procedure uses a modified version of the Echo
thin client sample that is included in the JaxWSServicesSamples sample.
The web services Echo thin client sample file, SampleClient.java,
is located in the src\SampleClientSei\src\com\ibm\was\wssample\sei\cli directory.
The sample class file is included in the WSSampleClientSei.jar file.
The JaxWSServicesSamples.ear enterprise
application and supporting Java archives
(JAR) files are located in the installableApps directory
within the JaxWSServicesSamples sample application.
- Deploy the JaxWSServicesSamples.ear file
onto the application server. After you deploy the JaxWSServicesSamples.ear file,
you are ready to test the sample web services client code against
the sample application.
Instead of using the web services client sample, you can
choose to add the code snippets to pass SAML tokens in SOAP request
messages programmatically using WSS APIs in your own web services
client application. The example in this procedure uses a JAX-WS web
services thin client; however, you can also use a managed client.
- Specify to use SSL message-level message protection. Use the following JVM property to specify to use SSL to protect
the SAML token request with the STS:
-Dcom.ibm.SSL.ConfigURL=file:profile_root\properties\ssl.client.props
Alternatively,
you can define the SSL configuration file using a Java system property in the sample client code;
for example:System.setProperty("com.ibm.SSL.ConfigURL", "file:profile_root/properties/ssl.client.props");
- Add the Thin Client for JAX-WS JAR file to the class path. Add the app_server_root/runtimes/com.ibm.jaxws.thinclient_8.5.0.jar
file to the class path. See the testing web services-enabled clients
information for more information about adding this JAR file to the
class path.
- Request the SAML token from an external STS. The
following code snippet illustrates how to request the SAML sender-vouches
token and assumes that an external STS is configured to accept a Username
token, and to issue a SAML 2.0 token using sender-vouches after validation:
//Request the SAML Token from external STS
WSSFactory factory = WSSFactory.getInstance();
String STS_URI = "https://externalstsserverurl:port/TrustServerWST13/services/RequestSecurityToken";
String ENDPOINT_URL = "http://localhost:9080/WSSampleSei/EchoService";
WSSGenerationContext gencont1 = factory.newWSSGenerationContext();
WSSConsumingContext concont1 = factory.newWSSConsumingContext();
HashMap<Object, Object> cbackMap1 = new HashMap<Object, Object>();
cbackMap1.put(SamlConstants.STS_ADDRESS, STS_URI);
cbackMap1.put(SamlConstants.SAML_APPLIES_TO, ENDPOINT_URL);
cbackMap1.put(SamlConstants.TRUST_CLIENT_WSTRUST_NAMESPACE, "http://docs.oasis-open.org/ws-sx/ws-trust/200512");
cbackMap1.put(SamlConstants.TRUST_CLIENT_COLLECTION_REQUEST, "false");
cbackMap1.put(SamlConstants.TOKEN_TYPE, WSSConstants.SAML.SAML11_VALUE_TYPE);
cbackMap1.put(SamlConstants.CONFIRMATION_METHOD, "sender-vouches");
SAMLGenerateCallbackHandler cbHandler1 = new SAMLGenerateCallbackHandler(cbackMap1);
// Add UNT to trust request
UNTGenerateCallbackHandler utCallbackHandler = new UNTGenerateCallbackHandler("testuser", "testuserpwd");
SecurityToken ut = factory.newSecurityToken(UsernameToken.class, utCallbackHandler);
gencont1.add(ut);
cbHandler1.setWSSConsumingContextForTrustClient(concont1);
cbHandler1.setWSSGenerationContextForTrustClient(gencont1);
SecurityToken samlToken = factory.newSecurityToken(SAMLToken.class, cbHandler1, "system.wss.generate.saml");
System.out.println("SAMLToken id = " + samlToken.getId());
- Use the WSSFactory newSecurityToken method to specify
how to request the SAML token from an external STS.
Specify
the following method to create the SAML token:
WSSFactory newSecurityToken(SAMLToken.class, callbackHandler, "system.wss.generate.saml")
Requesting
a SAML token requires the Java security
permission wssapi.SAMLTokenFactory.newSAMLToken. Use the Policy Tool
to add the following policy statement to the Java security policy file or the application
client was.policy file:
permission java.security.SecurityPermission "wssapi.SAMLTokenFactory.newSAMLToken"
The SAMLToken.class parameter
specifies the type of security token to create.
The
callbackHandler object
contains parameters that define the characteristics of the SAMLToken
that you are requesting and other parameters required to reach the
STS and obtain the SAML token. The SAMLGenerateCallbackHandler object
specifies the configuration parameters described in the following
table:
Table 1. SAMLGenerateCallbackHandler
properties. This table describes the configuration parameters
for the SAMLGenerateCallbackHandler object using the sender-vouches
confirmation method.Property |
Description |
Required |
SamlConstants.CONFIRMATION_METHOD |
Specifies to use the sender-vouches confirmation
method. |
Yes |
SamlConstants.TOKEN_TYPE |
Specifies the token type.
When
a web services client has policy set attachments, this property is
not used by the Web Services Security runtime environment.
Specify
the token value type by using the valueType attribute
of the tokenGenerator binding configuration.
The example in
this procedure uses a SAML 1.1 token; however, you can also use the WSSConstants.SAML.SAML20_VALUE_TYPE value.
|
Yes |
SamlConstants.STS_ADDRESS |
Specifies the Security Token
Service address.
For the example used in this task topic, the
value of this property is set to https to specify
to use SSL to protect the SAML Token request.
You must set
the -Dcom.ibm.SSL.ConfigURL property to enable the use of SSL to protect
the SAML token request with the STS.
|
Yes |
SamlConstants.SAML_APPLIES_TO |
Specifies the target STS address
for where you want to use the SAML token. |
No |
SamlConstants.TRUST_CLIENT_COLLECTION_REQUEST |
Specifies whether to request from
the STS a single token that is enclosed in a RequestSecurityToken
(RST) element or multiple tokens in a collection of RST elements that
are enclosed in a single RequestSecurityTokenCollection (RSTC) element. The
default behavior is to request a single token that is enclosed in
a RequestSecurityToken (RST) element from the STS.
Specifying
a true value for this property indicates to request
multiple tokens in a collection of RST elements that are enclosed
in a single RequestSecurityTokenCollection (RSTC) element from the
STS.
|
No |
SamlConstants.TRUST_CLIENT_WSTRUST_NAMESPACE |
Specifies the WS-Trust namespace
that is included in the WS-Trust request. The default value is WSTrust
1.3.
|
No |
A WSSGenerationContext instance and a WSSConsumingContext
instance are also set in the SAMLGenerateCallbackHandler object. The
WSSGenerationContext instance must contain a UNTGenerateCallbackHandler
object with the information to create the UsernameToken that you want
to send to the STS.
The
system.wss.generate.saml parameter
specifies the Java Authentication
and Authorization Service (JAAS) login module that is used to create
the SAML token. You must specify a JVM property to define a JAAS
configuration file that contains the required JAAS login configuration;
for example:
-Djava.security.auth.login.config=profile_root/properties/wsjaas_client.conf
Alternatively,
you can specify a JAAS login configuration file by setting a Java system property in the sample
client code; for example:
System.setProperty("java.security.auth.login.config", "profile_root/properties/wsjaas_client.conf");
- Obtain the token identifier of the created SAML token.
Use the following statement as a simple test for the SAML
token that you created:
System.out.println("SAMLToken id = " + samlToken.getId())
- Add the SAML token to the SOAP security header of web services
request messages.
- Initialize the web services client and configure the
SOAPAction properties. The following code example illustrates
these actions:
// Initialize web services client
EchoService12PortProxy echo = new EchoService12PortProxy();
echo._getDescriptor().setEndpoint(endpointURL);
// Configure SOAPAction properties
BindingProvider bp = (BindingProvider) (echo._getDescriptor().getProxy());
Map<String, Object> requestContext = bp.getRequestContext();
requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointURL);
requestContext.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
requestContext.put(BindingProvider.SOAPACTION_URI_PROPERTY, "echoOperation");
// Initialize WSSGenerationContext
WSSGenerationContext gencont = factory.newWSSGenerationContext();
gencont.add(samlToken);
- Initialize the WSSGenerationContext. The
following code snippet illustrates the use of the gencont.object of
the WSSGenerationContext type to initialize a generation context to
enable you to insert the SAMLToken into a web services
request message:
// Initialize WSSGenerationContext
WSSGenerationContext gencont = factory.newWSSGenerationContext();
gencont.add(samlToken);
Specifically, the
gencont.add(samlToken) method
call specifies to put the SAML token into a request message. This
operation requires the client code to have the following Java 2 Security permission:
permission javax.security.auth.AuthPermission "modifyPrivateCredentials"
- Add an X.509 token for message protection using the Web
Services Security API.
This sample code uses the dsig-sender.ks
key file and the SOAPRequester sample key. You must not use the sample
key in a production environment. The following code snippet illustrates
adding an X.509 token for message protection:
// Add an X.509 Token for message protection
X509GenerateCallbackHandler x509callbackHandler = new X509GenerateCallbackHandler(
null,
"profile_root/etc/ws-security/samples/dsig-sender.ks",
"JKS",
"client".toCharArray(),
"soaprequester",
"client".toCharArray(),
"CN=SOAPRequester, OU=TRL, O=IBM, ST=Kanagawa, C=JP", null);
SecurityToken x509 = factory.newSecurityToken(X509Token.class,
x509callbackHandler, "system.wss.generate.x509");
WSSSignature sig = factory.newWSSSignature(x509);
sig.setSignatureMethod(WSSSignature.RSA_SHA1);
WSSSignPart sigPart = factory.newWSSSignPart();
sigPart.setSignPart(samlToken);
sigPart.addTransform(WSSSignPart.TRANSFORM_STRT10);
sig.addSignPart(sigPart);
sig.addSignPart(WSSSignature.BODY);
- Create a WSSSignature object with the X509 token. The following line of code creates a WSSSignature object with
the X509 token:
WSSSignature sig = factory.newWSSSignature(x509);
- Add the signed part to use for message protection. The following line of code specifies to add WSSSignature.BODY
as the signed part:
sig.addSignPart(WSSSignature.BODY);
- Add the timestamp element in the SOAP messages security
header. The SAML20 SenderVouches WSHTTPS and SAML11 SenderVouches
WSHTTPS policy sets require web services requests and response messages
to carry a timestamp element in the SOAP messages Security header.
In the following code snippet, the factory.newWSSTimestamp() method
call generates the timestamp, and the gencont.add(timestamp) method
call adds the timestamp into the request message:
// Add Timestamp
WSSTimestamp timestamp = factory.newWSSTimestamp();
gencont.add(timestamp);
sig.addSignPart(WSSSignature.TIMESTAMP);
gencont.add(sig);
WSSConsumingContext concont = factory.newWSSConsumingContext();
- Configure the SAML token signature using STR-Transform
transform algorithm.
A separate WSSSignPart is needed
to specify the SecurityTokenReference transformation algorithm that
is represented by the
WSSSignPart.TRANSFORM_STRT10 attribute.
A SAML Token cannot be digitally signed directly. This attribute
enables the Web Services Security runtime environment to generate
a SecurityTokenReference element to reference the SAMLToken and to
digitally sign the SAMLToken using the SecurityTokenReference transformation.
The following line of code specifies to use the
WSSSignPart.TRANSFORM_STRT10 attribute:
WSSSignPart sigPart = factory.newWSSSignPart();
sigPart.setSignPart(samlToken);
sigPart.addTransform(WSSSignPart.TRANSFORM_STRT10);
- Attach the WSSGenerationContext object to the web services
RequestContext object. The WSSGenerationContext object
now contains all the security information that is required to format
a request message. The gencont.process(requestContext) method
call attaches the WSSGenerationContext object to the web services
RequestContext object to enable the Web Services Security runtime
environment to format the required SOAP security header; for example:
// Attaches the WSSGenerationContext object to the web services RequestContext object.
gencont.process(requestContext);
- Use the X.509 token to validate the digital signature and
the integrity of the response message. If the provider
policy requires the response message to be digitally signed, you must
initialize the X.509 token.
- A X509ConsumeCallbackHandler object is initialized with
a truststore, dsig-receiver.ks, and a certificate path object to validate
the provider digital signature. The following line of
code is used to initialize the X509ConsumeCallbackHandler object:
X509ConsumeCallbackHandler callbackHandlerVer = new X509ConsumeCallbackHandler(
"profile_root/etc/ws-security/samples/dsig-receiver.ks",
"JKS",
"server".toCharArray(),
certList,
java.security.Security.getProvider("IBMCertPath"));
- A WSSVerification object is created and the message
body is added to the verification object so that the Web Services
Security runtime environment validates the digital signature.
The following line of code is used to initialize the WSSVerification
object:
WSSVerification ver = factory.newWSSVerification(X509Token.class, callbackHandlerVer);
The
WSSConsumingContext object now contains all the security information
that is required to format a request message. The
concont.process(requestContext) method
call attaches the WSSConsumingContext object to the response method;
for example:
// Attaches the WSSConsumingContext object to the web services RequestContext object.
concont.process(requestContext);
Results
You have requested a SAML token with the sender-vouches
confirmation method from an external STS. After obtaining the token,
you sent the token with web services request messages using message
level protection using the JAX-WS programming model and WSS APIs.
Example
The following code sample is a complete, ready-to-use
web services client application that demonstrates how to request a
SAML token from an external STS and send that SAML token in web services
request messages with message level protection. This sample code illustrates
the procedure steps described previously.
/**
* The following source code is sample code created by IBM Corporation.
* This sample code is provided to you solely for the purpose of assisting you in the
* use of the technology. The code is provided 'AS IS', without warranty or condition of
* any kind. IBM shall not be liable for any damages arising out of your use of the
* sample code, even if IBM has been advised of the possibility of such damages.
*/
package com.ibm.was.wssample.sei.cli;
import com.ibm.was.wssample.sei.echo.EchoService12PortProxy;
import com.ibm.was.wssample.sei.echo.EchoStringInput;
import com.ibm.websphere.wssecurity.callbackhandler.SAMLGenerateCallbackHandler;
import com.ibm.websphere.wssecurity.callbackhandler.UNTGenerateCallbackHandler;
import com.ibm.websphere.wssecurity.wssapi.token.UsernameToken;
import com.ibm.websphere.wssecurity.wssapi.WSSConsumingContext;
import com.ibm.websphere.wssecurity.wssapi.WSSFactory;
import com.ibm.websphere.wssecurity.wssapi.WSSGenerationContext;
import com.ibm.websphere.wssecurity.wssapi.WSSTimestamp;
import com.ibm.websphere.wssecurity.wssapi.token.SAMLToken;
import com.ibm.websphere.wssecurity.wssapi.token.SecurityToken;
import com.ibm.websphere.wssecurity.callbackhandler.X509ConsumeCallbackHandler;
import com.ibm.websphere.wssecurity.callbackhandler.X509GenerateCallbackHandler;
import com.ibm.websphere.wssecurity.wssapi.WSSException;
import com.ibm.websphere.wssecurity.wssapi.signature.WSSSignPart;
import com.ibm.websphere.wssecurity.wssapi.signature.WSSSignature;
import com.ibm.websphere.wssecurity.wssapi.verification.WSSVerification;
import com.ibm.websphere.wssecurity.wssapi.token.X509Token;
import com.ibm.wsspi.wssecurity.core.token.config.WSSConstants;
import com.ibm.wsspi.wssecurity.saml.config.SamlConstants;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.InputStream;
import java.security.InvalidAlgorithmParameterException;
import java.security.NoSuchAlgorithmException;
import java.security.NoSuchProviderException;
import java.security.cert.CertStore;
import java.security.cert.CertificateException;
import java.security.cert.CertificateFactory;
import java.security.cert.CollectionCertStoreParameters;
import java.security.cert.X509Certificate;
import java.util.HashSet;
import java.util.Set;
import java.util.HashMap;
import java.util.Map;
import javax.xml.ws.BindingProvider;
public class SampleSamlSVClient {
private String urlHost = "localhost";
private String urlPort = "9080";
private static final String CONTEXT_BASE = "/WSSampleSei/";
private static final String ECHO_CONTEXT12 = CONTEXT_BASE+"EchoService12";
private String message = "HELLO";
private String uriString = "http://" + urlHost + ":" + urlPort;
private String endpointURL = uriString + ECHO_CONTEXT12;
private String input = message;
/**
* main()
*
* see printusage() for command-line arguments
*
* @param args
*/
public static void main(String[] args) {
SampleSamlSVClient sample = new SampleSamlSVClient();
sample.CallService();
}
/**
* CallService Parms were already read. Now call the service proxy classes.
*
*/
void CallService() {
String response = "ERROR!:";
try {
System.setProperty("com.ibm.SSL.ConfigURL", "profile_root/properties/ssl.client.props");
System.setProperty("java.security.auth.login.config", "profile_root/properties/wsjaas.conf");
//Request the SAML Token from external STS
WSSFactory factory = WSSFactory.getInstance();
String STS_URI = "https://externalstsserverurl:port/TrustServerWST13/services/RequestSecurityToken";
String ENDPOINT_URL = "http://localhost:9080/WSSampleSei/EchoService";
WSSGenerationContext gencont1 = factory.newWSSGenerationContext();
WSSConsumingContext concont1 = factory.newWSSConsumingContext();
HashMap<Object, Object> cbackMap1 = new HashMap<Object, Object>();
cbackMap1.put(SamlConstants.STS_ADDRESS, STS_URI);
cbackMap1.put(SamlConstants.SAML_APPLIES_TO, ENDPOINT_URL);
cbackMap1.put(SamlConstants.TRUST_CLIENT_WSTRUST_NAMESPACE, "http://docs.oasis-open.org/ws-sx/ws-trust/200512");
cbackMap1.put(SamlConstants.TRUST_CLIENT_COLLECTION_REQUEST, "false");
cbackMap1.put(SamlConstants.TOKEN_TYPE, WSSConstants.SAML.SAML11_VALUE_TYPE);
cbackMap1.put(SamlConstants.CONFIRMATION_METHOD, "sender-vouches");
SAMLGenerateCallbackHandler cbHandler1 = new SAMLGenerateCallbackHandler(cbackMap1);
// Add UNT to trust request
UNTGenerateCallbackHandler utCallbackHandler = new UNTGenerateCallbackHandler("testuser", "testuserpwd");
SecurityToken ut = factory.newSecurityToken(UsernameToken.class, utCallbackHandler);
gencont1.add(ut);
cbHandler1.setWSSConsumingContextForTrustClient(concont1);
cbHandler1.setWSSGenerationContextForTrustClient(gencont1);
SecurityToken samlToken = factory.newSecurityToken(SAMLToken.class, cbHandler1, "system.wss.generate.saml");
System.out.println("SAMLToken id = " + samlToken.getId());
// Initialize web services client.
EchoService12PortProxy echo = new EchoService12PortProxy();
echo._getDescriptor().setEndpoint(endpointURL);
// Configure SOAPAction properties
BindingProvider bp = (BindingProvider) (echo._getDescriptor().getProxy());
Map<String, Object> requestContext = bp.getRequestContext();
requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointURL);
requestContext.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
requestContext.put(BindingProvider.SOAPACTION_URI_PROPERTY, "echoOperation");
// Initialize WSSGenerationContext
WSSGenerationContext gencont = factory.newWSSGenerationContext();
gencont.add(samlToken);
// Add X.509 Tokens for message protection
X509GenerateCallbackHandler x509callbackHandler = new X509GenerateCallbackHandler(
null,
"profile_root/etc/ws-security/samples/dsig-sender.ks",
"JKS",
"client".toCharArray(),
"soaprequester",
"client".toCharArray(),
"CN=SOAPRequester, OU=TRL, O=IBM, ST=Kanagawa, C=JP", null);
SecurityToken x509 = factory.newSecurityToken(X509Token.class,
x509callbackHandler, "system.wss.generate.x509");
WSSSignature sig = factory.newWSSSignature(x509);
sig.setSignatureMethod(WSSSignature.RSA_SHA1);
WSSSignPart sigPart = factory.newWSSSignPart();
sigPart.setSignPart(samlToken);
sigPart.addTransform(WSSSignPart.TRANSFORM_STRT10);
sig.addSignPart(sigPart);
sig.addSignPart(WSSSignature.BODY);
// Add timestamp
WSSTimestamp timestamp = factory.newWSSTimestamp();
gencont.add(timestamp);
sig.addSignPart(WSSSignature.TIMESTAMP);
gencont.add(sig);
WSSConsumingContext concont = factory.newWSSConsumingContext();
// Prepare to consume timestamp in response message
concont.add(WSSConsumingContext.TIMESTAMP);
// Prepare to verify digital signature in response message
X509Certificate x509cert = null;
try {
InputStream is = new FileInputStream("profile_root/etc/ws-security/samples/intca2.cer");
CertificateFactory cf = CertificateFactory.getInstance("X.509");
x509cert = (X509Certificate) cf.generateCertificate(is);
} catch (FileNotFoundException e1) {
throw new WSSException(e1);
} catch (CertificateException e2) {
throw new WSSException(e2);
}
Set<Object> eeCerts = new HashSet<Object>();
eeCerts.add(x509cert);
java.util.List<CertStore> certList = new java.util.ArrayList<CertStore>();
CollectionCertStoreParameters certparam = new CollectionCertStoreParameters(eeCerts);
CertStore cert = null;
try {
cert = CertStore.getInstance("Collection", certparam, "IBMCertPath");
} catch (NoSuchProviderException e1) {
throw new WSSException(e1);
} catch (InvalidAlgorithmParameterException e2) {
throw new WSSException(e2);
} catch (NoSuchAlgorithmException e3) {
throw new WSSException(e3);
}
if (certList != null) {
certList.add(cert);
}
X509ConsumeCallbackHandler callbackHandlerVer = new X509ConsumeCallbackHandler(
"profile_root/etc/ws-security/samples/dsig-receiver.ks",
"JKS",
"server".toCharArray(),
certList,
java.security.Security.getProvider("IBMCertPath"));
WSSVerification ver = factory.newWSSVerification(X509Token.class, callbackHandlerVer);
ver.addRequiredVerifyPart(WSSVerification.BODY);
concont.add(ver);
gencont.process(requestContext);
concont.process(requestContext);
// Build the input object
EchoStringInput echoParm =
new com.ibm.was.wssample.sei.echo.ObjectFactory().createEchoStringInput();
echoParm.setEchoInput(input);
System.out.println(">> CLIENT: SEI Echo to " + endpointURL);
// Call the service
response = echo.echoOperation(echoParm).getEchoResponse();
System.out.println(">> CLIENT: SEI Echo invocation complete.");
System.out.println(">> CLIENT: SEI Echo response is: " + response);
} catch (Exception e) {
System.out.println(">> CLIENT: ERROR: SEI Echo EXCEPTION.");
e.printStackTrace();
}
}
}
When this web services client application sample
runs correctly, you receive messages like the following messages:
SAMLToken id = _6CDDF0DBF91C044D211271166233407
Retrieving document at 'file:profile_root/.../wsdl/'.
>> CLIENT: SEI Echo to http://localhost:9443/WSSampleSei/EchoService12
>> CLIENT: SEI Echo invocation complete.
>> CLIENT: SEI Echo response is: SOAP12==>>HELLO