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

UsernameToken in the SOAP Request

UsernameToken in the SOAP Request

When you build a client application based on the WSDL generated by the Web Services Hub, the request object contains the UsernameToken element in the header by default.
The UsernameToken element in the SOAP request can have one of the following password security:
  • Plain text password.
    Includes a password in plain text.
  • Hashed password.
    Includes an encrypted password hashed using the MD5 or SHA-1 hash function.
  • Digested password.
    Includes an encrypted password that is hashed with a nonce value and a timestamp.
Include the user password in the Password element of the UsernameToken.
The Password element has a Type attribute to indicate the type of password security used. If the Type attribute is omitted, the password type defaults to
PasswordText
.
If the Informatica domain uses Kerberos network authentication, you cannot use hashed or digested passwords in the SOAP request.

0 COMMENTS

We’d like to hear from you!