February 2015 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ] Juraci Paixão Kröhling resolved GTNSSO-28. ------------------------------------------ Assignee: Juraci Paixão Kröhling (was: Marek Posolda) Fix Version/s: 1.4.5.Final (was: 1.4.4.Final) Resolution: Done > realm is wrong adds an extra g in the realm name with OpenAM 11 > --------------------------------------------------------------- > > Key: GTNSSO-28 > URL: https://issues.jboss.org/browse/GTNSSO-28 > Project: GateIn SSO > Issue Type: Bug > Affects Versions: 1.4.0.Beta01 > Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11 > Reporter: Michael McKinsey > Assignee: Juraci Paixão Kröhling > Fix For: 1.4.5.Final > > > The realm name is coming up wrong with an extra g which I believe is causing the error #403x > https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0 > notice realm is ggatein > I found a reference to the extra g: > https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1... > It says: > // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing > String providerId = agentUrl + "/?Realm=g" + openSSORealm; > I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated GTNSSO-28: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1194717 > realm is wrong adds an extra g in the realm name with OpenAM 11 > --------------------------------------------------------------- > > Key: GTNSSO-28 > URL: https://issues.jboss.org/browse/GTNSSO-28 > Project: GateIn SSO > Issue Type: Bug > Affects Versions: 1.4.0.Beta01 > Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11 > Reporter: Michael McKinsey > Assignee: Marek Posolda > Fix For: 1.4.4.Final > > > The realm name is coming up wrong with an extra g which I believe is causing the error #403x > https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0 > notice realm is ggatein > I found a reference to the extra g: > https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1... > It says: > // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing > String providerId = agentUrl + "/?Realm=g" + openSSORealm; > I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ] Juraci Paixão Kröhling commented on GTNSSO-28: ---------------------------------------------- PR that solves the issue for 10.1 and later (including 12.0) without breaking 9.x https://github.com/gatein/gatein-sso/pull/8 > realm is wrong adds an extra g in the realm name with OpenAM 11 > --------------------------------------------------------------- > > Key: GTNSSO-28 > URL: https://issues.jboss.org/browse/GTNSSO-28 > Project: GateIn SSO > Issue Type: Bug > Affects Versions: 1.4.0.Beta01 > Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11 > Reporter: Michael McKinsey > Assignee: Marek Posolda > Fix For: 1.4.4.Final > > > The realm name is coming up wrong with an extra g which I believe is causing the error #403x > https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0 > notice realm is ggatein > I found a reference to the extra g: > https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1... > It says: > // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing > String providerId = agentUrl + "/?Realm=g" + openSSORealm; > I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

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 NEW to ASSIGNED > 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 > > 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, 2 months

1
0
0 / 0

[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 commented on GTNSSO-34: ---------------------------------------------- PR for GateIn : https://github.com/gatein/gatein-portal/pull/927 > 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 (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3575) LoginServlet still has left-overs from removal of Disabled Users feature

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3575?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3575: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1191310 > LoginServlet still has left-overs from removal of Disabled Users feature > ------------------------------------------------------------------------ > > Key: GTNPORTAL-3575 > URL: https://issues.jboss.org/browse/GTNPORTAL-3575 > Project: GateIn Portal > Issue Type: Bug > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > The "Disabled Users" feature was removed from the 3.8 branch, but a code related to it was not removed entirely from the LoginServlet, causing problems in SSO scenarios. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3575) LoginServlet still has left-overs from removal of Disabled Users feature

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3575?page=com.atlassian.jira.pl... ] Juraci Paixão Kröhling updated GTNPORTAL-3575: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/928 > LoginServlet still has left-overs from removal of Disabled Users feature > ------------------------------------------------------------------------ > > Key: GTNPORTAL-3575 > URL: https://issues.jboss.org/browse/GTNPORTAL-3575 > Project: GateIn Portal > Issue Type: Bug > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > The "Disabled Users" feature was removed from the 3.8 branch, but a code related to it was not removed entirely from the LoginServlet, causing problems in SSO scenarios. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3575) LoginServlet still has left-overs from removal of Disabled Users feature

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNPORTAL-3575: ------------------------------------------------- Summary: LoginServlet still has left-overs from removal of Disabled Users feature Key: GTNPORTAL-3575 URL: https://issues.jboss.org/browse/GTNPORTAL-3575 Project: GateIn Portal Issue Type: Bug Reporter: Juraci Paixão Kröhling Assignee: Juraci Paixão Kröhling The "Disabled Users" feature was removed from the 3.8 branch, but a code related to it was not removed entirely from the LoginServlet, causing problems in SSO scenarios. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-34?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated GTNSSO-34: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1192531 > 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 (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[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 commented on GTNSSO-34: ---------------------------------------------- PR submitted: https://github.com/gatein/gatein-sso/pull/7 > 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 (v6.3.11#6341)

9 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 February 2015