March 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNWSRP-213) Strict mode is not properly set at start-up

by Chris Laprun (JIRA)

Strict mode is not properly set at start-up ------------------------------------------- Key: GTNWSRP-213 URL: https://issues.jboss.org/browse/GTNWSRP-213 Project: GateIn WSRP Issue Type: Bug Components: Producer Affects Versions: 2.0.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.0.1-GA, 2.1.0-Alpha02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNWSRP-90) Use RuntimeContext from GTNCOMMON 2.0.4-GA when available

by Chris Laprun (JIRA)

Use RuntimeContext from GTNCOMMON 2.0.4-GA when available --------------------------------------------------------- Key: GTNWSRP-90 URL: https://jira.jboss.org/browse/GTNWSRP-90 Project: GateIn WSRP Issue Type: Feature Request Affects Versions: 2.0.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Priority: Minor -- 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

13 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (GTNWSRP-211) RegistrationUtils.validateConsumerAgent is not correct

by Chris Laprun (JIRA)

RegistrationUtils.validateConsumerAgent is not correct ------------------------------------------------------ Key: GTNWSRP-211 URL: https://issues.jboss.org/browse/GTNWSRP-211 Project: GateIn WSRP Issue Type: Bug Components: Producer Affects Versions: 2.1.0-Alpha01, 2.0.0-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.0.1-GA, 2.1.0-Alpha02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

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

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-128?page=com.atlassian.jira.plugi... ] Chris Laprun reassigned GTNWSRP-128: ------------------------------------ Assignee: Matt Wringe (was: Chris Laprun) > WSRP implementation does not executes getUserPrincipal() when the portlet is invoked remotely > --------------------------------------------------------------------------------------------- > > Key: GTNWSRP-128 > URL: https://issues.jboss.org/browse/GTNWSRP-128 > Project: GateIn WSRP > Issue Type: Bug > Environment: Red Hat Enterprise Linux 5 > Reporter: Ricardo Ferreira > Assignee: Matt Wringe > Labels: WSRP, consumer, getUserPrincipal, producer > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

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

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-127?page=com.atlassian.jira.plugi... ] Chris Laprun reassigned GTNWSRP-127: ------------------------------------ Assignee: Matt Wringe (was: Chris Laprun) > WSRP Identity Propagation users WSRP user context and should use WS-Security > ---------------------------------------------------------------------------- > > Key: GTNWSRP-127 > URL: https://issues.jboss.org/browse/GTNWSRP-127 > Project: GateIn WSRP > Issue Type: Bug > Environment: EPP 4.3 CP03 > Reporter: Aaron Pestel > Assignee: Matt Wringe > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (GTNWSRP-135) Better security support

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-135?page=com.atlassian.jira.plugi... ] Chris Laprun reassigned GTNWSRP-135: ------------------------------------ Assignee: Matt Wringe (was: Chris Laprun) > Better security support > ----------------------- > > Key: GTNWSRP-135 > URL: https://issues.jboss.org/browse/GTNWSRP-135 > Project: GateIn WSRP > Issue Type: Feature Request > Affects Versions: 1.1.1-GA > Reporter: Chris Laprun > Assignee: Matt Wringe > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNCOMMON-15) Clean up Maven dependencies

by Chris Laprun (JIRA)

Clean up Maven dependencies --------------------------- Key: GTNCOMMON-15 URL: https://issues.jboss.org/browse/GTNCOMMON-15 Project: GateIn Common Issue Type: Task Affects Versions: 2.0.3-GA Reporter: Chris Laprun Fix For: 2.0.4-GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNWSRP-209) Error when deleting a consumer in the WSRP admin portlet

by Arthur Peltier (JIRA)

Error when deleting a consumer in the WSRP admin portlet -------------------------------------------------------- Key: GTNWSRP-209 URL: https://issues.jboss.org/browse/GTNWSRP-209 Project: GateIn WSRP Issue Type: Bug Environment: jboss EPP 5.1.0 Reporter: Arthur Peltier Assignee: Chris Laprun Attachments: WSRP-Deletion error.txt When we delete a consumer in the WSRP admin portlet, the portlet disappears with an error message and we have a java.lang.NoClassDefFoundError exception in terminal -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] Moved: (GTNPORTAL-1834) Portlet's context-root cannot contain slashes

by Thomas Heute (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1834?page=com.atlassian.jira.pl... ] Thomas Heute moved JBEPP-855 to GTNPORTAL-1834: ----------------------------------------------- Project: GateIn Portal (was: JBoss Enterprise Portal Platform) Key: GTNPORTAL-1834 (was: JBEPP-855) > Portlet's context-root cannot contain slashes > --------------------------------------------- > > Key: GTNPORTAL-1834 > URL: https://issues.jboss.org/browse/GTNPORTAL-1834 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Thomas Heute > > I've tried to use a context-root with a slash "/" in a JSR-286 Hello World Portlet and it throws the following exception when trying to add it to a new page: > 11:59:46,926 ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet /oag.ade > 11:59:46,926 ERROR [STDERR] at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99) > Changing context-root to not contain slashes has fixed the problem. > Problem happens when using slashes "/" in: > application.xml of an .ear file > <module> > <web> > <web-uri>seamBookingPortlet.war</web-uri> > <context-root>/oag/ade</context-root> > </web> > </module> > Changing it to <context-root>/oag-ade</context-root> fixes the problem > jboss-web.xml of a .war file > <?xml version="1.0" encoding="UTF-8"?> > <jboss-web> > <context-root>/LG_1648_1_WEB/SamplePortlet</context-root> > </jboss-web> > Changing it to <context-root>/LG_1648_1_WEB.SamplePortlet</context-root> fixes the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNWSRP-206) Update Maven dependencies

by Thomas Heute (JIRA)

Update Maven dependencies ------------------------- Key: GTNWSRP-206 URL: https://issues.jboss.org/browse/GTNWSRP-206 Project: GateIn WSRP Issue Type: Task Reporter: Thomas Heute Assignee: Thomas Heute Fix For: 2.1.0-Beta01 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2011