[jboss-dev-forums] [Design of JBoss Portal] - Re: LDAP Support expectations

[bvogt]

Sorry for being so short in my comment.

May be I do not see the complete picture, but I guess that using LDAP means authentication
against the LDAP server too? If this is not the case, LDAP would be an option for us
otherwise there are two points for me to be considerd:

1. where to store user/role data
--------------------------------
The decision where to store the user/role data depends on external critera like:
- amount of expected data objects
- availability of additional resources (Memory, CPUs, Servers)
If there are a few thousands of users expected, the database solution might be
the way to choose.
On the other hand the LDAP based solution requires at least a service on the 
portal server (if CPUs and amount of memory permits this).

We think, that for our use case the dabase solution is enough for the current
requirements.

2. how to group portal functionality
------------------------------------
With 2.6 a new let's say 'grouping feature' is introduced by means of the
MembershipModule. For LDAP usage the is intended to be implemented, but (as I can see
right now) for database not.

I guess you intend the 'GroupOfNames' LDAP class to reflect the group memberships of
users? A counterpart in the database is missing. 

In order to have the portal admin decide which way to choose the database part should
be extended in an appropriate way.

Burkhard

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981679#3981679

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981679