CAS doesn't have a problem with it, but it may expand more than you want. All of these hostnames would match:
https://english.dept.utah.edu/foo https://somehost.math.dept.utah.edu/b<https://somehost.english.dept.utah.edu/foo>ar https://ant.expands.the.asterisk.match.anything.dept.utah.edu/ Using regex would give more predictable results. If you have a finite set of departments: ^https://(english|math|whatever)\.dept\.utah\.edu/.* or allow any department, but don't allow hostnames below that: ^https://[^.]*\.dept\.utah\.edu\/.* (FYI: I haven't tested that one with CAS, but it *should* work) -- Eric Pierce Identity Management Architect Information Technology University of South Florida (813) 974-8868 -- [email protected] ________________________________ From: Bryan E. Wooten [[email protected]] Sent: Thursday, August 01, 2013 11:56 AM To: [email protected] Subject: [cas-user] Service Manager Wild cards Quick question: We are running CAS 3.4.12 with the JSON file Service Manager. I have a request to add service like this: https://*.dept.utah.edu/**<UrlBlockedError.aspx>. I am not sure how CAS will react to the first wildcard character. Thoughts? Thanks, Bryan -- 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
