Documentation's navigation

The documentation for versions 2.21 and older can be found here.


On this page


How many field types exist?

Currently, thirteen field types exist.

Those field types are:


Text input

Multiline text

Select

Multi select

Cascade select

Date input (old)

Date input (new)


User select

Phone number

Instant Messenger

Language select

Country select

Retrieved from LDAP

Dependent field




Why should I use profile field type Retrieved from LDAP?

ONLY AVAILABLE PRIOR TO VERSION 2.25

Warning

This field type is marked as deprecated as of version 2.25 of Linchpin User Profiles.

Please don't use it to create new profile fields. Instead, use one of the other profile fields and configure the data source to be LDAP.

If you have existing profile fields of this type, please change them to another profile field type.

In a future update, this deprecated field type will be deleted. Any fields still existing with this field type will be turned into text input fields at that point.


Always retrieves the profile information from your LDAP resource.

Users will never be able to edit this profile field, even if the user can't be found in the LDAP resource.


The LDAP connection is strictly "read-only". Never will any data be written back to your LDAP resource.

Special configuration


In the Source section, select LDAP server from the drop-down menu. In the text field, enter the name of the LDAP attribute where the profile information is stored.

The value of this profile field will be retrieved from this LDAP attribute for each profile update.

Field type vs. LDAP attribute

If you want your LDAP resource to deliver profile information, you have two options that affect the possibility to edit fields.


Option 1: Define any field type (like text field or select field) and add an additional LDAP attribute.

If you select any other field type and still select LDAP server as data source, the information will be retrieved from your LDAP resource.

But if the user can't be found in the LDAP resource, the user will be able to edit the field by themselves.


Option 2: Define your field as "Retrieved from LDAP"

This option retrieves the data only from your LDAP resource.


Users will never be able to edit this profile field, even if the user can't be found in the LDAP resource.



Related topic: CUP - Alternative LDAP connection





Link to this page: https://seibert.biz/fieldtypeldap


This page was last edited on 10/02/2023.