clustering with HazelcastStorageService
cantor.2 at osu.edu
Wed Apr 27 18:42:43 EDT 2016
On 4/27/16, 6:39 PM, "users on behalf of Jonathan Johnson" <users-bounces at shibboleth.net on behalf of jsjohnson at unicon.net> wrote:
>The Shibboleth storage service allows any subsystem to create its own context in the service, so as long as you know the names of the contexts, you can configure the maps. When this was written, there was not a list of these available, which might have changed (a reference would be nice).
Nobody asked us either; but, they're really implementation details, or have been, it's never been something that anybody suggested would be useful to document.
It is one step above documenting cookie names in my mind, so I'm not predisposed to do it, but if there's some benefit...
If the issue is being able to avoid conflicts, we have always stipulated that people should use context names that are URIs or package-style with domains for any extension use cases.
More information about the users