[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ]
Marek Posolda updated GTNSSO-28:
--------------------------------
Fix Version/s: 1.4.3.Final
(was: 1.4.2.Final)
> 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.3.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.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNSSO-8) Unit tests
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNSSO-8?page=com.atlassian.jira.plugin.s... ]
Marek Posolda updated GTNSSO-8:
-------------------------------
Fix Version/s: 1.4.3.Final
(was: 1.4.2.Final)
> Unit tests
> ----------
>
> Key: GTNSSO-8
> URL: https://issues.jboss.org/browse/GTNSSO-8
> Project: GateIn SSO
> Issue Type: Enhancement
> Affects Versions: 1.1.1-GA
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Fix For: 1.4.3.Final
>
>
> Current support of unit tests is not good. There are couple of dummy unit tests, but they are disabled as they require server to be running before running tests. It will be needed to provide integration with some well-known solution (Arquillian, Cargo, JBoss unit...) and provide more unit tests for SSO component.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNPORTAL-3493) Membership just added, disappears
by Boubaker Khanfir (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3493?page=com.atlassian.jira.pl... ]
Boubaker Khanfir updated GTNPORTAL-3493:
----------------------------------------
Affects Version/s: 3.5.9.Final
> Membership just added, disappears
> ---------------------------------
>
> Key: GTNPORTAL-3493
> URL: https://issues.jboss.org/browse/GTNPORTAL-3493
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.9.Final
> Reporter: Boubaker Khanfir
> Attachments: plidm-ldap-membership-disappear.zip
>
>
> I attach a new unit test for a bug that we met in GateIN 3.5 (PL IDM 1.4.4).
> This one shows how we can add a membership and just after that it disappears.
> In this file [idm-configuration.xml|https://github.com/gatein/gatein-portal/blob/3.5.x/...], the comment :
> {quote}
> <!-- if "associationMembershipType" option is used and this option is set to true
> then Membership with MembershipType configured to be stored as PicketLink IDM association
> will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
> For RW LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
> However for DB only and/or Read-only LDAP, it's recommended to not map anything here -->
> {quote}
> is not good and have to be like this:
> {quote}
> <!-- if "associationMembershipType" option is used and this option is set to true
> then Membership with MembershipType configured to be stored as PicketLink IDM association
> will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
> For LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
> However for DB only, it's recommended to not map anything here -->
> {quote}
> What changes in this comment ?
> The LDAP RW or ReadOnly have to get the same behavior using this parameter and we should map all LDAP groups in "ignoreMappedMembershipTypeGroupList".
> I think it's better to force/compute this parameter in OrganizationService instead of giving the ability to do it manually. The other solution is to modify OrganizationService Impl to deal with such a use case but I prefer the first choice.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months