Subject: Grouper Users - Open Discussion List
- From: Gagné Sébastien <>
- To: "Bryan E. Wooten" <>, <>
- Subject: RE: [grouper-users] CASifying Grouper
- Date: Wed, 3 Apr 2013 14:58:38 -0400
- Authentication-results: sfpop-ironport02.merit.edu; dkim=neutral (message not signed) header.i=none
CAS returns the user ID that logged in. This ID must match the subject ID configured in your sources.xml so it can do a lookup
I assumed you also modified your UI’s build.xml to include CAS, and CAS’s build.properties ?
Here , in yale-cas-auth/build.properties, I had to add a parameter to my sso.validate.url to it doesn’t returns the domain name because we use a homemade .NET CAS server,
e.g. : sso.validate.url="https://devcas.umontreal.ca/cas/serviceValidate.ashx?noDomain=true
Do you get an error message in grouper_error.log ?
DO you have the standard CAS auth server ?
I am trying to CASify Grouper using the JASIG CAS Java client. I have read these instructions:
I think all that is really necessary is to fix the struts-config.xml action path /callLogin to go to home.do.
Then remove the security constraints from the web.xml.
And finally add the CAS filters to the web.xml.
When I hit Grouper from my browser I get redirected to my CAS login as expected. But after login I get the populateIndex.do page with a login link. Click the login link just stays on the populateIndex.do page.
Prior to CASifying I added my subjectID to the Wheel Group.
There is one comment in the first link I did not understand:
“Ensure the REMOTE_USER value that is returned from CAS is configured as one of the subject identifiers in the sources.xml:”
The sample they gave was for a jdbc source and I am using AD as a source.
Any help appreciated.
- [grouper-users] CASifying Grouper, Bryan E. Wooten, 04/03/2013
- <Possible follow-up(s)>
- RE: [grouper-users] CASifying Grouper, Gagné Sébastien, 04/03/2013
Archive powered by MHonArc 2.6.16.