bug #4847
Updated by Andreas Müller over 6 years ago
This is a general problem with the vaadin framework deployed on a CDM Server running multiple CDM Instances. Since a Vaadin session is connected (one-one) to a specific UI, any attribute set in the session of the UI will be accessible for all running CDM Instances. This is clearly not always desirable for all cases. E.g. the various services that are registered as session attributes, should be mapped to the host-port-cdm instance, so that access to these are restricted to the UI running on a particular CDM Instance. The specific case of authentication has been dealt with in #4844, but this needs to be generalised.