14.02.2014 Views

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

ldapv3.pdf 7947KB Apr 17 2013 11:30:42 AM - mirror omadata

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

dn Mapping<br />

CREATE SEQUENCE ldap_entries_id_seq;<br />

CREATE TABLE ldap_entries<br />

(<br />

id int4 NOT NULL PRIMARY KEY<br />

DEFAULT nextval('ldap_entries_id_seq'),<br />

dn varchar(255) NOT NULL UNIQUE,<br />

-- dn_ru varchar(255),<br />

oc_map_id int4 NOT NULL,<br />

parent int NOT NULL,<br />

keyval int NOT NULL,<br />

UNIQUE (oc_map_id,keyval),<br />

FOREIGN KEY (oc_map_id) REFERENCES ldap_oc_mappings (id)<br />

);<br />

ldap_entries<br />

The purpose of ldap_entries is to map a dn to a database key, the last step<br />

in transforming the LDAP data-model to the SQL relational model.<br />

The virtual dn<br />

The objectclass<br />

id from<br />

ldap_oc_mappings<br />

The object id of the parent object,<br />

used to create the heirarchical<br />

structure required by the LDAP<br />

data-model. The root object within<br />

the database has a parent of 0.<br />

The integer key used to map this virtual dn<br />

to the actual content of the relational database.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!