I think there needs to be something like a "UserFactory" that can be set 
globally in the system. This factory creates

the concrete User instance whenever its needed and returns it back to Fortress.  And 
secondly there must be some kind of "Serializer" which

maps the LDAP node to the User instance. One would subclass this serializer and 
call the parent method to

the things that are already working. After the parent method you could then 
easily map the LDAP things to your

concrete instance. Just guessing but something like this.


We should also considering the "extension" posibility to other things like 
Groups or Roles. This would open great

flexibility in the system. For instance why not extending the Group with some 
additional info :)

Thx

Am 19.10.2016 um 15:28 schrieb Shawn McKinney:




On Oct 19, 2016, at 1:40 AM, Patrick Brunmayr 
<[email protected]><mailto:[email protected]> wrote:

Of course this is a good idea but the User object anways smells like 
inetOrgPerson :)




You’ve got me there.  :-)




On Oct 19, 2016, at 1:40 AM, Patrick Brunmayr 
<[email protected]><mailto:[email protected]> wrote:

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 ?




Checkout the reviewmgr:
http://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/ReviewMgr.html

To pull back all users:

List<User> findUsers(new User(") );

or there are a few other searches you can do, by userid, role, org unit.




On Oct 19, 2016, at 1:40 AM, Patrick Brunmayr 
<[email protected]><mailto:[email protected]> wrote:

*   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.



That’s the question that begs asking.  I can again point to the idea of a 
callback module that gets inserted into the flow or perhaps Chris Pike’s work 
using the querybuilder will help us here.

The good news is you’re not the only one asking for this and it’s doable for a 
few methods, i.e. user add, update, search.

Shawn

--
Patrick Brunmayr
LINZ AG TELEKOM
Infrastruktur & Netzwerktechnik
Internet Services

Die LINZ AG TELEKOM ist ein Geschäftsbereich der LINZ STROM GmbH
für Energieerzeugung, -handel, -dienstleistungen und Telekommunikation.

4021 Linz,  Wiener Straße 151, Austria
Tel.:        +43(0)732/3400-5639
Fax:        +43(0)732/3400-155639
E-Mail:    [email protected]<mailto:[email protected]>
Internet:  www.linzag-telekom.at<http://www.linzag-telekom.at>

FN 199533 g des Landesgerichtes Linz
Zertifiziert nach:
EN ISO   9001 Qualitätsmanagement (QM)
OHSAS 18001 Arbeitsschutzmanagementsystem
ISO/IEC 27001 Informationssicherheits-Managementsystem (ISMS)




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]


Reply via email to