CA SDM Web Services performs the user authentication by locating the policy through the plain text policy code, retrieving the policy holder’s public key associated with the policy, decrypting the encrypted policy code, matching the decrypted content with the policy code, and finally, opening a session with a back-end server. The plain text session ID (SID) is returned and can be used for subsequent method invocations. Only the policyholder holds the private key that matches the policy’s associated public key stored in CA SDM.
All subsequent web services calls must include the returned session ID (SID). The Proxy contact specified in the policy is responsible for all web services activities initiated in this session. All function group security and data partition is enforced for the proxy contact.
Important! The Encrypted_Policy parameter should be in the BASE64 text format. The user application must perform proper conversion from the binary format.
Policy is a required field. When you define it, use plain text policy code as defined in a policy. Encrypted_Policy (the digital signature of the policy code encrypted with the policy holder’s private key) is required. When you define Encrypted_Policy, use the algorithm SHA1 with RSA to obtain the digital signature.
| Copyright © 2012 CA. All rights reserved. |
|