Hi,
Following this:
https://apereo.github.io/cas/5.1.x/installation/User-Interface-Customization-Themes.html
I did:
- From the cas v5.1.x github repo, I copy the `*/static/themes/apereo*`
directory with all it's content into my `*/resources/cas-theme-custom*`
directory,
- Add a
Hi,
I'm in the verge of theming my CAS 5.1.x instance, I'm reading in the
official documentation here:
https://apereo.github.io/cas/5.1.x/installation/User-Interface-Customization-CSSJS.html
It commands to *add new .css file not .scss file*, I could infer from this
that we shouldn't work with
What do you mean by redirecting the CAS to this address? Do you mean to
specify a "logoutUrl" parameter in the services register? I tried this
entry "logoutUrl" :
https://dev-540472.oktapreview.com/app/kidev540472_oktaidpend_1/exkd5ymrh7ZmIRjiH0h7/slo/saml
however, to no avail.
What should
You can specify a logout url with cas customization.
El domingo, 7 de enero de 2018, azki escribió:
> What do you mean by redirecting the CAS to this address? Do you mean to
> specify a "logoutUrl" parameter in the services register? I tried this
> entry "logoutUrl" :
Thanks Misagh. I have removed that line. I am having the following errors
in the log:
2018-01-08 09:20:00,652 DEBUG
[org.apereo.cas.authentication.DefaultAuthenticationEventExecutionPlan] -
2018-01-08 09:20:00,653 DEBUG
[org.apereo.cas.config.CasCoreAuthenticationConfiguration] -
2018-01-08
Hello everyone,
Happy new year.
I have an issue I don't succeed to find out a solution with proxying.
I'm running the latets 5.2 graddle overlay and have an apache reverse proxy
in front of the CAS instance.
WAN <==> FRONT (HTTPS) <==> CAS (AJP)
The SSL is provided by Let's encrypt. I made a
"theme" : "classpath:apereo",
The solution is very simple, add “classpath:” as theme name prefix.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this