How to map LDAP attribute with Pega Property [Pega 7.2.2]
Hi Team,
How to map my LDAP attributes(refer attached LDAP attributes) to Pega property
Search Filter
(sAMAccountName=%V)
User belongs to both SPX Users and ABC Users.
memberOf: CN=SPX Users,OU=Project Users,DC=abc,dc=com memberOf: CN=ABC Users,OU=Project Users,DC=abc,dc=com
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.
Hi Team,
How to map my LDAP attributes(refer attached LDAP attributes) to Pega property
Search Filter
(sAMAccountName=%V)
User belongs to both SPX Users and ABC Users.
memberOf: CN=SPX Users,OU=Project Users,DC=abc,dc=com memberOf: CN=ABC Users,OU=Project Users,DC=abc,dc=com
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.
EPAM Systems, Inc.
ES
Hi Kanneesh,
Thanks for posting on PSC,
Review links:-
- Video explaining details:- https://pdn.pega.com/node/1011711
- https://collaborate.pega.com/question/require-different-login-screens-standard-vs-ldap-url
- https://collaborate.pega.com/question/how-enable-ldap-authentication-pega-722
Review links provided in the above posts as well. Hope it helps you in implementation.
Kindly notify if it does, by marking this post as answered for larger Pega audience or do share the solution for two-way learning.
Regards,
Asif
Accenture Technology Solutions Pte Ltd
SG
Hi Asif,
Thanks for the reply.
I went through the video already before I post this question. I am repeating my question again.
I have attached the OrganizationalPerson_LDAP.txt and LDAP_Mapping.PNG files.
Just tell me which LDAP attribute has to be mapped to my
.pyOrganization
.pyOrgDivison
.pyOrgUnit
If you say "memberOf" attribute, then how do I do it. ?
memberOf: CN=SPX Users,OU=Project Users,DC=abc,dc=com
memberOf: CN=ABC Users,OU=Project Users,DC=abc,dc=com
We cannot add any other new attribute in LDAP now, as this is a legacy system.
EPAM Systems, Inc.
ES
Refer it as well:-
Pegasystems Inc.
IN
Hi Kaneesh,
It is not that you have to use O,OU,l attributes in mapping tab.
Mapping tab in authentication service rule is intended for mapping data from LDAP server attributes to Pega properties.
You can map any attributes to Pega properties but they should match(like single value attribute to single value property and value list attribute to value list property)
Whenever you want to map LDAP attributes to Pega, You might need to first see whether the required values like organisation/division/unit are already available in LDAP server.
If you don't already have them, ask LDAP team to create those in LDAP directory server.
EX: In Pega, if organisation name is pegaorg and division name is pegadiv and unit name is pegaunit.
Then First check in LDAP if the user has these values in any of the existing user attributes.
If yes, map those attributes to Pega properties.
If no, create them by creating new attributes to hold these values or set them to existing attributes in LDAP directory server and map the attributes.
Thank you,
Adithya
Accenture Technology Solutions Pte Ltd
SG
Hi Adithya,
Thanks for the reply.
I have attached the OrganizationalPerson_LDAP.txt and LDAP_Mapping.PNG files.
We cannot add any other new attribute in LDAP now, as this is a legacy system.
Just tell me which LDAP attribute has to be mapped to my
.pyOrganization
.pyOrgDivison
.pyOrgUnit
If you say "memberOf" attribute, then how do I do it. ?
memberOf: CN=SPX Users,OU=Project Users,DC=abc,dc=com
memberOf: CN=ABC Users,OU=Project Users,DC=abc,dc=com
Pegasystems Inc.
IN
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.
Conclusion:
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.
Accenture Technology Solutions Pte Ltd
SG
Hi Adithya,
Not sure if my question is misleading.
Refer my attachments, OrganizationalPerson_LDAP.txt and LDAP_Mapping.PNG files.
If you are given with this LDAP structure(which cannot be modified as this Legacy system), which attribute do you use the mapping for
.pyOrganization
.pyOrgDivison
.pyOrgUnit
User belongs to the following groups
1. SPX Users
2. ABC Users
"memberOf" is the only attribute which helps us in identifying it.
Hi Adithya,
Not sure if my question is misleading.
Refer my attachments, OrganizationalPerson_LDAP.txt and LDAP_Mapping.PNG files.
If you are given with this LDAP structure(which cannot be modified as this Legacy system), which attribute do you use the mapping for
.pyOrganization
.pyOrgDivison
.pyOrgUnit
User belongs to the following groups
1. SPX Users
2. ABC Users
"memberOf" is the only attribute which helps us in identifying it.
memberOf: CN=SPX Users,OU=Project Users,DC=abc,dc=com
memberOf: CN=ABC Users,OU=Project Users,DC=abc,dc=com
Is there a way to split this "memberOf" attribute and map to Pega property ?
Pegasystems Inc.
IN
Hi Kanneesh,
We can't split the attribute and map it to Pega properties.
If you give cn in mapping then it will take the value that is mapped to cn which is firstname in your case.
Can you tell me what are all Pega properties that you are trying to map and what values are expected for these properties?
Accenture Technology Solutions Pte Ltd
SG
Hi Adithya,
Thanks for the response.
I just need to login successfully into Pega with this LDAP.
My Organization or Division or Organization Unit should be
1. SPX Users
2. ABC Users
PS : I cannot change or add any attribute into OrganizationalPerson_LDAP.txt
Pegasystems Inc.
IN
Yes Kanneesh.
Your org/div/unit/pyseridnetifier values should already be present in the LDAP directory server so you can verify them to grant access to Pega.