This might briefly help for CAS 4 (but the idea is the same for CAS 3): http://jasig.github.io/cas/4.0.x/installation/Service-Management.html
It determines the sort order of services tried in ascending mode. If the first entry that is tried matches your service, then the enumeration will stop, which means if the first/previous entry matches a wider selection of urls than the second/next, the configuration for the latter will never be activated, which is something I suspect you're dealing with now. -----Original Message----- From: Richard Wiseman [mailto:[email protected]] Sent: Wednesday, April 8, 2015 12:46 AM To: [email protected] Subject: [cas-user] Releasing attributes based upon the service URL Hi, I've a working instance of CAS that successfully returns certain attributes to any service that uses it. I now want to start returning attributes selectively based upon the service URL. I've duplicated the (sole) RegexRegisteredService bean in my deployerConfigContext.xml file, modifying only its ID, evaluationOrder and allowedAttributes list. However, I'm finding the resulting behaviour somewhat unpredictable! I haven't been able to work out what the significance of the evaluationOrder is. Are the beans tried in order, stopping when one matches? Or do they somehow build a list of attributes to release if multiple beans' serviceId regular expressions match? The main symptom is that no attributes seem to be released when I have more than one RegexRegisteredService bean, regardless of whether one or both match the serviceId. Is there some documentation that explains all this? Thanks, Richard -- 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
