> On Sep 10, 2024, at 9:05 AM, Brian Demers <[email protected]> wrote:
>
> IMHO, one of the issues in making a _generic_ solution like this is (IMHO)
> everyone does LDAP a little differently (different schemas, extensions,
> structure, etc)
> But this could start out as a simple example, supporting a single schema,
> and then grow into a more robust solution.
Hello,
I’ve been thinking about this too. One that can map from a generic taxonomy
exposed to the client to a more specific schema on the backend.
Client < — > scimple -> generic user plug-in < — > ldap
The plug-in would include
- ldapv3 connection pooling
- configuration
- schema mapping
Would the config use dictionaries to do this mapping?
name: user
objects: inetOrgPerson, myOrgPerson
string: uid
string: description
base64: userPassword
string: ou
...
game: group
objects: groupOf...
member: mymembers
...
Since scimple’s java so would be the connector.
Anyway, these have been percolating for a while. Would like to find some time
to start implementing.
Cheers
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
