Yes I did.
When visiting https://localhost:8443/cas/login
The site comes up fine.
On Thu, Mar 15, 2018, 8:57 AM Matthew Uribe <matthew.ur...@aims.edu> wrote:
> Did you setup the keystore?
>
> On Thursday, March 15, 2018 at 9:55:14 AM UTC-6, Jono Jono wrote:
>>
&
14 mars 2018 23:55:33 UTC+1, Jono Jono a écrit :
>>
>> I am following the instructions to bring this up here:
>> https://github.com/apereo/cas-overlay-template
>>
>> With the default setup if I run build.sh it does not come up and there
>> are no error messages.
>
I am following the instructions to bring this up here:
https://github.com/apereo/cas-overlay-template
With the default setup if I run build.sh it does not come up and there are
no error messages.
When visiting 8443, nothing is running there.
Now if I delete the cas.properties file, it does
or security-group was for CAS's hazelcast, so I had to use
hazelcast.xml to make sure I knew the values in there.
On Wednesday, February 28, 2018 at 11:58:40 AM UTC-8, rbon wrote:
>
> Jono,
>
> Try this log4j2 item,
>
>
I'm having trouble understanding caching ticket registries. This chart in
particular:
https://apereo.github.io/cas/5.2.x/planning/High-Availability-Guide.html#recommended-architecture
shouldnt cas-2 be pointing at a cache? is the diagram incorrect?
--
- Website: https://apereo.github.io/cas
-
I have done that. The log shows when I authenticate. And it shows stuff
about hazelcast's heartbeat. But it does not say anything about how the key
is store or where I can find it.
Should I see something particular?
On Wed, Feb 28, 2018 at 9:15 AM, Ray Bon <r...@uvic.ca> wrote:
> Jono
I'm using CAS 4.2 with Hazelcast, but I'm unable to verify that CAS is
writting to Hazelcast. Can you point me to how I would determine the data
that CAS is writing to the cache?
Here is the hazelcast part of my properties file:
hz.mapname=tickets
hz.cluster.logging.type=slf4j
