October 2010 - gatein-issues - Jboss List Archives

[JBoss JIRA] Moved: (GTNWSRP-128) WSRP implementation does not executes getUserPrincipal() when the portlet is invoked remotely

by Chris Laprun (JIRA)

[ https://jira.jboss.org/browse/GTNWSRP-128?page=com.atlassian.jira.plugin.... ] Chris Laprun moved JBPORTAL-2404 to GTNWSRP-128: ------------------------------------------------ Project: GateIn WSRP (was: JBoss Portal) Key: GTNWSRP-128 (was: JBPORTAL-2404) Affects Version/s: (was: 2.7.2 Final) Component/s: (was: Portal WSRP) > WSRP implementation does not executes getUserPrincipal() when the portlet is invoked remotely > --------------------------------------------------------------------------------------------- > > Key: GTNWSRP-128 > URL: https://jira.jboss.org/browse/GTNWSRP-128 > Project: GateIn WSRP > Issue Type: Bug > Environment: Red Hat Enterprise Linux 5 > Reporter: Ricardo Ferreira > Assignee: Chris Laprun > Attachments: myPortlet.zip > > > The JBoss Portal implementation does not executes correctly API invocations related to the principal retrieve from the portlet contêiner. When you executes a local portlet, the API call "HttpServletRequest.getUserPrincipal()" works fine. But when you install this same portlet in a remote portlet container using WSRP, the API call returns "null". -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (GTNWSRP-127) WSRP Identity Propagation users WSRP user context and should use WS-Security

by Chris Laprun (JIRA)

[ https://jira.jboss.org/browse/GTNWSRP-127?page=com.atlassian.jira.plugin.... ] Chris Laprun moved JBPORTAL-2468 to GTNWSRP-127: ------------------------------------------------ Project: GateIn WSRP (was: JBoss Portal) Key: GTNWSRP-127 (was: JBPORTAL-2468) Component/s: (was: Portal WSRP) > WSRP Identity Propagation users WSRP user context and should use WS-Security > ---------------------------------------------------------------------------- > > Key: GTNWSRP-127 > URL: https://jira.jboss.org/browse/GTNWSRP-127 > Project: GateIn WSRP > Issue Type: Bug > Environment: EPP 4.3 CP03 > Reporter: Aaron Pestel > Assignee: Chris Laprun > > The current WSRP implementation passes the username via the WSRP user context, which according to the spec is not the purpose of the user context. > I have created a wiki that offers a potential solution. It involves two jax-rpc handers (one to generate the ws-security header on the consumer and one to parse and authenticate the ws-security header on the producer). In addition, org/jboss/portal/wsrp/producer/RequestProcessor.java needs to be changed to use the authenticated user's context rather than the information passed in the wsrp user context. Source code for these pieces is in the JARs at this wiki: http://community.jboss.org/wiki/JBossEPP43-WSRPwithWS-SecurityandSSL > Here is the current implementation of RequestProcessor that pulls security information from the WSRP user context, followed by my proposed implementation: > ------------------------------------------------------------------------------------------- > // fix-me: check that the correct semantics is used. > private SecurityContext createSecurityContext(final MarkupParams params, final RuntimeContext runtimeContext, > final org.jboss.portal.wsrp.core.UserContext wsrpUserContext) > { > return new SecurityContext() > { > public boolean isSecure() > { > return params.isSecureClientCommunication(); > } > public String getAuthType() > { > return runtimeContext.getUserAuthentication(); > } > public String getRemoteUser() > { > if (wsrpUserContext != null) > { > return wsrpUserContext.getUserContextKey(); > } > return null; > } > public Principal getUserPrincipal() > { > return null; > } > public boolean isUserInRole(String roleName) > { > return wsrpUserContext != null && Tools.isContainedIn(roleName, wsrpUserContext.getUserCategories()); > } > public boolean isAuthenticated() > { > return wsrpUserContext != null; > } > }; > } > ------------------------------------------------------------------------------------------- > ------------------------------------------------------------------------------------------- > // fix-me: check that the correct semantics is used. > private SecurityContext createSecurityContext(final MarkupParams params, final RuntimeContext runtimeContext, > final org.jboss.portal.wsrp.core.UserContext wsrpUserContext) > { > final Request r = ((org.apache.catalina.connector.Request)(SecurityAssociationValve.activeRequest.get())); > return new SecurityContext() > { > public boolean isSecure() > { > return r.isSecure(); > } > public String getAuthType() > { > return r.getAuthType(); > } > public String getRemoteUser() > { > return r.getRemoteUser(); > } > public Principal getUserPrincipal() > { > return r.getUserPrincipal(); > } > public boolean isUserInRole(String roleName) > { > return r.isUserInRole(roleName); > } > public boolean isAuthenticated() > { > return r.getUserPrincipal() != null; > } > }; > } > ------------------------------------------------------------------------------------------- -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNWSRP-122) Richfaces request aren't managed properly

by Michal Vanco (JIRA)

Richfaces request aren't managed properly ----------------------------------------- Key: GTNWSRP-122 URL: https://jira.jboss.org/browse/GTNWSRP-122 Project: GateIn WSRP Issue Type: Bug Affects Versions: 2.0.0-Beta05 Reporter: Michal Vanco Assignee: Chris Laprun Fix For: 2.0.0-CR01 When using tictactoe portlet or richfacesPortlet I get bad responses on all ajax requests. If you click on anything, you get html source instead of UI, after refresh page is ok. RichfacesPortlet is bundled at EPP (5.1.0 ER03) at: jboss-epp-5.1/portletbridge/examples/richFacesPortlet-2.1.0.CR1.war -- 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

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1607) UIPortlet should use constant PortalContext since it never varies

by Chris Laprun (JIRA)

UIPortlet should use constant PortalContext since it never varies ----------------------------------------------------------------- Key: GTNPORTAL-1607 URL: https://jira.jboss.org/browse/GTNPORTAL-1607 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebUI Affects Versions: 3.1.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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1600) MOPConsumerStructureProvider does not reflect current state

by Chris Laprun (JIRA)

MOPConsumerStructureProvider does not reflect current state ----------------------------------------------------------- Key: GTNPORTAL-1600 URL: https://jira.jboss.org/browse/GTNPORTAL-1600 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WSRP integration Affects Versions: 3.1.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 3.2.0-GA In particular with respect to page creation/destruction. -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNWSRP-120) ProducerInfo refresh does not properly handle situation where WSDL URL is incorrect.

by Chris Laprun (JIRA)

ProducerInfo refresh does not properly handle situation where WSDL URL is incorrect. ------------------------------------------------------------------------------------ Key: GTNWSRP-120 URL: https://jira.jboss.org/browse/GTNWSRP-120 Project: GateIn WSRP Issue Type: Bug Components: Admin GUI Affects Versions: 2.0.0-Beta05 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.0.0-CR01 -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNWSRP-118) Error when editing name of v1 consumer

by Michal Vanco (JIRA)

Error when editing name of v1 consumer --------------------------------------- Key: GTNWSRP-118 URL: https://jira.jboss.org/browse/GTNWSRP-118 Project: GateIn WSRP Issue Type: Bug Affects Versions: 2.0.0-Beta05 Reporter: Michal Vanco Assignee: Chris Laprun Fix For: 2.0.0-CR01 When I want to edit consumer name, I get error in UI: Couldn't access WSRPV2ServiceDescriptionPortType service. Cause: Cannot get port meta data for: org.oasis.wsrp.v2.WSRPV2ServiceDescriptionPortType Log is clear. - create new v1 consumer (or use selfv1) - configure -> edit name -> Refresh & Save This applies only for v1, with v2 consumer I have no error when editting name. -- 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

15 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNWSRP-119) ProducerInfo.internalRefresh should properly log exceptions when they occur

by Chris Laprun (JIRA)

ProducerInfo.internalRefresh should properly log exceptions when they occur --------------------------------------------------------------------------- Key: GTNWSRP-119 URL: https://jira.jboss.org/browse/GTNWSRP-119 Project: GateIn WSRP Issue Type: Feature Request Components: Consumer Affects Versions: 2.0.0-Beta05 Reporter: Chris Laprun Assignee: Chris Laprun Priority: Minor Fix For: 2.0.0-CR01 -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Updated: (GTNPORTAL-1599) Create a wizard for generating a portal extension

by eric schabell (JIRA)

[ https://jira.jboss.org/browse/GTNPORTAL-1599?page=com.atlassian.jira.plug... ] eric schabell updated GTNPORTAL-1599: ------------------------------------- Attachment: extension.tar.bz2 > Create a wizard for generating a portal extension > ------------------------------------------------- > > Key: GTNPORTAL-1599 > URL: https://jira.jboss.org/browse/GTNPORTAL-1599 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: Working with JBoss EPP 5.x versions > Reporter: eric schabell > Attachments: extension.tar.bz2 > > > Working with extenstions like the one I will attach or the one provided in the docs directory is a bit cumbersome. Can we have someone setup a wizard for the portal to generate an extension project. Maybe a maven archtype would be enough but not sure. Would be great to have this in the portal tooling. > PS. feel free to categorize this with the proper project, not sure if it should be in JBoss Tools or not? -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNWSRP-113) UI improvements in import & export

by Michal Vanco (JIRA)

UI improvements in import & export ---------------------------------- Key: GTNWSRP-113 URL: https://jira.jboss.org/browse/GTNWSRP-113 Project: GateIn WSRP Issue Type: Bug Components: Admin GUI Affects Versions: 2.0.0-Beta03, 2.0.0-Beta01 Reporter: Michal Vanco Assignee: Chris Laprun Fix For: 2.0.0-CR01 Attachments: wsrp-consumers-list_changed_actions_column.png, wsrp-export-list_changed_column_width.png, wsrp-export_detail_changed_column_width.png wsrp-import_changed_column_width: change width of Import? column - 5% or 50px is enough, table looks much better wsrp-export_detail_changed_column_width: change first column width at export detail - 110px wsrp-export-list_changed_column_width: change column width at exports list, Has failed portlets? - 100px - table looks much better wsrp-consumers-list_changed_actions_column: change column width at consumers list, Actions - 500px or 55% - all actions are at one line (or more if there will be some icons for Import/Export) Note: screens are with edited widths of columns (proposals) - not current status. -- 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

15 years, 5 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues October 2010