So I've been experimenting with the Hazelcast service registry streaming. The file for the service is created when this is enabled. cas.serviceRegistry.stream.enabled=true It does appear that the service is created in memory only when the serviceRegistry streaming is disabled. cas.serviceRegistry.stream.enabled=false
On Thursday, October 24, 2019 at 8:21:47 AM UTC-4, M. Daley wrote: > > Testing out the SAML idp support and found that a service file is > generated for this endpoint each time the server boots. > > Each boot results in a new id, and evaluation order and filename. > > Example: > File: RegexRegisteredService-8549171654979440640.json > > serviceId: https://{CAS-URL-REMOVED}/cas/idp/profile/SAML2/Callback.* > name: RegexRegisteredService > id: 8549171654979440640 > description: SAML Authentication Request Callback > > > It doesn't seem to be checking if a service has already been created that > matches the endpoint. Even if I have a wildcard service file, a new > service file will be generated. > > Is this expected behavior, and how would that work with something like the > git service registry? > > Thanks, > > M. Daley > > -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/9e1b7d56-d6ed-4dbe-a029-2cbddc5027ad%40apereo.org.
