AnsweredAssumed Answered

Ldap Account DN Suffix

Question asked by Sunita Bhat on May 20, 2019
Latest reply on May 21, 2019 by Boris Lekumovich

Like • Show 0 Likes0
Comment • 1

Hi,

I am setting up an Open Ldap AFX connector. The structure of my LDAP instance is like the following:

o=mydomain.com

ou=ams,o=mydomain.com

ou=MX,ou=ams,o=mydomain.com

ou=US,ou=ams,o=mydomain.com

ou=AR,ou=ams,o=mydomain.com

ou=CN,ou=ams,o=mydomain.com

ou=BR,ou=ams,o=mydomain.com

My need is to create Accounts under each of these country codes based on User's region attribute. In the connector settings, I have to provide an Account DN suffix. If I give the suffix as "ou=MX,ou=ams,o=mydomain.com", then how can I create accounts under the other country codes. This is a required field so can't keep it empty either.

Has any one worked a similar use case?

Rgds

Sunita

Boris Lekumovich

May 21, 2019 12:36 AM

Correct Answer

One approach is to use AFX_OU_Picker

Another approach is to use AFXCUSTOM prefix variable.

Search for AFXCUSTOM in RSA Link for additional information.

From product help section:

Any JOB-level user variable defined in a workflow that has a name starting with AFXCUSTOM_ will be used to replace variables in all change items processed in that workflow. Any JOB-level variables defined in a workflow with a name starting with AFXUSERCUSTOM_<USERID>_, where <USERID> is a number, will be used to replace variables in change items involving the user with that userid number (i.e. if it's AFXUSERCUSTOM_14_SOMETHING then it will be used to replace variables in change items where the user that's used to provide values for ${User.*} variables has an ID of 14.

Note: The “has an ID of 14" above means this is the ID of the user in the master enterprise user table.

Everything in the variable name after the initial tokens is converted to dot notation, and that's what's used for variable substitution. Therefore:

    The value of a workflow JOB-level user variable with the name AFXCUSTOM_SECURITY_LEVEL will be used to substitute for ${Security.Level}.
    The value of a workflow JOB-level user variable with the name AFXCUSTOM_CUSTOM_SECURITY_LEVEL will be used to substitute for ${Custom.Security.Level}.
    The value of a workflow JOB-level user variable with the name AFXCUSTOM_USER_NAME will be used to substitute for ${User.Name}.
    The value of a workflow JOB-level user variable with the name AFXUSERCUSTOM_14_USER_NAME will be used to substitute for ${User.Name}, but only in CIs involving the user with ID 14 in the MasterEnterpriseUser table

See the reply in context

No one else had this question

Outcomes

Any JOB-level user variable defined in a workflow that has a name starting with AFXCUSTOM_ will be used to replace variables in all change items processed in that workflow. Any JOB-level variables defined in a workflow with a name starting with AFXUSERCUSTOM_<USERID>_, where <USERID> is a number, will be used to replace variables in change items involving the user with that userid number (i.e. if it's AFXUSERCUSTOM_14_SOMETHING then it will be used to replace variables in change items where the user that's used to provide values for ${User.*} variables has an ID of 14. Note: The “has an ID of 14" above means this is the ID of the user in the master enterprise user table. Everything in the variable name after the initial tokens is converted to dot notation, and that's what's used for variable substitution. Therefore: The value of a workflow JOB-level user variable with the name AFXCUSTOM_SECURITY_LEVEL will be used to substitute for ${Security.Level}. The value of a workflow JOB-level user variable with the name AFXCUSTOM_CUSTOM_SECURITY_LEVEL will be used to substitute for ${Custom.Security.Level}. The value of a workflow JOB-level user variable with the name AFXCUSTOM_USER_NAME will be used to substitute for ${User.Name}. The value of a workflow JOB-level user variable with the name AFXUSERCUSTOM_14_USER_NAME will be used to substitute for ${User.Name}, but only in CIs involving the user with ID 14 in the MasterEnterpriseUser table

Ldap Account DN Suffix

Outcomes

Related Content

Recommended Content