LDAP connector - USER_ATTRIBUTE mapping

[GauravJain]

Hi

is it possible to set a static string value for a user customproperty in the USER_ATTRIBUTE mapping configuration in LDAP connector?

I require this to setup User Account Correlation Rule at endpoint level.

If above is not possible then can we go for pre-processor queries in MODIFYUSERDATAJSON where we can update a customproperty with some static value for each user record?

Please do suggest if there is another better approach to implement it.

Regards

Gaurav

[rushikeshvartak]

Can you explain use case with example

[GauravJain]

Hi @rushikeshvartak Thanks for your revert.

I want to map a user identity whose username is "user123" to an LDAP account having naming convention as "abc-{username}-as" OR "bcd-{username}-aq" OR few more like this.

To do this,

1st approach could be to populate these static string values "abc" / "bcd" / "as" / "aq" etc. in customproperty in USER_ATTRIBUTE mapping while importing users like CUSTOMPROPERTY1:: "#CONST#abc#String" so that each user will have these static values. Is it feasible?

2nd approach is to store these static string values in user's customproperty like customproperty1="abc-", customproperty2="-as", customproperty3="bcd-", customproperty4="-aq" and many more in PREPROCESSQUERIES in MODIFYUSERDATAJSON. 

First, please suggest what is feasible from above approaches and is there any better approach to achieve this task?

secondly, In both the above approaches there could still be an issue if we have to store like 20-30 such static values in customproperties in User object. Considering we have a limited number of custom properties available in Users object, i am sure we may not be able to scale this solution in future if we have more such account naming conventions.

I have tried to explain it but in case you have any further questions, please write back.

Regards

Gaurav

[rushikeshvartak]

• CONST is not supported in LDAP connector.
• You can map this accounts one time to user using import sheet

[GauravJain]

This is not a one time exercise as the new accounts can be directly created in AD as well. So, i can use Enhance query here but the problem we may face in future is limitation of custom properties on User object to store all such static values for each user record. 

[rushikeshvartak]

Use custom property with multiple values 

abc###pqr###zyaj

[GauravJain]

By mistake i typed "Enhance Query" option but i don't think we can use it for this task.

If i use this format "abc###pqr###zyaj" then how do i map it in correlation rules? i can only define initial characters in rule so if i have to extract "pqr", how do i configure it in correlation rules?

[naveenss]

Hi @GauravJain is this static value same for all users? If yes, you can use inline preprocessor to compute the compete value "abc-{username}-aq" or whatever the format you need and store it in a custom property. Later you can use this customproperty for correlating the account. 

[GauravJain · Accepted solution]

thanks Naveen. i resolved this using Advance config in correlation rules. Like this

users.username = accounts.name#accounts.name LIKE concat('abc-', users.username, '-__')