CA SiteMinder requires a certificate to complete signing the WS-Token. CA SiteMinder signs the WS-Token and sends it to SharePoint. To create a certificate for the WS-Token, import an existing certificate that contains both a private and a public key.
This certificate is often in the Public-Key Cryptography Standards #12 (PKCS) format. In the following example, the password protects the PKCS#12 file.
Note: On Windows operating environments, a .pfx file is equivalent to a .p12 file.
Follow these steps:
smkeytool -addPrivKey -alias alias_name -keycertfile certificate_file_name.p12 -password certificate_private_key_password
Note: If you want to define aliases for your certificates, the name of the first alias must be defaultenterpriseprivatekey. Subsequent aliases support any name you want. For more information about the smkeytool command, see the Policy Server Configuration Guide.
SiteMinder imports the certificate.
smkeytool -export -alias alias_name -outfile exported_certificate_file_name.cer -type cert
The trust certificate file that SharePoint requires is created.
Note: The Powershell script created by the SharePoint connection wizard requires the paths to the following certificates on your SharePoint central administration server:
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |