Show Table of Contents
9.14. LDAP Connector Update Capabilities
The LDAP connector also provides an update capability. However, additional modeling requirements are imposed beyond those required for read-only access. Here is a list of these additional requirements:
- Supports Update table property - to enable updates, each source model table must have this property set to 'true';
- Updateable column property - to enable updates, each column in the source model table must have this property set to 'true';
- You also need these additional columns:
- DN - for all update types (INSERT, UPDATE, and DELETE), the distinguished name must be modeled as a column, setting the name in source to dn. For UPDATE and DELETE capability, the DN must be specified in the criteria clause while for INSERT, the DN must be one of the column values to be set.
- objectClass - for INSERT, the objectclass must be modelled as a column, setting the name in source to objectClass. It must also be one of the column values to be set.
- additional - each entry defined in the LDAP directory’s schema may also have one or more additional required columns. This is dependent on the LDAP server implementatation so consult the LDAP documentation accordingly.
Here are some sample queries:
SELECT * FROM LdapModel.People
INSERT INTO LdapModel.People (dn, sn,
objectclass, Name) VALUES
('cn=JoeYoung,ou=people,dc=example,dc=org','Young','person',
'Joe Young')
UPDATE LdapModel.People SET PhoneNumber='(314) 299-2999' WHERE DN='cn=JoeYoung,ou=people,dc=example,dc=org'
DELETE FROM LdapModel.People WHERE DN='cn=JoeYoung,ou=people,dc=example,dc=org'

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.