[
https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin....
]
Marek Posolda commented on GTNSSO-28:
-------------------------------------
yes, you're right. This was needed for OpenAM 9 and 10, which are currently supported
versions. For OpenAM 11, you can either workaround and build gatein-sso in your
environment, or if you have time, you can send PR with more proper fix, which will work
in both OpenAM 9,10 and 11 . I think proper fix will need to add another init parameter
(either with OpenAM version or name of the realm for ProviderID part).
For build gatein-sso, you just need java 6 (or later) and maven 3.0.3 (or later) and run
just "mvn clean install" from "gatein-sso" directory. If it
doesn't work, feel free to create another JIRA and please attach details about your
environment (java version, maven version, OS etc).
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
Priority: Blocker
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)