CAS 5.1.0-RC4 In-memory ticket registry still starting when using Hazelcast ticket registry

[Matt S.]

Hello,

We're testing CAS 5.1.0-RC4 and noticed that the in-memory ticket registry still seems to be starting when we configure CAS to use the Hazelcast ticket registry.

Configuration was done according to the documentation, linked here by adding the dependency and configuring the properties in cas.properties.

The following warning shows up in the logs even though the logs clearly show that an HZ ticket registry was setup prior to this point in the logs.

WARN [org.apereo.cas.config.CasCoreServicesConfiguration] - <Runtime memory is used as the persistence storage for retrieving and persisting service definitions. Changes that are made to service definitions during runtime WILL be LOST upon container restarts.>

...which shows up after the following line:

INFO [org.apereo.cas.ticket.registry.HazelcastTicketRegistry] - <Setting up Hazelcast Ticket Registry instance [HazelcastInstance{name='devcas5Tickets', node=[xx.xx.xx.xx]:5701}]>

It seems as if the bean called "ticketRegistry" that should be registered by HZ is either not being registered or recognized by the time CAS checks if it should load the default in-memory ticket registry.

Please advise.

Thanks,

Matt

[Misagh Moayyed]

This is quite simple. You are looking at the wrong log.

 

The warning is warning you about service definitions and the service registry. Not tickets.

 

--Misagh

--
- 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
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/0390f2cd-a47d-4e9d-aa39-7f66b705b63b%40apereo.org.

[Matt S.]

Sorry, I copied the wrong one.  Please see below.

WARN [org.apereo.cas.config.CasCoreTicketsConfiguration] - <Runtime memory is used as the persistence storage for retrieving and managing tickets. Tickets that are issued during runtime will be LOST upon container restarts. This MAY impact SSO functionality.>

[Misagh Moayyed]

It’s likely a bad or misplaced logging call; not that the registry is taking over HZ. Feel free to file an issue.

 

--Misagh

---

This email has been scanned for spam and viruses by Proofpoint Essentials. Click here to report this email as spam.

=

[Christian Schmidt]

Hi,

I just went through the logs of a new installation of 6.1 RC6 and found the same logging entry like Matt with Version 5.1.

2019-09-20 16:38:26,277 DEBUG [org.apereo.cas.config.HazelcastTicketRegistryConfiguration] - <Created Hazelcast map configuration for [DefaultTicketDefinitionProperties(cascade=false, storageName=serviceTicketsCache, storageTimeout=10, storagePassword=null)]>

...

2019-09-20 16:38:33,655 INFO [org.apereo.cas.util.CoreTicketUtils] - <Ticket registry encryption/signing is turned off. This MAY NOT be safe in a clustered production environment. Consider using other choices to handle encryption, signing and verification of ticket registry tickets, and verify the chosen ticket registry does support this behavior.>

Accoring to the logs HZ ist starting and according to netstat is is also running as expected.

I had a quick look at the soruces and there is no way around, that the function ticketRegistry() in the CasCoreTicketsConfiguration class is getting called after the HZ ticket registry is created

--> where can I, as mentioned by Misagh, report this as a Bug?