Date: Fri, 29 Mar 2024 08:43:20 +0000 (UTC) Message-ID: <278085677.7719.1711701800534@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7718_88580751.1711701800533" ------=_Part_7718_88580751.1711701800533 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
GROUPER: About FAQ Software Documentation &= nbsp; Contribute WG Contact |
---|
The existing LDAP Provisioning Connector has LDAP knowledge built in at = almost every level. This is not surprising considering that it was written = to satisfy an RFQ that only had LDAP in mind as a target. KU's Relational D= atabase Provisioning Connector is better, but has too much knowledge built = in at a low level in the synchronization code about what relational databas= es might look like.
Here is a diagram of the current Ldappc classes (with some classes ignored for clarity).&nb= sp;
GROUPER: About FAQ Software Documentation &= nbsp; Contribute WG Contact |
---|