Hello,

> what you mean is that this configuration key is only present in the doc, 
not in the configuration file????
Yup. ${configurationKey} is not a working mechanism, *don't put 
${configurationKey}.cluster.instanceName in your cas.properties file, 
instead, put this cas.ticket.registry.hazelcast.cluster.members.*

${configurationKey} is just the way of CAS like to document their 
properties...

- Andy

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/54bf4d6d-afaf-40a9-8d19-66923bdb858a%40apereo.org.

Reply via email to