Closed (fixed)
Project:
CAS
Version:
8.x-1.x-dev
Component:
CAS
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
24 Sep 2018 at 09:54 UTC
Updated:
15 Oct 2018 at 00:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
bkosborneWhy do you need a custom validation path? If your CAS server implements the CAS protocol appropriately, then the paths are all the same. What CAS server software are you using?
Comment #3
ieguskiza commentedHi there, the CAS server we use follows the protocol but also provides alternate options that allow more fine-grained authentication.
I agree it may sound too specific but at the very least I think there should be a PreValidateEvent, if only for consistency's sake since there already is a PreRedirectEvent as well.
Comment #4
ieguskiza commentedI uploaded a patch to showcase the proposed solution.
Comment #6
ieguskiza commentedApologies, the previous patch was not the correct one.
Comment #7
bkosborneI think the new pre validate event should handle all the customizations. We shouldn't add the ability to specify a unique validation URL in the admin config. I think the admin config should satisfy the needs of 90% of the CAS setups, and I don't think yours is a common one. The pre validate event can have a method to control the base URL and path.
Comment #8
ieguskiza commentedYeah that makes sense. I uploaded a patch where the event allows to modify both the path and the parameters. Let me know what you think.
Comment #10
ieguskiza commentedFixed the test and added a separate one for the new event.
Comment #11
upchuk commentedMade some small corrections. Nothing major.
Comment #12
bkosborneLooks good. I just modified the comments.
Comment #13
bkosborneOops empty patch
Comment #16
bkosborne