We're running 3.5.1 with Google Apps integration in production. Setting it up was no different than with the old version that we were running prior to the upgrade (3.4.3.1). The only attribute that we're releasing to Google is 'uid', which contains the username.
If the signature validation fails and you know that the private key is correct, maybe the certificate that you're validating against is the wrong one. Best regards, -- Carlos. -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Friday, 08 February, 2013 11:18 To: [email protected] Subject: Re: [cas-user] "login credentials could not be verified" with Google SSO > I assume from other messages I've seen in this user group that Google > Apps integration does work. Has anyone else run into this? Has anyone > tried this on CAS 3.5.1? I have not, nor am I aware of confirmation from anyone else. It's concerning because we have upgraded to OpenSAML 2.x as of the 3.5.1 upgrade [1]. I may be able to jury-rig an integration test in our dev environment and report back. I would love if someone else in the community would save me the effort by confirming Google Apps Integration in 3.5.1+. Thanks, M [1] https://issues.jasig.org/secure/ReleaseNote.jspa?projectId=10007&version=1 2182 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
