Previous Topic: Modify LDAP Values with Conversion ExpressionsNext Topic: Section Syntax


Conversion Expression Syntax

Conversion expressions for imported LDAP values can comprise one or more sections. For example:

/al <attribute><[section1][section2][section3]>

where each [section] represents an element in the final CA DataMinder attribute value.

For example, in the above expression, the sections may resolve like this for a CA DataMinder user, Lynda Steel:

[section1]

Resolves to \o=Unipraxis

[section2]

Resolves to \ou=Paris

[section3]

Resolves to \cn=Lynda.Steel

Example Conversion Expression

In a fictitious LDAP directory for Unipraxis, values for the office attribute may have a ‘UX-’ prefix, such as ‘UX‑Boston’ and ‘UX‑New York’. The example conversion expression below strips out the prefix in the resulting CA DataMinder user groups (that is, ‘Boston and ‘New York)’:

/al office[if"UX-"["???{%untilEnd%}"] else["{?%untilEnd%}"]]

Separators between Sections

You cannot add literal separators between sections. Instead, you must add a custom ‘separator expression’ to insert the required character between sections. The example expression below inserts a single semicolon:

["zzzz",default=;]

Note: This method relies on the specified search text (in this case "zzzz") not being found; the expression then inserts the ‘default’ text (in this case, a semicolon).

To insert a backslash between sections, a modification is needed. This is because backslash characters have a special meaning in these conversion expressions. To insert a literal backslash, use this expression:

["zzzz",default=\\\\]

More information:

Section Syntax