In etc/cas/config/cas.properties:
cas.theme.paramName: theme
cas.theme.defaultThemeName: skeleton
spring.thymeleaf.cache=false
cas.view.templatePrefixes[0]: file:///etc/cas/templates
cas.messageBundle.baseNames=classpath:/skeleton_in_ID.properties,classpath:
messages
Help me on this issue.
Thanks Curtis, the problem is resolved in the site configuration (nginx).
--
- 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 message because you are
Hi,
I tried to customize the display based on the guidelines from
https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties.html#views
with the theme "*skeleton*" name stored in:
*(workspace)* /opt/cas/workspace/cas-overlay-template
etc/cas/config/skeleton_in_ID.properties ->
I have attached server and deployerConfigContext xml files here.
thanks.
On Wednesday, September 26, 2018 at 5:48:36 PM UTC+5:30, Arun R U wrote:
>
> Hi,
>
> I have configured CAS in my local machine with LDAP, and deployed in the
> tomcat server.
> And I have integrated this CAS application
Thanks, Arnold. There are options in the management app to input a Service
Provider Name Qualifier and Name Qualifier, but no option to disable it.
Providing a blank name yields the serviceId/entityID in the NameQualifier
and SPNameQualifier in the NameID portion of the SAML response by
Hi,
I have configured CAS in my local machine with LDAP, and deployed in the
tomcat server.
And I have integrated this CAS application with my application with
different port configured tomcat server.
And it is successfully worked without the SSL enabled.
And I have generated the SSL keys and
You need to provde the Host or X-Forwarded-Host header, like this example
describes:
https://www.nginx.com/resources/wiki/start/topics/examples/likeapache/
This lets the backend web server know it's being reverse proxied.
On Tuesday, September 25, 2018 at 4:52:22 PM UTC-4, Fahmi L. Ramdhani
Hi,
Authentication handlers are called depending on the passed credentials. For
a delegated authentication, a ClientCredentials is created which triggers
the ClientAuthenticationHandler.
Are you sure your new authentication handler supports ClientCredentials?
Thanks.
Best regards,
Jérôme
On