So, if you are using CAS v2, you also get back the following in the
response?

        <cas:user>sD2d9dioPB3CS5VN97fZS61rmBg=</cas:user>

Any chance the service in your registry is marked with anonymous=true? 

> -----Original Message-----
> From: Chris Peck [mailto:[email protected]]
> Sent: Wednesday, May 28, 2014 6:15 AM
> To: [email protected]
> Subject: [cas-user] upgrade to CAS server 3.5.2.1 breaks rubyCAS and
older
> phpCAS clients
> 
> I'm running a test CAS server v3.5.2.1 and most of our clients work
fine,
> we've run into two exceptions:
> 
> Ruby-CAS-Client https://github.com/rubycas/rubycas-client running RHEL
Linux,
> ruby 2.0.0p353 phpCAS 1.3.2, php version 5.3.8 Solaris 10
> 
> From the debug log for phpCAS, I see the following, that value matches
up
> with what phpCAS phpCAS::getUser() returns
> 
>
<saml1:NameIdentifier>sD2d9dioPB3CS5VN97fZS61rmBg=</saml1:NameIdentifier>
> 
> (Note - I'm not sure what this is, so I made some minor changes to the
above
> values).  I'm guessing there is some sort of encoding going on here that
may
> be what causes ruby & older version of php to get a bit confused? I get
the
> same value return if I use CAS 2.0 instead of SAML 1.1.  All the
attributes
> that get returned look correct as well.
> 
> I've run the same php script on Linux and Solaris 10 (php 5.3.10) and it
> works just fine.  I'm not too worried about the phpCAS client, as that
works,
> but, the RubyCAS client is used by someone else here, and, this is a
sticking
> point to finalize the upgrade.
> 
> Has anyone else seen this sort of thing? Any ideas on what may cause
this?
> Thanks,
> Chris Peck
> College of William and Mary
> 
> PS - both of the above clients work fine with our current production CAS
> v3.4.5
> 
> 
> --
> 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

Reply via email to