Akash,
A lot of what you need is derived from LDAP itself. Essentially the only thing you tell CAPM to do is where and how to search the LDAP system. Below is a really basic example that you may be able to use to start with. The {0} and {1} in the beginning are variables that reference what the person logging in types. In this case, when the user logging in to CAPC enters their username it is mapped to the 0 variable and same thing for the password but it is mapped to the 1 variable. You can see this used again for the Search String further down, this is trying to match the LDAP field, sAMAccountName to the username that is entered in CAPC.
One last tip, in SsoConfig, make these changes under Remote Value and not Local Override.
SSO Configuration/CA Performance Center/LDAP Authentication:
Connection User: {0}
Connection Password: {1}
Search Domain: ldap://ldapHostname:389/DC=sondaso,DC=com
Search String: (sAMAccountName={0})
Search Scope: Subtree
User Bind: Disabled
Encryption: DIGEST-MD5
Account User: {sAMAccountName}
Account User Default Clone: user
Group:
Krb5ConfigFile:
Status: Enabled
Timeout: 10000