So now what Organization , Division and Organization Unit to be created in Pega before I login ?
and Which LDAP attribute I must use to map with Pega property name to make successful login ? [There is no "o", "ou" or "I" attribute in the LDAP, refer the attached OrganizationalPerson_LDAP.txt file]
Because what I understand from other post is Org structure with Division and Org Unit must be created and the LDAP attribute must match with the mapped Organization, Division and Organization Unit to make successful login.
Any pointer on Mapping LDAP attributes to Pega Properties is much appreciated.
You can map any attribute to any properties in Pega and modify the Authentication activity to change the logic or create your own activity so you use only available attributes of LDAP.
With the default activity(Authentication LDAP), you have to store the values of Organization/Division/Unit/UserIdentifier values in LDAP directory and map them to Pega properties so Pega knows these users/user attributes exist in LDAP and authenticates the user.
If you do not have the Pega related property values in LDAP, Pega can't be able to check the LDAP for the existence of the user.
Whatever attribute you map, it should have expected values.
If you are mapping any attribute to pyOrganization, then that attribute must have the Pega Organization name.