Baron,
When you say 'update config', do you mean the build config or the cas
properties?
For the latter you could 'edit on the server'.
The missing dependenc[y|ies] may be the result of things like beta packages
being remove or moved to different repos.
You can find the package somewhere on
I know this is ancient, but we have an instance of CAS 3.4.11 deployed for a
specialized internal use[*]. The problem is, I recently decided to update its
config after not touching it for a very long time, but when I ran 'mvn clean
package' in my maven overlay work directory it fails with
Thanks mike.
This may not be the cleanest solution, but it works and will be easy to
maintain accross CAS upgrades.
I just configured jdbc audit, and a trigger to update my users table.
delimiter //
CREATE TRIGGER COM_AUDIT_TRAIL_on_insert_update_users_datelastlogin
AFTER INSERT ON
Hello all,
I found what may be a bug (in a library).
After configuring jdbc audit and starting cas for the first time, I got
the following error (see full exception below).
Caused by: java.sql.SQLSyntaxErrorException: You have an error in your
SQL syntax; check the manual that corresponds
I have configured my xx.com domian and now I have to support yy.com by the
same CAS server . Where do I need to do the changes ?
Regards,
Amit
On Fri, Sep 25, 2020 at 4:38 PM Christophe Delcour <
christophedelc...@gmail.com> wrote:
> thank you for the quick response ;-)
> here are the modules
thank you for the quick response ;-)
here are the modules added in the build.gradle:
implementation
"org.apereo.cas:cas-server-support-json-service-registry:${casServerVersion}"
implementation
"org.apereo.cas:cas-server-support-ldap:${project.'cas.version'}"
implementation
You need that in build.gradle :
implementation
"org.apereo.cas:cas-server-support-json-service-registry:${casServerVersion}"
And that in cas.properties :
cas.service-registry.json.location=file:///etc/cas/services
Can you check?
--
- Website: https://apereo.github.io/cas
- Gitter
Hello,
I am trying to install Apereo CAS 6.3 under Tomcat 9 but I have a problem.
My service is not recognised and in my logs, I have these 2 lines of
warning:
WARNING [https-jsse-nio-443-exec-4]
javax.persistence.spi.PersistenceProviderResolverHolder$DefaultPersistenceProviderResolver.log
