December 2016 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNSSO-34) Support for CAS 4

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-34?page=com.atlassian.jira.plugin.... ] Juraci Paixão Kröhling closed GTNSSO-34. ---------------------------------------- Resolution: Done I actually think this was done already. I'm closing as "Done". > Support for CAS 4 > ----------------- > > Key: GTNSSO-34 > URL: https://issues.jboss.org/browse/GTNSSO-34 > Project: GateIn SSO > Issue Type: Feature Request > Reporter: Juraci Paixão Kröhling > Assignee: Marek Posolda > Fix For: 1.4.4.Final > > > With CAS 4.0, some changes were made which broke our support for CAS. So, a new component needs to be done, based on the existing component for 3.5, taking these changes into account. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-1805) add ability to send email on registration and x successive failures

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1805?page=com.atlassian.jira.pl... ] Marek Posolda reassigned GTNPORTAL-1805: ---------------------------------------- Assignee: Boleslaw Dawidowicz (was: Marek Posolda) > add ability to send email on registration and x successive failures > ------------------------------------------------------------------- > > Key: GTNPORTAL-1805 > URL: https://issues.jboss.org/browse/GTNPORTAL-1805 > Project: GateIn Portal > Issue Type: Feature Request > Components: Identity integration > Reporter: Prabhat Jha > Assignee: Boleslaw Dawidowicz > Priority: Optional > Fix For: 3.9.0.Final > > Attachments: README.txt, sendMailAfterInvalidLoginPatch.txt, sendMailAfterRegistrationPatch.txt > > > Please attach the patch based on your work at https://issues.jboss.org/browse/JBQA-4122. By default the feature should be turned off. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-1465) Being able to define permissions with recursive groups

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1465?page=com.atlassian.jira.pl... ] Marek Posolda reassigned GTNPORTAL-1465: ---------------------------------------- Assignee: (was: Marek Posolda) > Being able to define permissions with recursive groups > ------------------------------------------------------ > > Key: GTNPORTAL-1465 > URL: https://issues.jboss.org/browse/GTNPORTAL-1465 > Project: GateIn Portal > Issue Type: Feature Request > Components: Security > Affects Versions: 3.1.0-GA > Reporter: Noel Rocher > Fix For: 4.x > > > Meaning : give access to Managers where there's sub-groups as ITManagers, HRManagers ... all in only one permission definition > Managers > - ITManagers > - HRManagers > - ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

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

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2972?page=com.atlassian.jira.pl... ] Marek Posolda reassigned GTNPORTAL-2972: ---------------------------------------- Assignee: (was: Marek Posolda) > EPP+SP: Problem with LoginRedirectFilter reading POST parameters > ---------------------------------------------------------------- > > Key: GTNPORTAL-2972 > URL: https://issues.jboss.org/browse/GTNPORTAL-2972 > Project: GateIn Portal > Issue Type: Enhancement > Reporter: Marek Posolda > Fix For: 3.x > > > 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 was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2744) Changing page size in AbstractSerializablePageList should recreate underlying lazy list

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2744?page=com.atlassian.jira.pl... ] Marek Posolda reassigned GTNPORTAL-2744: ---------------------------------------- Assignee: (was: Marek Posolda) > Changing page size in AbstractSerializablePageList should recreate underlying lazy list > --------------------------------------------------------------------------------------- > > Key: GTNPORTAL-2744 > URL: https://issues.jboss.org/browse/GTNPORTAL-2744 > Project: GateIn Portal > Issue Type: Enhancement > Affects Versions: 3.5.0.Beta02 > Reporter: Marek Posolda > Priority: Minor > Fix For: 3.9.0.Final > > > It seems that if we have pageList of type AbstractSerializablePageList and we want to change the size of the page via setPageSize, we should recreate underlying lazyList. Currently underlying lazyList is not recreated, which means that it's not in line with pageList and still have old pageSize. > Example: > - I will create pageList of size 10 > - I will call pageList.setPageSize(6) -- this will update info of pageList, but underlying lazyList will still have bad info about pageSize > - I will call pageList.getPage(7). Now lazyList needs to load 20 items (all items from 30 to 39 and then all items from 40 to 49) instead of 6 items (items from 36 to 41). > Unit test will follow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-34) Support for CAS 4

by Marek Posolda (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-34?page=com.atlassian.jira.plugin.... ] Marek Posolda commented on GTNSSO-34: ------------------------------------- [~juraci.costa] Can we close this "out of date"? Or should I assign to you? Ideally I just want GTNSSO JIRAs to be cleared from the list of my open jiras :) > Support for CAS 4 > ----------------- > > Key: GTNSSO-34 > URL: https://issues.jboss.org/browse/GTNSSO-34 > Project: GateIn SSO > Issue Type: Feature Request > Reporter: Juraci Paixão Kröhling > Assignee: Marek Posolda > Fix For: 1.4.4.Final > > > With CAS 4.0, some changes were made which broke our support for CAS. So, a new component needs to be done, based on the existing component for 3.5, taking these changes into account. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues December 2016