Thinking about a LDAP directory, you have to stick to a predefined schema, so you cannot store any kind of attributes.
We need to decide where the attribute filtering will occur: either in the IUserDirectory client, or in the IUserDirectory implementation. > it'd be simpler to provide a method that returns a dictionary of the > known attributes for a single user. This would mean that the filtering has to be done in the LDAP plugin itself: LDAP directories may have hundreds of attributes per user entry, and only a few numbers need to be retrieved. I'm ok with this approach. > Is "get_supported_attributes" necessary? A LDAP-based backend may not accept all the attributes: there's gonna be a way to tell the IUserDirectory that some attributes can be stored (for example: name, address), some cannot (for example: session id). How do we handle this ? What would be the exact list of stored parameters in the IUserDirectory, btw ? -- Manu _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
