June 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2912) Unable to logout when property 'admins only'

by Matt Wringe (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2912?page=com.atlassian.jira.pl... ] Matt Wringe commented on GTNPORTAL-2912: ---------------------------------------- Not a bug. This allows the admin to use a different mechanism rather than the shared layout. It is up to the admin to make sure there is another mechanism available to perform such operations, such as a separate portlet not part of the shared layout. > Unable to logout when property 'admins only' > -------------------------------------------- > > Key: GTNPORTAL-2912 > URL: https://issues.jboss.org/browse/GTNPORTAL-2912 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Beta01 > Environment: gatein-master (3.6.0.Beta02-SNAPSHOT) > Reporter: Vlastislav Ramik > Labels: JPP61-Test-dev > > Unable to logout when property 'admins only' is set for portal layout. > If the 'admins only' property is set for newly created portal, i.g. 'test', once the portal is accessed, shared layout is not displayed even for classic portal. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3103) Edit permissions are not updated in REST API

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3103?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-3103: ------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.6.0.Final Resolution: Done > Edit permissions are not updated in REST API > -------------------------------------------- > > Key: GTNPORTAL-3103 > URL: https://issues.jboss.org/browse/GTNPORTAL-3103 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST API > Affects Versions: 3.6.0.Beta02 > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Fix For: 3.6.0.Final > > > The field access-permissions are read from the request instead of edit-permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3103) Edit permissions are not updated in REST API

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3103?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-3103: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/522 > Edit permissions are not updated in REST API > -------------------------------------------- > > Key: GTNPORTAL-3103 > URL: https://issues.jboss.org/browse/GTNPORTAL-3103 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST API > Affects Versions: 3.6.0.Beta02 > Reporter: Nick Scavelli > Assignee: Nick Scavelli > > The field access-permissions are read from the request instead of edit-permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3045) Site Editor link used in case when we are in Group navigation

by Matt Wringe (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3045?page=com.atlassian.jira.pl... ] Matt Wringe reassigned GTNPORTAL-3045: -------------------------------------- Assignee: Matt Wringe > Site Editor link used in case when we are in Group navigation > ------------------------------------------------------------- > > Key: GTNPORTAL-3045 > URL: https://issues.jboss.org/browse/GTNPORTAL-3045 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Beta02 > Environment: jboss-jpp-6.1.0.ER1-prod-17052013.zip > Reporter: Vlastislav Ramik > Assignee: Matt Wringe > Labels: JPP61-Test-dev > > When you are in Group navigation there is link Site Editor. There should be Group Editor. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3103) Edit permissions are not updated in REST API

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3103?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3103: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=971077 > Edit permissions are not updated in REST API > -------------------------------------------- > > Key: GTNPORTAL-3103 > URL: https://issues.jboss.org/browse/GTNPORTAL-3103 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST API > Affects Versions: 3.6.0.Beta02 > Reporter: Nick Scavelli > Assignee: Nick Scavelli > > The field access-permissions are read from the request instead of edit-permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3103) Edit permissions are not updated in REST API

by Nick Scavelli (JIRA)

Nick Scavelli created GTNPORTAL-3103: ---------------------------------------- Summary: Edit permissions are not updated in REST API Key: GTNPORTAL-3103 URL: https://issues.jboss.org/browse/GTNPORTAL-3103 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: REST API Affects Versions: 3.6.0.Beta02 Reporter: Nick Scavelli Assignee: Nick Scavelli The field access-permissions are read from the request instead of edit-permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-27) Can't login through external IDP scenario with non-ascii password

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-27?page=com.atlassian.jira.plugin.... ] Marek Posolda resolved GTNSSO-27. --------------------------------- Resolution: Done Fixed by commit https://github.com/gatein/gatein-sso/commit/44502c2f1119f3c6ed67715c5ec23... > Can't login through external IDP scenario with non-ascii password > ----------------------------------------------------------------- > > Key: GTNSSO-27 > URL: https://issues.jboss.org/browse/GTNSSO-27 > Project: GateIn SSO > Issue Type: Bug > Affects Versions: 1.3.2.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 1.3.3.Final > > > - Configure portal with external IDP as in https://docs.jboss.org/author/display/GTNPORTAL36/SAML2#SAML2-Setupwithex... > - Create user in portal with password like aaa”aaa > - It won't be possible to login as this user on IDP side on http://www.idp.com:8080/idp-sig > Reason: IDP site in idp-sig.war application doesn't have specified encoding, so it uses ISO-8859-1 by default. Also FormAuthenticator is trying to use this encoding for decoding of request parameters. If we have password with characters not available in ISO-8859-1, user can't login. We need to use UTF-8 encoding in all places. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3101) Encoding issue when login with password containing non-ASCII characters

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3101?page=com.atlassian.jira.pl... ] Marek Posolda updated GTNPORTAL-3101: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/521 > Encoding issue when login with password containing non-ASCII characters > ----------------------------------------------------------------------- > > Key: GTNPORTAL-3101 > URL: https://issues.jboss.org/browse/GTNPORTAL-3101 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Beta02 > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.0.Final > > > Steps to reproduce: > - Login as root, Go to http://localhost:8080/portal/g/:organization:management:executive-board/o... and register user with password: aaa£aaa > - Logout as root and try to login as new user. Login won't be successful > Reason: Form for saving new user handles usecase correctly and it correctly save password aaa£aaa into Picketlink IDM DB. Problem seems to be during login as LoginServlet doesn't decode parameters from URL in UTF-8 . It seems that it's using ISO-8859-1 as password is decoded in LoginServlet with value: aaaÂ£aaa > Fix: We should trigger request.setCharacterEncoding("UTF-8") in LoginServlet to ensure that params will be decoded with UTF-8 and password will be correctly decoded as: aaa£aaa -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-27) Can't login through external IDP scenario with non-ascii password

by Marek Posolda (JIRA)

Marek Posolda created GTNSSO-27: ----------------------------------- Summary: Can't login through external IDP scenario with non-ascii password Key: GTNSSO-27 URL: https://issues.jboss.org/browse/GTNSSO-27 Project: GateIn SSO Issue Type: Bug Affects Versions: 1.3.2.Final Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 1.3.3.Final - Configure portal with external IDP as in https://docs.jboss.org/author/display/GTNPORTAL36/SAML2#SAML2-Setupwithex... - Create user in portal with password like aaa”aaa - It won't be possible to login as this user on IDP side on http://www.idp.com:8080/idp-sig Reason: IDP site in idp-sig.war application doesn't have specified encoding, so it uses ISO-8859-1 by default. Also FormAuthenticator is trying to use this encoding for decoding of request parameters. If we have password with characters not available in ISO-8859-1, user can't login. We need to use UTF-8 encoding in all places. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2917) NPEs thrown while accessing /portal context when JPP is being started

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2917?page=com.atlassian.jira.pl... ] Lucas Ponce updated GTNPORTAL-2917: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/gatein/gatein-portal/pull/520 (was: https://github.com/gatein/gatein-portal/pull/519) > NPEs thrown while accessing /portal context when JPP is being started > --------------------------------------------------------------------- > > Key: GTNPORTAL-2917 > URL: https://issues.jboss.org/browse/GTNPORTAL-2917 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final, 3.6.0.Beta01 > Reporter: Dominik Pospisil > Assignee: Lucas Ponce > Labels: JPP61-Test-dev > Fix For: 3.6.0.Final > > Attachments: jsf2-rf4-test.zip, jsf2-rf4-test.zip > > > JPP throws NPE if a client tries to access /portal context during server startup. The NPEs occur after the server logs "Registering web context: /portal" until the portal EAR is competely deployed. > Steps to Reproduce: > 1. start the server > 2. access /portal context while the server is being started > > Exceptions thrown: > 15:08:25,855 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/portal].[portal]] (http-/127.0.0.1:8080-1) Servlet.service() for servlet portal threw exception: java.lang.NullPointerException > at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:138) [exo.jcr.framework.web-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:] > at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.5.2.Final-redhat-4.jar:3.5.2.Final-redhat-4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:] > > 15:08:37,235 WARN [org.exoplatform.web.CacheUserProfileFilter] (http-/127.0.0.1:8080-1) An error occured while cache user profile: javax.servlet.ServletException: java.lang.NullPointerException > at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.5.2.Final-redhat-4.jar:3.5.2.Final-redhat-4] > at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.1-GA-redhat-1.jar:2.4.1-GA-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-2.jar:1.0.1.Final-redhat-2] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:] -- 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, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues June 2013