New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

extra attributes from Jasig Cas 3.5 #83

Open

Poil opened this issue Nov 1, 2014 · 1 comment

Poil commented Nov 1, 2014

Hi,

I'm unable to get extra_attributes from my Jasig Cas 3.5; with phpcas I've no problem, is there an incompatibility with Jasig CAS ?

Best regards,

josh7weaver commented Jun 8, 2018

This is an old question, but could be closed with this answer:

Seems there was at one time, however, after rubycas/rubycas-server#165 was merged along with https://github.com/rubycas/rubycas-client/pull/39/files on the client side, it appears the Ruby CAS server is sending attributes in jasig style per spec and the client should be able to consume both types of response. See more info in this currently outdated wiki page.

As of version 0.7.0, the CAS server is able to send back this extra information in authentication responses. Currently, however, only the RubyCAS-Client is able to read this additional data. Without modification, clients for other platforms will continue to only see the username. (Is this still true?)

Your phpcas client worked because it has a conditional statement that allows for different styles of extra_attributes: https://github.com/apereo/phpCAS/blob/master/source/CAS/Client.php#L3311

Hopefully this will help some poor soul in the future!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment