November 2012 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNSSO-18) Investigate Picketlink federation WARNINGS during GateIn as IDP setup

by Marek Posolda (JIRA)

Marek Posolda created GTNSSO-18: ----------------------------------- Summary: Investigate Picketlink federation WARNINGS during GateIn as IDP setup Key: GTNSSO-18 URL: https://issues.jboss.org/browse/GTNSSO-18 Project: GateIn SSO Issue Type: Enhancement Affects Versions: 1.3.0.Beta01 Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 1.3.0.Beta02 There are some WARNs from picketlink federation when having GateIn as SAML2 IDP. It doesn't break functionality, but needs to be investigated if everything is ok in configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
1
0 / 0

[JBoss JIRA] (GTNSSO-17) Get rid of commons-httpclient3 and move everything to httpclient4

by Marek Posolda (JIRA)

Marek Posolda created GTNSSO-17: ----------------------------------- Summary: Get rid of commons-httpclient3 and move everything to httpclient4 Key: GTNSSO-17 URL: https://issues.jboss.org/browse/GTNSSO-17 Project: GateIn SSO Issue Type: Enhancement Reporter: Marek Posolda Assignee: Marek Posolda It's done for AS7 side. Needs to done and properly verified also for authentication plugins on SSO servers side (CAS, JOSSO, OpenAM) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
3
0 / 0

[JBoss JIRA] (GTNSSO-20) Replace call HttpMethod.getResponseBodyAsString() in RestCallbackHandler

by Martin Weiler (JIRA)

Martin Weiler created GTNSSO-20: ----------------------------------- Summary: Replace call HttpMethod.getResponseBodyAsString() in RestCallbackHandler Key: GTNSSO-20 URL: https://issues.jboss.org/browse/GTNSSO-20 Project: GateIn SSO Issue Type: Task Affects Versions: 1.3.0.Beta01 Reporter: Martin Weiler Assignee: Marek Posolda Using SAML2 integration with RestCallbackHandler leads to the following WARN messages: 10:03:14,421 WARN [HttpMethodBase] Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. The HttpMethod.getResponseBodyAsString() method call should be replaced in order to avoid the WARN message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-19) EPP+SP: Problem with LoginRedirectFilter reading POST parameters

by Marek Posolda (JIRA)

Marek Posolda created GTNSSO-19: ----------------------------------- Summary: EPP+SP: Problem with LoginRedirectFilter reading POST parameters Key: GTNSSO-19 URL: https://issues.jboss.org/browse/GTNSSO-19 Project: GateIn SSO Issue Type: Enhancement Affects Versions: 1.3.0.Beta01 Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 1.3.0.GA Reported by Martin Weiler: a customer is using LoginRedirectFilter on EPP+SP. We found out that this filter is breaking the Content Inline editing functionality of SP, as it reads out the request parameters, which results in the POST parameters getting null. The customer is suggesting the following fix: // Return true if logout request is in progress - private boolean isLogoutRequest(HttpServletRequest req) - { - String portalComponentId = req.getParameter("portal:componentId"); - String portalAction = req.getParameter("portal:action"); - if (("UIPortal".equals(portalComponentId)) && ("Logout".equals(portalAction))) - { - return true; - } - else - { - return false; - } + private boolean isLogoutRequest(HttpServletRequest req) { + if("GET".equals(req.getMethod())) { + String portalComponentId = req.getParameter("portal:componentId"); + String portalAction = req.getParameter("portal:action"); + + if (("UIPortal".equals(portalComponentId)) && ("Logout".equals(portalAction))) + return true; + else + return false; + } + else + return false; } If you think it is ok, could you go ahead and commit it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2709) Upgrade SSO version to 1.3.0.CR03

by Marek Posolda (JIRA)

Marek Posolda created GTNPORTAL-2709: ---------------------------------------- Summary: Upgrade SSO version to 1.3.0.CR03 Key: GTNPORTAL-2709 URL: https://issues.jboss.org/browse/GTNPORTAL-2709 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Components: SSO Affects Versions: 3.5.0.Beta01 Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 3.5.0.Beta02 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
3
0 / 0

[JBoss JIRA] (GTNPORTAL-2708) Login screen is displayed as text instead of rendered in clustered environment

by Chris Laprun (JIRA)

Chris Laprun created GTNPORTAL-2708: --------------------------------------- Summary: Login screen is displayed as text instead of rendered in clustered environment Key: GTNPORTAL-2708 URL: https://issues.jboss.org/browse/GTNPORTAL-2708 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: 2-node AS7 cluster behind load balancer, not sure if the issue also happens without load balancer Reporter: Chris Laprun For example trying to access http://localhost/portal/g/:platform:administrators/Test directly on a running cluster behind a load balancer redirects you to the page at http://localhost/portal/login?initialURI=/portal/g/:platform:administrato... which should display the login screen but that screen appears as text instead of being rendered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (GTNPC-9) PortletRequestDispatcher does not execute 'forward' method during resource request.

by Thomas Heute (JIRA)

PortletRequestDispatcher does not execute 'forward' method during resource request. ----------------------------------------------------------------------------------- Key: GTNPC-9 URL: https://jira.jboss.org/jira/browse/GTNPC-9 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 1.2.0-Beta01 Reporter: Thomas Heute Assignee: Julien Viet See linked issue -- 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

11 years, 6 months

4
12
0 / 0

[JBoss JIRA] Created: (GTNPC-13) AbstractPortalContext should be renamed as it's not abstract

by Chris Laprun (JIRA)

AbstractPortalContext should be renamed as it's not abstract ------------------------------------------------------------ Key: GTNPC-13 URL: https://jira.jboss.org/jira/browse/GTNPC-13 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 2.1.0-Beta02 Reporter: Chris Laprun Fix For: 2.1.0-CR1 -- 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

11 years, 6 months

4
11
0 / 0

[JBoss JIRA] (GTNPC-86) Add support for CDI portlets

by Ken Finnigan (JIRA)

Ken Finnigan created GTNPC-86: --------------------------------- Summary: Add support for CDI portlets Key: GTNPC-86 URL: https://issues.jboss.org/browse/GTNPC-86 Project: GateIn Portlet Container Issue Type: Feature Request Reporter: Ken Finnigan Fix For: 2.3.3-GA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
2
0 / 0

[JBoss JIRA] (GTNPC-85) Cannot build from scratch without privileged access to JBoss legacy repository

by Chris Laprun (JIRA)

Chris Laprun created GTNPC-85: --------------------------------- Summary: Cannot build from scratch without privileged access to JBoss legacy repository Key: GTNPC-85 URL: https://issues.jboss.org/browse/GTNPC-85 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 2.3.2-GA Reporter: Chris Laprun Fix For: 2.3.3-GA If you try to build PC with a clean environment without priviledged access to JBoss' legacy repo, you will get the following (or similar) error: [ERROR] Failed to execute goal on project pc-test-core: Could not resolve dependencies for project org.gatein.pc:pc-test-core:jar:2.3.3-GA-SNAPSHOT: Failed to collect dependencies for [org.gatein.common:common-logging:jar:2.0.4-GA (compile), org.gatein.wci:wci-wci:jar:2.2.0-Beta01 (compile), org.gatein.pc:pc-controller:jar:2.3.3-GA-SNAPSHOT (compile), org.gatein.pc:pc-portlet:jar:2.3.3-GA-SNAPSHOT (compile), org.gatein.pc:pc-api:jar:2.3.3-GA-SNAPSHOT (compile), log4j:log4j:jar:1.2.16 (compile), org.jboss.unit:jboss-unit:jar:1.2.4 (compile), org.jboss.unit:jboss-unit-remote:jar:1.2.4 (compile), org.jboss.unit:jboss-unit-tooling-ant:jar:1.2.4 (compile), org.jboss.unit:portal-test:jar:1.2.4 (compile), org.jboss.unit:portal-test-generic:jar:1.2.4 (compile), org.jboss.remoting:jboss-remoting:jar:2.5.0.GA (compile), concurrent:concurrent:jar:1.3.4 (test), jboss:jboss-serialization:jar:1.0.3.GA (test), org.jboss.logging:jboss-logging-jdk:jar:2.0.5.GA (compile), org.jboss.logging:jboss-logging-log4j:jar:2.0.5.GA (compile), commons-logging:commons-logging:jar:1.1.1 (compile), commons-httpclient:commons-httpclient:jar:3.1 (compile), javax.ccpp:ccpp:jar:1.0 (compile), javax.portlet:portlet-api:jar:2.0 (compile), org.apache.maven:maven-ant-tasks:jar:2.1.1 (compile), org.slf4j:slf4j-simple:jar:1.5.8 (test)]: Failed to read artifact descriptor for apache-log4j:log4j:jar:1.2.14: Could not transfer artifact apache-log4j:log4j:pom:1.2.14 from/to repository.jboss.org (http://repository.jboss.org/maven2/): Access denied to: http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.14/log4j-1.2.14... -> [Help 1] Repository needs to be explicitly set in the POM file (so that folks trying to build don't have to set it) and exclusions should be added to dependencies to avoid pulling useless dependencies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues November 2012