CAS Module Without phpCAS
metzlerd - March 10, 2009 - 05:43
| Project: | CAS |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
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?
#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.