Example configuration templating

[Maryna Bardadym]

Could someone please help provide me good example of the configuration of a JASIG cas overlay with error templating?

When I try to get an error page I always get a JSON instead of the error page.

I would like to see a working application.yml file.

[Ray Bon]

Maryna,

You are refering to JASIG cas. The JASIG name has not been in use for many years. 

You can use https://github.com/apereo/cas-overlay-template or https://github.com/apereo/cas-initializr

You can see examples of properties files in these [prior version] build guides https://paulchauvet.github.io/deploying-cas/ and https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html

To customize a ui page, see https://fawnoos.com/2024/11/12/cas72x-common-userinterface-changes/ there are other blog entries for earlier versions.

Please describe your setup and steps you took that resulted in a json response instead of the built in error page?

Here is the beginning of my application.yml.

The variables and secrets are set in an application.properties file that is deployed with the war file by jenkins. You can of course, put all values in the yml file.

# Application properties that need to be
# embedded within the web application can be included here

cas:
  server:
    scope: ${server.scope}
    name: https://${cas.server.scope}
    prefix: ${cas.server.name}/cas
  audit:
    slf4j:
      use-single-line: true
  authn:
    accept:
      users: ${users.static.list}
    attribute-repository:
      stub:
        id: stub
        attributes:
          domain: uvic.ca
      ldap[0]:
        attributes:
          description: description
        bind-credential: ${authn.ldap.bind-credential}

Ray

On Thu, 2024-11-14 at 04:26 -0800, Maryna Bardadym wrote:

You don't often get email from marynab...@gmail.com. Learn why this is important