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

Digested Password

Digested Password

The UsernameToken element includes the following child elements:
  • Username element.
    Contains a user name that can be found in the PowerCenter Native security domain.
  • Password element.
    Contains a digested password. The password is the value generated from hashing the password concatenated with the nonce value of the Nonce element and the timestamp in the Created element. The password must be hashed with the SHA-1 hash function and encoded to Base64.
    For digested password security, the Type attribute of the Password element must be set to
    PasswordDigest
    .
  • Nonce element.
    Contains a nonce value, which is a random value that can be used only once.
  • Created element.
    Contains a timestamp value that indicates the time when the request was created. The timestamp uses the UTC format,
    yyyy-MM-dd'T'HH:mm:ss.SSS'Z'.
    For example:
    2008-08-11T18:06:32.425Z.
The nonce value you include in a SOAP request can be used only once. By default, it is valid for 300 seconds (five minutes) after the time that the request is created, as indicated by the value in the Created element. The client application must send the request within the time that the nonce value is valid. For example, the Created value indicates that the request was created at 10:00 a.m. The request is valid from 10:00 a.m. to 10:05 a.m. If the client application sends the request to the Web Services Hub before 10:00 a.m. or after 10:05 a.m., then the request and the nonce value are not valid and the request will fail.
The digested password uses the standard OASIS password digest algorithm:
Password_Digest = Base64 ( SHA-1 ( nonce + created + password ) )
You can use any tool to generate the nonce value, timestamp, and the digested password.
The following code shows an example of the security header for a request that uses a digested password:
<soapenv:Header>     <!-- UsernameTokens -->     <inf:Security>         <UsernameToken>             <Username>Administrator</Username>             <Password Type="PasswordDigest"> Xty5lCAf5SVO0AY3OtsYq7nv/DI=</Password>             <Nonce>KjsaeiuDFKJEwkr4332rL=</Nonce>             <Created>2008-08-12T01:11:47.013Z</Created>         </UsernameToken>     </inf:Security> </soapenv:Header>

0 COMMENTS

We’d like to hear from you!