Yes. As a general rule we try to keep the ldap smell out of the api exposed to the caller.
Of course this is a good idea but the User object anways smells like inetOrgPerson :) My thoughts were more along the lines that you extend the user entity with your custom attributes. Thats perfect. But there are several question * How can i get a list of all Users in Fortress API ? * How can i get a User by a Criteria ? * How will Fortress handle to give me back my specific User class with the populated extra Fields. Remember i need to manipulate the User later and i need access to my extra Fields. Just some thoughts :) Am 18.10.2016 um 17:54 schrieb Shawn McKinney: On Oct 18, 2016, at 9:47 AM, Patrick Brunmayr <[email protected]><mailto:[email protected]> wrote: The questions is more where to make these changes! Is it useful to have some more generic methods on the User class like * getObjectClass * getAuxClasses * setAuxClasses * hasAuxClass * getAttributes * getAttribute * setAttribute * hasAttribute Is this to LDAP specific ? Yes. As a general rule we try to keep the ldap smell out of the api exposed to the caller. My thoughts were more along the lines that you extend the user entity with your custom attributes. i.e. public class MyUser extends User { … } On Oct 18, 2016, at 9:47 AM, Patrick Brunmayr <[email protected]><mailto:[email protected]> wrote: Or another approach would be to have some kind of Eventlistener to react on the add and update methods. There you get an LDAP connection and the user object as parameters. You can then implement your custom logic there. More generic is to have access to the methods above and the add and update methods must check the extra aux classes and attributes and reflect them back into LDAP. Would be nice to have some kinde of configuration which extra classes to handle in the web UI. Then there should be a the possibility to edit there attributes if its not much effort. Yeah listener or callback that is registered. i.e. myUserHandler (LDAPEntry le, User ue) then you simply add the attributes that are needed by upcasting to your extended user object grabbing the attributes, adding to entry, and returning control to main method. The web UI is a separate matter. Doable, but not as simple. Care would have to be taken to make it easy to upgrade. Shawn LINZ AG für Energie, Telekommunikation, Verkehr und Kommunale Dienste A-4021 Linz, Wiener Straße 151, Postfach 1300, Tel. +43/732/3400-0, E-Mail: [email protected]
