Il 24/07/2017 08:04, Fabio Martelli ha scritto:
Il 21/07/2017 18:57, Sébastien Beaudlot ha scritto:
Hi
Do you have any backend configured for ticket registry ? This may be
the easiest way to achieve your goal.
Hi Sébastien, thank you for your prompt reply.
No I have not a backend configured
Can anybody let me know, How ticket cleanup works in clustered CAS
environment?
Thank you in advance.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
-
Can anybody let me know, How ticket cleanup works in clustered CAS
environment? We are using JPA Ticket Registry.
Thank you in advance.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation webs
A Scheduled Job runs on all nodes (normally DefaultTicketRegistryCleaner),
which obtains a lock using the underlying LockingStrategy (e.g.
JpaLockingStrategy),
and performs the ticket cleaning using the underlying TicketRegistry
implementation (e.g. JpaTicketRegistry).
All other nodes running
Thank you for your reply. I have one more query, If cleanup activity
initiated by one server then will other server get permision to insert
record into TICKETGRANTINGTICKET and SERVICETICKET tables?
On Wednesday, July 26, 2017 at 4:59:38 PM UTC+5:30, robertoschwald wrote:
>
> A Scheduled Job run
Of course you can add tickets while cleaner is running, assuming you properly
configured the cas.ticket.registry.jpa.dialect property (e.g. using
org.hibernate.dialect.MySQL5InnoDBDialect).
> Am 26.07.2017 um 13:52 schrieb shruti halgekar :
>
> Thank you for your reply. I have one more query,
Hi everyone,
I'm using gradle overlay 5.0.x and everything was fine until I tried to
change application.yml location,
I'm doing this:
java -jar -Xmx2048M cas/build/libs/cas.war
--cas.standalone.config='${project.rootDir}/etc/cas/config' (tried with
and without the single quotes
Looks like t
I have created a war overlay project that I have deployed on my local eclipse
IDE tomcat environment. When I try to deploy the same war to our production
tomcat the war explodes and claims to start up. However the spring banner is
never displayed and I receive a 404 for the cas url through the b
Tomcat 7 does not support Servlet Spec 3.1, which is required by CAS 5.
You need to upgrade to Tomcat 8.5.x (supersedes the 8.0.x line).
Note the special considerations documented for external Tomcat
configurations here:
https://apereo.github.io/cas/5.1.x/installation/Configuring-Servlet-Contain
Thank you david, yes I upgraded my server to 9.0.0.M22 and it deployed
correctly.
I do find it interesting that in eclipse using tomcat 7 it deployed correctly.
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of David Curry
Sent: Wednesday, July 26, 2017 11:21 AM
To: cas-user@ap
I know this thread is a couple months old, but we just went to production with
this on CAS v5.0.4 and we were having the same issue and of course this is my
first place to look. But I found on the Duo documentation that I needed to add
the following after the iframe in the casDuoLoginView.html f
11 matches
Mail list logo