Posted by metzlerd on March 10, 2009 at 5:43am
Jump to:
| Project: | CAS |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I am considering reimplementing the CAS module without phpCAS. The reasoning behind this is as follows:
* Reduce the known compaitibility issues with differing versions of phpCAS
* Improve ease of installations (no extra libraries to download).
* Lets me leverage drupal database for ticket storage for features such as single sign-out.
* Possibility of enabling proxy ticket generation api for accessing portal servlets.
I'm interested in what module users think about this proposal? Good idea? Bad Idea? Indifferent?
Comments
#1
I know this is old, but I'm a big fan of leveraging other people's work. So if you think this can be handled by submitting patches to phpCAS then I'd do that. Otherwise, if rewriting is the only way of implementing the features you want then I think go for it.
#2
Generally I agree. Have you had any luck in submitting your own patches? The other issue you commented on today suggested that phpCAS couldn't support the newer 3.x features to get user name.
Anyway... thanks for the input. It's never too late.
#3
I've never submitted patches to phpCAS. I suggested to my co-worker that he submit a patch, but he hasn't felt too motivated. :) Interestingly at the moment I think we are looking towards cas wrapped in shibboleth as the solution for attribute release.
#4
I just read an email to the CAS list and it seems that the phpCAS version in trunk supports samlValidate for attribute release.
#5
Good idea. currently I do not manage how to install PHPCAS, whereas I need CASE on my site.
.
#6
After using phpCAS 1.1RC1 for a bit I'd like to suggest that it be required for 2.x of this module. It gives us attribute release handling and the api has changed enough that supporting both current and earlier versions would be a pain. I'd be tempted to only support CAS 3 server logout paramater of service also . It seems that is the place where all the different cas flavors have merged. I'm willing to throw some time into this if your ready to work on it some more.
#7
I won't require a release candidate, so lets wait until full release of 1.1 before we make a stance on that. Right now it's pretty easy to wrap if is_callable around the required functions so it works properly.
#8
Sure I understand I was thinking only for 2.x because it's not released yet either. By the issue queue it seems 1.1 is supposed to be released very soon.
#9
I agree with to implement CAS Module without PHPCas hehehe ^^, so we do not need to download file Php CAS again ^^
#10
I just wanted to let the Drupal-CAS community know that development on phpCAS has really ramped up this year now that Joachim Fritschi has taken over management of the project. In 2009 there were 15 commits to phpCAS where as so far in 2010 there have been 138. Right now we are in the process of releasing phpCAS-1.2.0 (a few RCs have been tagged so far).
Here are a few of the changes in the new version:
Changes in version 1.2.0RC2
Improvements
* add callback hooks during authentication and single sign-out [PHPCAS-76] (Adam Franco)
Changes in version 1.2.0RC1
Improvements
* add hasAttribute($key) and getAttribute($key) [PHPCAS-43] (Adam Franco)
* add unit tests for cas 2.0 attribute support [PHPCAS-88] (Adam Franco)
* add deprecation messages to the logout functions with an url parameter [PHPCAS-85] (Joachim Fritschi)
Bug Fixes
* fix public/private modifier for some functions [PHPCAS-87] (Joachim Fritschi)
Changes in version 1.2.0-beta1
Bug Fixes
* fix redirection behind a proxy. [PHPCAS-78] (Alex Barker)
* remove the bogus setCasServerCert() function and clean up the curl ssl settings [PHPCAS-84] (Joachim Fritschi)
Improvements
* mark the logout functions with an url parameter a deprecated [PHPCAS-85] (Joachim Fritschi)
* add public/private modifier for all vars and functions [PHPCAS-77] (Joachim Fritschi)
* add a testing framwork that implement on and offline testing capabilities [PHPCAS-66] (Adam Franco)
* add RFC compliant cookie storage for the proxy() mode. [PHPCAS-54] (Adam Franco)
* removal of the domxml compatibility lib [PHPCAS-72] (Matthew Brooks, Joachim Fritschi)
* add support for attributes for the cas_2.0 protocol [PHPCAS-43] (Joachim Fritschi)
* removal of unused code and comments [PHPCAS-63] (Joachim Fritschi)
* fix static function warnings for php 5.x [PHPCAS-46] (Joachim Fritschi)
The attribute support and login/single-sign-out hooks added to phpCAS-1.2.0 should help address some of the issues mentioned in the initial issue comment.
#11
This clearly isn't going to happen on the 6.x-2.x branch, and given that phpCAS has stabilized quite a bit, I suggest we not pursue this further.