September 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3545) Upgrade Apache POI to version 3.10.1

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3545?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3545: ------------------------------------ Description: CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138168 (was: CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138166) > Upgrade Apache POI to version 3.10.1 > ------------------------------------ > > Key: GTNPORTAL-3545 > URL: https://issues.jboss.org/browse/GTNPORTAL-3545 > Project: GateIn Portal > Issue Type: Task > Reporter: Peter Palaga > Assignee: Peter Palaga > > CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138168 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3545) Upgrade Apache POI to version 3.10.1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3545?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3545: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1138168 > Upgrade Apache POI to version 3.10.1 > ------------------------------------ > > Key: GTNPORTAL-3545 > URL: https://issues.jboss.org/browse/GTNPORTAL-3545 > Project: GateIn Portal > Issue Type: Task > Reporter: Peter Palaga > Assignee: Peter Palaga > > CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138166 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3547) Update cas-client-core on gatein-portal

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3547?page=com.atlassian.jira.pl... ] Juraci Paixão Kröhling updated GTNPORTAL-3547: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/907 > Update cas-client-core on gatein-portal > --------------------------------------- > > Key: GTNPORTAL-3547 > URL: https://issues.jboss.org/browse/GTNPORTAL-3547 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3547) Update cas-client-core on gatein-portal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3547?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3547: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1131355 > Update cas-client-core on gatein-portal > --------------------------------------- > > Key: GTNPORTAL-3547 > URL: https://issues.jboss.org/browse/GTNPORTAL-3547 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3547) Update cas-client-core on gatein-portal

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNPORTAL-3547: ------------------------------------------------- Summary: Update cas-client-core on gatein-portal Key: GTNPORTAL-3547 URL: https://issues.jboss.org/browse/GTNPORTAL-3547 Project: GateIn Portal Issue Type: Enhancement Reporter: Juraci Paixão Kröhling Assignee: Juraci Paixão Kröhling -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3546) Update cas-client-core on gatein-sso

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNPORTAL-3546: ------------------------------------------------- Summary: Update cas-client-core on gatein-sso Key: GTNPORTAL-3546 URL: https://issues.jboss.org/browse/GTNPORTAL-3546 Project: GateIn Portal Issue Type: Enhancement Reporter: Juraci Paixão Kröhling Assignee: Juraci Paixão Kröhling -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3545) Upgrade Apache POI to version 3.10.1

by Peter Palaga (JIRA)

Peter Palaga created GTNPORTAL-3545: --------------------------------------- Summary: Upgrade Apache POI to version 3.10.1 Key: GTNPORTAL-3545 URL: https://issues.jboss.org/browse/GTNPORTAL-3545 Project: GateIn Portal Issue Type: Task Reporter: Peter Palaga Assignee: Peter Palaga CVE-2014-3574 CVE-2014-3529 apache-poi: various flaws, see https://bugzilla.redhat.com/show_bug.cgi?id=1138166 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3543) Update gatein-portal to PicketLink 2.5.3

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3543?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3543: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.9.0.Final 3.8.8.Final Resolution: Done > Update gatein-portal to PicketLink 2.5.3 > ---------------------------------------- > > Key: GTNPORTAL-3543 > URL: https://issues.jboss.org/browse/GTNPORTAL-3543 > Project: GateIn Portal > Issue Type: Task > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.9.0.Final, 3.8.8.Final > > > Update the dependency on PicketLink to version 2.5.3, consuming the new version of gatein-sso. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3524) Custom portals cannot use remote portlets

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3524?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3524: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.9.0.Final Resolution: Done > Custom portals cannot use remote portlets > ----------------------------------------- > > Key: GTNPORTAL-3524 > URL: https://issues.jboss.org/browse/GTNPORTAL-3524 > Project: GateIn Portal > Issue Type: Bug > Components: WSRP integration > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.9.0.Final > > > Before GTNPORTAL-3291, the FederatingPortletInvoker was shared among all contexts, meaning that a PortletInvoker responsible for local portlets was the same on "portal" and on "sample-portal". Similarly, a WSRP PortletInvoker was also shared. > This caused the problems described in 3291 and 2700 and a fix was issued in that each context would have it's own FederatingPortletInvoker . > With local portlets, each context having its own FederatingPortletInvoker is not a big issue, because the query is made at the JCR level for which portlets are available. > With remote portlets, it's a problem, as WSRP registers the consumers only once, for the "portal" context. This means that the consumer invokers are not available for non-"portal" contexts. With this, a call from the context "sample-portal" to the FederatingPortletInvoker, requesting portlet "selfv2.bla" would fail, as there's no way to find this portlet on this particular invoker tree. > While the producers are also started for the "portal" context, the fact that producers have their own servlet context makes it immune from this bug, as all HTTP calls to the producers reaches a context whose invoker *knows* about the requested portlet. In other words: producers are not affected by this bug. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3524) Custom portals cannot use remote portlets

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3524?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3524: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/891 > Custom portals cannot use remote portlets > ----------------------------------------- > > Key: GTNPORTAL-3524 > URL: https://issues.jboss.org/browse/GTNPORTAL-3524 > Project: GateIn Portal > Issue Type: Bug > Components: WSRP integration > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.9.0.Final > > > Before GTNPORTAL-3291, the FederatingPortletInvoker was shared among all contexts, meaning that a PortletInvoker responsible for local portlets was the same on "portal" and on "sample-portal". Similarly, a WSRP PortletInvoker was also shared. > This caused the problems described in 3291 and 2700 and a fix was issued in that each context would have it's own FederatingPortletInvoker . > With local portlets, each context having its own FederatingPortletInvoker is not a big issue, because the query is made at the JCR level for which portlets are available. > With remote portlets, it's a problem, as WSRP registers the consumers only once, for the "portal" context. This means that the consumer invokers are not available for non-"portal" contexts. With this, a call from the context "sample-portal" to the FederatingPortletInvoker, requesting portlet "selfv2.bla" would fail, as there's no way to find this portlet on this particular invoker tree. > While the producers are also started for the "portal" context, the fact that producers have their own servlet context makes it immune from this bug, as all HTTP calls to the producers reaches a context whose invoker *knows* about the requested portlet. In other words: producers are not affected by this bug. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues September 2014