Skip to Content.
Sympa Menu

grouper-dev - ldappc-ng comparing provisioned identifiers ?

Subject: Grouper Developers Forum

List archive

ldappc-ng comparing provisioned identifiers ?

Chronological Thread 
  • From: Tom Zeller <>
  • To: Grouper Dev <>
  • Subject: ldappc-ng comparing provisioned identifiers ?
  • Date: Fri, 19 Feb 2010 09:54:56 -0600
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=HekaEmrDNV8cDFMSoXdy95p8VgJ5p0N3coFXZKlK2tVXFBxwJV1Ny7YW9MDP4eahaM zbg61lHTUy2r0MKmRT7s6xEnq4rjFAwMCJ3BkJln4U9PX3Rq34wNaYL4u3EVp24KtzMc RCAnzXobz/cUWPneFNee5jamXFGosclM6gaKk=

I'm looking for feedback regarding two styles of comparing provisioned
identifiers, what I'll call "exact-match" and "pluggable".

By exact-match I mean comparing identifiers as case-sensitive strings,
e.g. idA.equals(idB).

By pluggable I mean that identifiers might be massaged before
comparison, for example, making them case-insensitive

For ldap DNs, a pluggable comparison might involve case-insensitivity,
escaping, and normalizing whitespace.

If ldappc-ng compares ldap DNs as exact-matches, then the (software)
connector to an ldap server would need to always normalize DNs upon
receiving requests and sending responses.

If ldappc-ng compares ldap DNs pluggably, then the (software)
connector to an ldap server could return whatever DN it receives from
the ldap server, and it would be up to ldappc-ng to normalize.

I'm leaning towards exact-match, which leaves the details of
identifier normalization to the connector. In other words, the
connector code contains all of the target specific details.

Feedback ? Does this make sense ?


Archive powered by MHonArc 2.6.16.

Top of Page