March 2015 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3572) Missing exception handling in MembeshipDAOImpl

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3572?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3572: ---------------------------------------------------- vramik(a)redhat.com changed the Status of [bug 1179940|https://bugzilla.redhat.com/show_bug.cgi?id=1179940] from ON_QA to VERIFIED > Missing exception handling in MembeshipDAOImpl > ---------------------------------------------- > > Key: GTNPORTAL-3572 > URL: https://issues.jboss.org/browse/GTNPORTAL-3572 > Project: GateIn Portal > Issue Type: Bug > Components: Identity integration > Affects Versions: 3.8.2.Final > Reporter: Martin Weiler > Assignee: Boleslaw Dawidowicz > Fix For: 3.9.0.Final, 3.8.14.Final > > > MembershipDAOImpl.linkMembership(...) is missing exception handling around the following call: > {code} > getIdentitySession().getRoleManager().createRole(mt.getName(), user.getUserName(), groupId); > {code} > If this call fails, eg. for example due to an exception from the underlying database, this result in a corrupted transaction state. Subsequent requests using this thread fail with an error similar to the following: > {noformat} > org.hibernate.AssertionFailure: null id in org.picketlink.idm.impl.model.hibernate.HibernateIdentityObjectRelationship entry (don't flush the Session after an exception occurs) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3560) Cache-control on the UI encodes too much

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3560?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3560: ---------------------------------------------------- vramik(a)redhat.com changed the Status of [bug 1165102|https://bugzilla.redhat.com/show_bug.cgi?id=1165102] from ON_QA to VERIFIED > Cache-control on the UI encodes too much > ---------------------------------------- > > Key: GTNPORTAL-3560 > URL: https://issues.jboss.org/browse/GTNPORTAL-3560 > Project: GateIn Portal > Issue Type: Feature Request > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.9.0.Final, 3.8.9.Alpha02 > > > The cache-control directive, when specified on the UI, gets too much encoding when being set as a header. This means that it's not useful at the current state when more than one parameter for the cache-control is set: > For instance, the string "no-cache, max-age=0, must-revalidate, no-store" becomes this header: > {code}Cache-Control:no-cache%2C+max-age%3D0%2C+must-revalidate%2C+no-store{code} > The input should be sanitized only for new lines, to avoid a "HTTP Response Splitting" attack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3572) Missing exception handling in MembeshipDAOImpl

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3572?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3572: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1179940|https://bugzilla.redhat.com/show_bug.cgi?id=1179940] from MODIFIED to ON_QA > Missing exception handling in MembeshipDAOImpl > ---------------------------------------------- > > Key: GTNPORTAL-3572 > URL: https://issues.jboss.org/browse/GTNPORTAL-3572 > Project: GateIn Portal > Issue Type: Bug > Components: Identity integration > Affects Versions: 3.8.2.Final > Reporter: Martin Weiler > Assignee: Boleslaw Dawidowicz > Fix For: 3.9.0.Final, 3.8.14.Final > > > MembershipDAOImpl.linkMembership(...) is missing exception handling around the following call: > {code} > getIdentitySession().getRoleManager().createRole(mt.getName(), user.getUserName(), groupId); > {code} > If this call fails, eg. for example due to an exception from the underlying database, this result in a corrupted transaction state. Subsequent requests using this thread fail with an error similar to the following: > {noformat} > org.hibernate.AssertionFailure: null id in org.picketlink.idm.impl.model.hibernate.HibernateIdentityObjectRelationship entry (don't flush the Session after an exception occurs) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3560) Cache-control on the UI encodes too much

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3560?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3560: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1165102|https://bugzilla.redhat.com/show_bug.cgi?id=1165102] from MODIFIED to ON_QA > Cache-control on the UI encodes too much > ---------------------------------------- > > Key: GTNPORTAL-3560 > URL: https://issues.jboss.org/browse/GTNPORTAL-3560 > Project: GateIn Portal > Issue Type: Feature Request > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.9.0.Final, 3.8.9.Alpha02 > > > The cache-control directive, when specified on the UI, gets too much encoding when being set as a header. This means that it's not useful at the current state when more than one parameter for the cache-control is set: > For instance, the string "no-cache, max-age=0, must-revalidate, no-store" becomes this header: > {code}Cache-Control:no-cache%2C+max-age%3D0%2C+must-revalidate%2C+no-store{code} > The input should be sanitized only for new lines, to avoid a "HTTP Response Splitting" attack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3579) Add validation for surrogate pair of characters on UITabbedDashboard

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3579?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3579: ---------------------------------------------------- Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 1105521|https://bugzilla.redhat.com/show_bug.cgi?id=1105521] from ON_QA to VERIFIED > Add validation for surrogate pair of characters on UITabbedDashboard > -------------------------------------------------------------------- > > Key: GTNPORTAL-3579 > URL: https://issues.jboss.org/browse/GTNPORTAL-3579 > Project: GateIn Portal > Issue Type: Bug > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.14.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNCOMMON-24) FastURLDecoder cannot decode surrogate pair characters

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNCOMMON-24?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on GTNCOMMON-24: -------------------------------------------------- Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 1105521|https://bugzilla.redhat.com/show_bug.cgi?id=1105521] from ON_QA to VERIFIED > FastURLDecoder cannot decode surrogate pair characters > ------------------------------------------------------ > > Key: GTNCOMMON-24 > URL: https://issues.jboss.org/browse/GTNCOMMON-24 > Project: GateIn Common > Issue Type: Bug > Reporter: Takayuki Konishi > Attachments: surrogatepairtest.patch > > > FastURLDecoder cannot decode surrogate pair characters. > When I decoded [U+20000B|http://www.fileformat.info/info/unicode/char/2000B/index.htm], I got MalformedInputException: > {code} > org.gatein.common.text.MalformedInputException: Cannot decode char 'A0' > at org.gatein.common.text.FastURLDecoder.safeEncode(FastURLDecoder.java:217) > at org.gatein.common.text.AbstractCharEncoder.encode(AbstractCharEncoder.java:45) > at org.gatein.common.text.AbstractCharEncoder.encode(AbstractCharEncoder.java:62) > at org.gatein.common.text.FastURLDecoderTestCase.testEncodeSurrogatePair(FastURLDecoderTestCase.java:159) > {code} > I also attach a patch for testcase. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3524?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3524: ---------------------------------------------------- Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 1122527|https://bugzilla.redhat.com/show_bug.cgi?id=1122527] from ON_QA to VERIFIED > 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, 3.8.14.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.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3580) Make the PicketLinkIDMService hot deployed with new configuration

by Neji Gammoudi (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3580?page=com.atlassian.jira.pl... ] Neji Gammoudi commented on GTNPORTAL-3580: ------------------------------------------ Hello, Any news about this issue Please? > Make the PicketLinkIDMService hot deployed with new configuration > ----------------------------------------------------------------- > > Key: GTNPORTAL-3580 > URL: https://issues.jboss.org/browse/GTNPORTAL-3580 > Project: GateIn Portal > Issue Type: Feature Request > Components: Identity integration > Affects Versions: 3.5.10.Final > Reporter: Neji Gammoudi > Assignee: Boleslaw Dawidowicz > > I want to make an administration LDAP screen for eXoPlatform from which i can update the LDAP configuration for different implementations (openldap,opends,ad,...) that requires the load of different XML configuration files such as picketlink-idm-msad-config.xml and picketlink-idm-ldap-config.xml ,... > I didn't found any way to make the PciketLinkIDMService hot deployed with new configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3577) Remove mentions to LinkedIn OAuth in for JBoss-based packaging

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3577?page=com.atlassian.jira.pl... ] Peter Palaga commented on GTNPORTAL-3577: ----------------------------------------- There is one more commit to fix this: https://github.com/gatein/gatein-portal/commit/499defa92ca0df4a877c05f4d8... > Remove mentions to LinkedIn OAuth in for JBoss-based packaging > -------------------------------------------------------------- > > Key: GTNPORTAL-3577 > URL: https://issues.jboss.org/browse/GTNPORTAL-3577 > Project: GateIn Portal > Issue Type: Bug > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.8.14.Final > > > The LinkedIn OAuth integration currently misses a few pieces to work on JBoss AS and related (Wildfly, EAP, ...). So, the configuration file needs to be changed to remove mentions to it, until this integration is done and tested for this package. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3524?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3524: ---------------------------------------------------- Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 1122527|https://bugzilla.redhat.com/show_bug.cgi?id=1122527] from MODIFIED to ON_QA > 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, 3.8.14.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.11#6341)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2015