[Design of JBoss Portal] - missing groups for role assignments
by bvogt
Hi,
I got the impression, that the portal is missing an interesting portal
feature: adding portal functionality to groups of users.
I've thought a while about this, looked at the svn-sources and believe it's not
contained within the v2.6 LDAP solution.
Therefore I would like to provide this functionality based on the 2.4 branch,
but need some information about the v2.6 LDAP solution design in order to take
it into consideration for my improvements.
Some background information, currently we have:
1. Portal-users and -groups are stored in an LDAP tree, which is asynchronously
changed by an entitlement system
2. Portal functionality (pages) are assigned to (LDAP-)groups
3. Users get all portal roles of all groups they are member of
This leads to an automatic entitlement for portal users with no effort at the
portal side.
My solution could be:
1. Users and roles are still stored in the database
2. Introducing new DB objects: jbp_groups, jbp_group_membership, jbp_group_roles
3. Introducing a new RoleModule derived from the existing one, which provides a
method like: Set getRolesByGroupMembership(User user);
4. Introducing a new LoginModule which uses the new RoleModule to do after
successful login:
- Remove all roles assigned to the user
- add all roles assigned to groups where the user is member of to the user
Would this be useful considering the portal design, or not?
Burkhard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975604#3975604
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975604
19 years, 3 months
[Design of JBoss jBPM] - Re: console layout
by david.lloyd@jboss.com
"tom.baeyens(a)jboss.com" wrote : i think that one page will be simpler to accomodate all the different possible combinations that people could query for.
Maybe, but again the end result is more complex (and slower) queries.
"tom.baeyens(a)jboss.com" wrote : with separate links, you'll get an exponential number of separate pages to accomodate for all the different combinations of search criteria.
You get that with radio buttons too. The only difference is that you're using javascript to generate all the different combinations. You still have to handle all the criteria on the server side. Also, the problem stands that prepopulating the search form may not be sufficient to uniquely select the item in question.
"tom.baeyens(a)jboss.com" wrote : i also think that the complete page will not be that big.
|
| i also think that a single page will be simpler for users as they will recognize that page and not get lost in a tree of search pages.
That is true, but it might be made less confusing by designing the UI such that the user is never really "lost". I think that clear navigation controls can help a lot with this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975545#3975545
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975545
19 years, 3 months
[Design of Kosmos] - Re: Kosmos portlet page is empty
by trp
When I click on Kosmos in portal I have been presented a page saying
HTTP Status 500 -
--------------------------------------------------------------------------------
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Exception in JSP: /phalanx/index.jsp:92
89: <%
90: if (!leftIsEmpty) {
91: %>
92: <basic:forEachWindowInRegion region="<%= left %>">
93: <%@ include file="window.jsp" %>
94: </basic:forEachWindowInRegion>
95: <% } %>
Stacktrace:
org.jboss.portal.server.servlet.PortalServlet.doGet(PortalServlet.java:227)
javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.apache.jasper.JasperException: Exception in JSP: /phalanx/index.jsp:92
89: <%
90: if (!leftIsEmpty) {
91: %>
92: <basic:forEachWindowInRegion region="<%= left %>">
93: <%@ include file="window.jsp" %>
94: </basic:forEachWindowInRegion>
95: <% } %>
Please help me to solve it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975534#3975534
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975534
19 years, 3 months