Table of Contents

Search

  1. Preface
  2. Web Service Concepts
  3. Understanding the Web Services Provider
  4. Using the Web Services Hub Console
  5. Batch Web Service Operations
  6. Writing Client Applications
  7. Working with Web Service Sources and Targets
  8. Editing Web Service Sources and Targets
  9. Working with Web Service Mappings
  10. Working with Web Service Workflows
  11. Appendix A: Web Service Sample Client Applications
  12. Appendix B: Configure the Web Browser

Web Services Provider Guide

Web Services Provider Guide

Testing a Protected Real-time Web Service

Testing a Protected Real-time Web Service

To test a protected real-time web service, include a valid user name token in the SOAP header. You can enter the user name and password in the Form Input tab or modify the SOAP message to include all elements of the user name token in the XML Input tab.
You can test a protected web service with a plain text or hashed password in the Form Input or XML Input tab. To test a protected web service with a hashed password, encrypt the password with the MD5 or SHA-1 hash function before you test the web service. The encryption must be encoded in Base64. Use the resulting hashed value as the password for the web service.
You can test a protected web service with a digested password in the XML Input tab. To test a protected web service with a digested password, add the Password attribute and elements required in the UsernameToken element for digested passwords.
To test a protected web service:
  1. In the Web Services section for real-time web services, select the protected web service to run and click
    Try-It
    .
  2. In the Try-It application window, select the operation for the protected web service.
  3. To use the Form Input to test the web service operation, click the Form Input tab.
    In the SOAP header section, enter the user name and a plain text or hashed password.
    In the SOAP body section, enter the values for the parameters required by the protected web service.
    -or-
    To use the XML Input to test the web service operation, click the XML Input tab and update the UsernameToken element.
    To test a protected web service that uses a plain text or hashed password, replace the value
    [string]
    in the Username and Password child elements with a valid user name and password:
    <UsernameToken>     <Username>[string]</Username>     <Password>[string]</Password> </UsernameToken>
    To test a protected web service that uses a digested password, replace the value
    [string]
    in the Username element with a valid user name. Update the Password element and add Nonce and Created elements with the appropriate value:
    <UsernameToken>     <Username>[string]</Username>     <Password Type="PasswordDigest">[string]</Password>     <Nonce>[NonceValue]</Nonce>     <Created>[RequestCreationTimestamp]</Created> </UsernameToken>
    For more information about the UsernameToken element, see UsernameToken in the SOAP Request.
    In the SOAP body section, enter the values for the parameters required by the protected web service.
  4. Click Send.
    The Web Services Hub runs the protected web service operation and displays the SOAP message response on the console.
  5. Click the Close button of the web browser to exit the Try-It application window and return to the main page of the Web Services Hub Console.

0 COMMENTS

We’d like to hear from you!