6.1.0-RC4 SAML Callback endpoint created each boot.

[M. Daley]

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

[M. Daley]

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