In PR #246117, we realized that the internal MW client is exposed by using the getScopedClient. We should use the createInternalRepository instead. Otherwise anyone using it from the TM where there is no user, will get an unauthorized error. The solution of the PR was to disable the spaces extension.

DoD

• Expose a truly internal MW client by using createInternalRepository .
• Check if the alerting plugin needs the spaces extension when using the internal client. If yes, let the alerting plugin create a variant of the internal client with the spaces extension enabled. An alternative would be for the alerting plugin to pass the namespaces attribute to the find method if needed.