June 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1783) Improve UIPage to make it easier for extending in other extension project

by Vu Viet Phuong (JIRA)

Improve UIPage to make it easier for extending in other extension project ------------------------------------------------------------------------- Key: GTNPORTAL-1783 URL: https://issues.jboss.org/browse/GTNPORTAL-1783 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong When we need to write a new UIPage in other project , for example UIDesktopPage extends UIPage, but in Gatein, it's hard to create a new instance of UIDesktopPage. We should add to UIPage a static map that help us to add more Class object in UIDesktopPage --> this map will help us to retrieve the actual UIDesktopPage class in Gatein project protected static Map<String, Class<? extends UIPage>> realClass; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1762) Wrong configuration to setup gatein with CAS server

by houssem njah (JIRA)

Wrong configuration to setup gatein with CAS server --------------------------------------------------- Key: GTNPORTAL-1762 URL: https://issues.jboss.org/browse/GTNPORTAL-1762 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.1.0-GA Environment: tomcat pacakge Reporter: houssem njah Assignee: Luc Texier Priority: Critical Hi, when i want to setup gatein with cas server, i follow the documentation found here: http://docs.jboss.com/gatein/portal/3.1.0-FINAL/reference-guide/en-US/htm... there was an error when we edit the jass.conf: in documentation, we ask to edit this file to be like this: org.gatein.sso.agent.login.SSOLoginModule required org.exoplatform.services.security.j2ee.TomcatLoginModule required portalContainerName=portal realmName=gatein-domain but it doesn't work. i change this file to: org.gatein.sso.agent.login.SSOLoginModule required; org.exoplatform.services.security.j2ee.TomcatLoginModule required; and the authentication work. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1734) Edit CAS section in reference guide document

by Khoi Nguyen (JIRA)

Edit CAS section in reference guide document -------------------------------------------- Key: GTNPORTAL-1734 URL: https://issues.jboss.org/browse/GTNPORTAL-1734 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Khoi Nguyen Fix For: 3.2.0-GA In section http://docs.jboss.com/gatein/portal/3.1.0-FINAL/reference-guide/en-US/htm... , we guide to edit the jaas.conf file in Tomcat server seems incorrect. We must change to org.gatein.sso.agent.login.SSOLoginModule required; org.exoplatform.services.security.j2ee.TomcatLoginModule required portalContainerName=portal realmName=gatein-domain; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1558) Have an option to set the default value for "Show Info Bar" and make it disable by default

by Thomas Heute (JIRA)

Have an option to set the default value for "Show Info Bar" and make it disable by default ------------------------------------------------------------------------------------------ Key: GTNPORTAL-1558 URL: https://jira.jboss.org/browse/GTNPORTAL-1558 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Heute >From training field, it seems that most common use cases is to remove the info bar from portlets, so it should probably be made as default. But there should be a way to set the default to be the former behavior -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
16
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1502) DateTimeValidator validates incorrect with particular languages

by Khoi Nguyen (JIRA)

DateTimeValidator validates incorrect with particular languages --------------------------------------------------------------- Key: GTNPORTAL-1502 URL: https://jira.jboss.org/browse/GTNPORTAL-1502 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Khoi Nguyen With a particular language, French for example, if value of UIFormDateTimeInput field having day value > 12, DateTimeValidator would return false. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1450) Priority for skin modules

by Patrice Lamarque (JIRA)

Priority for skin modules ------------------------- Key: GTNPORTAL-1450 URL: https://jira.jboss.org/browse/GTNPORTAL-1450 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.1.0-GA Reporter: Patrice Lamarque The css stylesheets declared in gatein-resources.xml files get merged in no specific order. Sometimes, it is useful to control the order in which the resulting css markup appears in the merged file in order to apply css overrides. This is typically the kind of things you would like to do in an extension. By implementing a priority on skin module we should be able to give more control to the overrides. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
20
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1008) Gadget permissions are not working correctly (gagdet with restricted access in the AppReg are visible)

by Tugdual Grall (JIRA)

Gadget permissions are not working correctly (gagdet with restricted access in the AppReg are visible) ------------------------------------------------------------------------------------------------------ Key: GTNPORTAL-1008 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1008 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 3.0.0-GA Reporter: Tugdual Grall When in the App registry a gadget as been set to visible only to a restricted audience this permission is not used when in the portlet/gadget catalog. Use case: 1- Connect as Root 2- Go in the App Registry 3- Select one gadget, for example ToDo 4- Set the permission to /platform/administrators usrs 5- log out 6- connect as mary/gtn 7- go to your dashboard 8- click add gadget: 9 - BUG: you can see the ToDo Gadget and you can add it to the page ( You are not supposed to) 10 - Edit your page 11- Click on Gadget: 12- BUG: you can see the ToDo gadget (same bug as before) 13-BUG Add it on the page, you can drop it but it wil not be visible (protected content) since you are not allowed to do it. FIX: we need to hide the gadget from the catalog when the permissions are set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
12
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-819) Make sure pubsub is working between gadget

by jerem j (JIRA)

Make sure pubsub is working between gadget ------------------------------------------ Key: GTNPORTAL-819 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-819 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: jerem j Gadget API has a nice way to let gadget communicate together. http://wiki.opensocial.org/index.php?title=Gadgets.pubsub_(v0.8) . As far as I remember, that was not working. It should be connected to the pubsub functionality of the portal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1530) Generalize use of BaseMapping in WSRP mapping classes.

by Chris Laprun (JIRA)

Generalize use of BaseMapping in WSRP mapping classes. ------------------------------------------------------ Key: GTNPORTAL-1530 URL: https://jira.jboss.org/browse/GTNPORTAL-1530 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WSRP integration Affects Versions: 3.2.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Priority: Minor Fix For: 3.2.0-GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1926) DB and LDAP in read-only: user attributes are saved only to DB but they are still read from LDAP

by Marek Posolda (JIRA)

DB and LDAP in read-only: user attributes are saved only to DB but they are still read from LDAP ------------------------------------------------------------------------------------------------ Key: GTNPORTAL-1926 URL: https://issues.jboss.org/browse/GTNPORTAL-1926 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Identity integration Affects Versions: 3.1.0-GA Environment: - EPP 5.1.1.DEV01 with latest exo.portal.component.identity from GateIn trunk - Picketlink 1.3.0.Alpha03 - LDAP configured with read-only setup (picketlink-idm-ldap-acme-config.xml from "example" folder used as configuration file) Reporter: Marek Posolda Assignee: Boleslaw Dawidowicz Fix For: 3.2.0-GA I have LDAP configured as read-only (Parameter "readOnly" with value "true" is configured as option in configuration of "PortalRepository" in picketlink configuration file picketlink-idm-ldap-acme-config.xml ) And then I am doing this in EPP UI: 1) Login as "mposolda" with password 2) Click to my name in right top corner 3) Change my first name and last name to "Marekkk Poosoldaaaa". 4) Click "Save" and I have message that attributes are changed successfully 5) Logout 6) Login again as mposolda 7) I am seeing that I am still "Marek Posolda" Problem is that attributes are written to DB in method FallbackIdentityStoreImpl.updateAttributes (which is correct) but then they are read from LDAP in FallbackIdentityStoreImpl.getAttributes and DB attributes are simply ignored . This is confusing for users, because they may have feeling that their attributes are updated but they aren't) I think that one of these two conditions should be met: a) Show warning in step 4 that user can't change LDAP attributes (like FirstName, Lastname or Email) b) Don't show warning but in this case, attributes from DB should have preference over attributes from LDAP. It will be nice if this can be configurable and administrator can choose between option (a) or (b) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues June 2011