...
LDAPPCNG provisions group and membership information contained in the Groups Registry to an LDAP directory service.
...
For example, LDAPPCNG ships with an LDAP provider using the vt-ldap distribution.
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | ldappcng.xml | xml |
|---|
|
<target id="ldap" provider="ldap-provider" /> |
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | ldappc-services.xml | xml |
|---|
|
<Service id="ldap-provider" xsi:type="ldappc:LdapPoolProvider" ldapPoolId="ldapPool">
<ConfigurationResource file="/ldappc-ldap.xml" xsi:type="resource:ClasspathResource" />
</Service> |
...
For example, an object returned from a target which has an attribute named "objectclass" with value "groupOfNames" will be identified as a "group" object.
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | ldappc-services.xmlxml |
|---|
|
<object id="group">
<identifier ref="group-dn" baseId="ou=groups,dc=example,dc=edu">
<identifyingAttribute name="objectClass" value="groupOfNames" />
</identifier> |
...
The values of the "members-jdbc" and "members-g:gsa" attributes are passed to the attribute resolver to determine their identifiers.
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | ldappcng.xmlxml |
|---|
|
<references name="member" emptyValue="" >
<reference ref="members-jdbc" toObject="member" />
<reference ref="members-g:gsa" toObject="group" />
</references> |
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | ldappc-resolver.xmlxml |
|---|
|
<resolver:AttributeDefinition id="members-jdbc" xsi:type="grouper:Member" sourceAttributeID="members">
<resolver:Dependency ref="GroupDataConnector" />
<grouper:Attribute id="id" source="jdbc" />
</resolver:AttributeDefinition>
<resolver:AttributeDefinition id="members-g:gsa" xsi:type="grouper:Member" sourceAttributeID="members">
<resolver:Dependency ref="GroupDataConnector" />
<grouper:Attribute id="name" source="g:gsa" />
</resolver:AttributeDefinition> |
...