December 2012 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2771) Ensure that generated rememberme token is really unique

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2771?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2771: ---------------------------------------------------- mposolda(a)redhat.com made a comment on [bug 887972|https://bugzilla.redhat.com/show_bug.cgi?id=887972] See https://issues.jboss.org/browse/GTNPORTAL-2771 > Ensure that generated rememberme token is really unique > ------------------------------------------------------- > > Key: GTNPORTAL-2771 > URL: https://issues.jboss.org/browse/GTNPORTAL-2771 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.0.Final > > > Currently we are generating random rememberme tokens based on random int number (random.nextInt()). In systems with millions or many thousands login, this discriminator is not enough. > We should improve it and fix it either by: > 1) Ensure that generated token is really unique. In system with many logins the random number may not be unique enough, so we need to add other info (like System.currentTimeMillis() or counter or both...) > 2) In case that token already exists, we should generate other one instead of refresh the current one. > Maybe combination of both approaches would be best :-) -- 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-2771) Ensure that generated rememberme token is really unique

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2771?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-2771: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=887972 > Ensure that generated rememberme token is really unique > ------------------------------------------------------- > > Key: GTNPORTAL-2771 > URL: https://issues.jboss.org/browse/GTNPORTAL-2771 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.0.Final > > > Currently we are generating random rememberme tokens based on random int number (random.nextInt()). In systems with millions or many thousands login, this discriminator is not enough. > We should improve it and fix it either by: > 1) Ensure that generated token is really unique. In system with many logins the random number may not be unique enough, so we need to add other info (like System.currentTimeMillis() or counter or both...) > 2) In case that token already exists, we should generate other one instead of refresh the current one. > Maybe combination of both approaches would be best :-) -- 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-2771) Ensure that generated rememberme token is really unique

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2771?page=com.atlassian.jira.pl... ] Marek Posolda updated GTNPORTAL-2771: ------------------------------------- SourceForge Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000A7KOF&sfdc.ove... > Ensure that generated rememberme token is really unique > ------------------------------------------------------- > > Key: GTNPORTAL-2771 > URL: https://issues.jboss.org/browse/GTNPORTAL-2771 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.0.Final > > > Currently we are generating random rememberme tokens based on random int number (random.nextInt()). In systems with millions or many thousands login, this discriminator is not enough. > We should improve it and fix it either by: > 1) Ensure that generated token is really unique. In system with many logins the random number may not be unique enough, so we need to add other info (like System.currentTimeMillis() or counter or both...) > 2) In case that token already exists, we should generate other one instead of refresh the current one. > Maybe combination of both approaches would be best :-) -- 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-2771) Ensure that generated rememberme token is really unique

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2771?page=com.atlassian.jira.pl... ] Marek Posolda updated GTNPORTAL-2771: ------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.6.0.Final Resolution: Done Issue fixed in 'master' and in '3.5.x' branch > Ensure that generated rememberme token is really unique > ------------------------------------------------------- > > Key: GTNPORTAL-2771 > URL: https://issues.jboss.org/browse/GTNPORTAL-2771 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.0.Final > > > Currently we are generating random rememberme tokens based on random int number (random.nextInt()). In systems with millions or many thousands login, this discriminator is not enough. > We should improve it and fix it either by: > 1) Ensure that generated token is really unique. In system with many logins the random number may not be unique enough, so we need to add other info (like System.currentTimeMillis() or counter or both...) > 2) In case that token already exists, we should generate other one instead of refresh the current one. > Maybe combination of both approaches would be best :-) -- 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-2754) Priority ignored during navigation import for modes merge and overwrite.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2754?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-2754: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=887954 > Priority ignored during navigation import for modes merge and overwrite. > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2754 > URL: https://issues.jboss.org/browse/GTNPORTAL-2754 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Labels: EPP6.0-Test-Dev > Attachments: navigation-import-priority-fix.patch > > > Looks like in NavigationImporter navigation priority cannot be updated once created. -- 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-2776) Update the portal to better handle mobile devices

by Matt Wringe (JIRA)

Matt Wringe created GTNPORTAL-2776: -------------------------------------- Summary: Update the portal to better handle mobile devices Key: GTNPORTAL-2776 URL: https://issues.jboss.org/browse/GTNPORTAL-2776 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Mobile Reporter: Matt Wringe Assignee: Matt Wringe -- 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-2754) Priority ignored during navigation import for modes merge and overwrite.

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2754?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-2754: ------------------------------------- Labels: EPP6.0-Test-Dev (was: ) > Priority ignored during navigation import for modes merge and overwrite. > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2754 > URL: https://issues.jboss.org/browse/GTNPORTAL-2754 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Labels: EPP6.0-Test-Dev > Attachments: navigation-import-priority-fix.patch > > > Looks like in NavigationImporter navigation priority cannot be updated once created. -- 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-2754) Priority ignored during navigation import for modes merge and overwrite.

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2754?page=com.atlassian.jira.pl... ] Nick Scavelli updated GTNPORTAL-2754: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/299 > Priority ignored during navigation import for modes merge and overwrite. > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2754 > URL: https://issues.jboss.org/browse/GTNPORTAL-2754 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Nick Scavelli > Attachments: navigation-import-priority-fix.patch > > > Looks like in NavigationImporter navigation priority cannot be updated once created. -- 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-2754) Priority ignored during navigation import for modes merge and overwrite.

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2754?page=com.atlassian.jira.pl... ] Nick Scavelli reassigned GTNPORTAL-2754: ---------------------------------------- Assignee: Nick Scavelli > Priority ignored during navigation import for modes merge and overwrite. > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2754 > URL: https://issues.jboss.org/browse/GTNPORTAL-2754 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Attachments: navigation-import-priority-fix.patch > > > Looks like in NavigationImporter navigation priority cannot be updated once created. -- 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-2775) lack of logging when error "org.gatein.pc.api.NoSuchPortletException: No such portlet xxx" occurs

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2775?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-2775: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=878272 > lack of logging when error "org.gatein.pc.api.NoSuchPortletException: No such portlet xxx" occurs > ------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-2775 > URL: https://issues.jboss.org/browse/GTNPORTAL-2775 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > > Some times the following errors occur: > ERROR [STDERR] (ajp-10.5.38.13-8009-85) org.gatein.pc.api.NoSuchPortletException: No such portlet /xxxxx > .headerImports > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:113) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker._getPortlet(ProducerPortletInvoker.java:202) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker.getPortlet(ProducerPortletInvoker.java:119) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.federation.impl.FederatedPortletInvokerService.getPortlet(FederatedPortletInvokerService.java:110) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.federation.impl.FederatingPortletInvokerService.getPortlet(FederatingPortletInvokerService.java:231) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.gatein.pc.portlet.PortletInvokerInterceptor.getPortlet(PortletInvokerInterceptor.java:83) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.application.UIPortlet.setState(UIPortlet.java:939) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIPortlet(PortalDataMapper.java:246) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:402) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:314) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:419) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:314) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:419) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:314) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:419) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:314) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:419) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:314) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.buildUIContainer(PortalDataMapper.java:419) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:314) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIContainer(PortalDataMapper.java:291) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.util.PortalDataMapper.toUIPage(PortalDataMapper.java:320) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.page.UIPageBody.getUIPage(UIPageBody.java:148) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.page.UIPageBody.setPageBody(UIPageBody.java:78) > 2012-11-09 10:26:51,903 ERROR [STDERR] (ajp-10.5.38.13-8009-85) at org.exoplatform.portal.webui.portal.UIPortal.refreshUIPage(UIPortal.java:238) > ... > It indicates that the logged portlet somehow is not recognized by EPP. To fix this issue we have to drop the portlet from the problematic page and re-add it again. > However, the errors don't show what page is having this problem. We have to identify the pages by checking the timestamps. > We would like the EPP code could add more logging here to show the specific page info if such error pops up. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues December 2012