Certainly, it would be nice. Feel free to submit a PR please.
Hi,
At the moment it is not possible to configure the TcpDiscoverySpi br/>localPort, it will always start ignite on the default port 475000... I br/>want to start ignite on a different port due to firewall-rrestrictions.
I can configure cas to check for ignite instances on different ports, br/>but it can't actually launch it's own build-in ignite serverr on a port br/>of my choosing. <
It would be nice if localPort could be exposed as a property.
Unless I have missed something completely... can I still override the br/>ignite-config.xml somewhere??
Cheers,
Stephan
-- br/>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
--- br/>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 post to this group, send email to cas-...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/57FB42D9.1000004%40cosmos.esa.int.
For more options, visit https://groups.google.com/a/apereo.org/d/optout.