This is using docker because it is the easiest and fastest way for me to test
it. However, you can use it as a base to build the app and test configurations
as you go. I left a lot of stuff out as including them would defeat the
purpose of explaining the configuration for the style and were
Great, finally you got it, so is this your build only for docker?
https://github.com/dannymk/cas-dynamic-style
On Sunday, May 17, 2020 at 5:07:07 AM UTC+5:30, CanaryJudge wrote:
>
> I put together a small backup copy of the working version here:
>
I put together a small backup copy of the working version here:
https://github.com/dannymk/cas-dynamic-style
> On May 16, 2020, at 4:17 PM, 'Daniel Maldonado' via CAS Community
> wrote:
>
> OK, through a lot of trial and error I figured out where to put the files.
> NOT in the source and NOT
OK, through a lot of trial and error I figured out where to put the files.
NOT in the source and NOT compiling it into the final war. It is more of a
runtime configuration option
which was very hard to figure out.
I will have to put together a small project to make sure no one else suffers
Yes, yet again, that thread implies that the “skeleton_in_ID.properties”
belongs in the “src/main/resources/*.properties” directory.
Which implies that it needs to be compiled into the war before it is found.
Why would “dynamic themes” need to be included in the source?
That is not dynamic in
The new error is similar to this
https://groups.google.com/a/apereo.org/forum/#!topic/cas-user/dPf36An-qyU
Check that full thread, CAS is expecting theme.properties file.
if you are editing heavily then this is obvious in CAS, and Yes CAS
documentation needs a reincarnation! indeed :-).
This can’t be this difficult. I am actually very surprised that it has taken
this long to configure such an important project. If I ever get this working I
am going to have to put together some instructions for a newbie as the current
ones leave a lot to be desired in the form of examples :-)
Ok, at the end of the error it says "cannot be located" so might be
path/permission issue?, make sure
/etc/cas/templates/ is accessible by tomcat, also instead of
"file:///etc/cas/templates" try "file:/etc/cas/templates"
IF you are still getting errors, enable DEBUG mode in log4j2.xml, you
Just changed the value to what you specified below and got the same error:
2020-05-16 14:04:15,369 WARN
[org.apereo.cas.services.web.RegisteredServiceThemeResolver] -
It is almost it is ignoring the “cas.view.template-prefixes…” directive in the
cas.properties file.
> On May 16, 2020, at
Can you try with this variable?
cas.view.template-prefixes[0]=file:///etc/cas/templates
On Monday, May 11, 2020 at 8:20:30 AM UTC+5:30, CanaryJudge wrote:
>
> CAS Version: 6.2.0-SNAPSHOT
>
> Following the directions at:
>
I am comfortable doing this however it is very suspect to have to BUILD the
project EVERY time I want to create a new theme.
There are some properties in this section:
https://apereo.github.io/cas/6.1.x/ux/User-Interface-Customization-Themes.html
@Matthieu Marc
Thanks for the info, looks like there are some changes in the path for 6.2
version, i found all the files in 2 jar files
properties files present in below jar
cas-server-webapp-resources-6.2.0-SNAPSHOT.jar
All default CSS / JS and HTML files are in
After having build your instance with gradle, you will find in
build/overlays/bootWar/cas/WEB-INF/lib all jar files used by your instance.
I am using tomcat embedded implementation, maybee jar are in another place.
You will find this jar file cas-server-webapp-resources-6.1.5.jar (or
another
13 matches
Mail list logo
