If restart is necessary for some client property change, that sounds rather
like a bug. Could you please file a JIRA that includes your exact scenario,
clustering setup and Keycloak version?
--Hynek
On Tue, Oct 24, 2017 at 7:57 PM, <mcwitters(a)winsupplyinc.com> wrote:
I'm sorry if this has been asked before or is readily available
information, but I haven't been able to locate a definitive answer.
Under what circumstances must the Keycloak server(s) be restarted for
changes to take effect? I spent a lot of time due to new or updated client
redirect URIs not taking effect until a restart occurs and not expecting to
have to. I've not problem with the necessity of it, but just wanted to know
for sure when it is required.
Thanks in advance.
Mike W.
************************************************************
*********************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
************************************************************
*********************************
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
--Hynek