locale per service

22 views

Skip to first unread message

Pablo Vidaurri

unread,

Jan 26, 2023, 11:54:51 PM1/26/23

to CAS Community

I see this in docs for CAS 6.5.x and newer but not in 6.3 or 6.4. I assume since it does not work in 6.3 it was introduced in 6.5. I know not everything is documented so not sure if this was available before 6.5

locale definition per service

{

"@class" : "org.apereo.cas.services.RegexRegisteredService",

"serviceId" : "^https://www.example.org",

"name" : "MyTheme",

"locale" : "de",

"id" : 1

}

Petr Bodnár

unread,

Jan 29, 2023, 1:41:34 AM1/29/23

to CAS Community, Pablo Vidaurri

Hi Pablo,

I think I can confirm your expectations: a Git blame on an ancestor of `RegexRegisteredService` (BTW deprecated in favor of `CasRegisteredService ` since 6.6.x) shows the "locale" property was introduced in 6.5.x and not any sooner, in this concrete commit:

https://github.com/apereo/cas/commit/859d66873a893a8673db2991bb6ae89f4115ef66

(Also note you can use just "https://www.example.org" in "serviceId", as the whole region of the incoming "service" parameter is matched by the default (regex) matching strategy. This also means that for example "https://www.example.org/somepath" won't get matched with your example service.)