On Tue, 2017-05-09 at 09:41 +0200, Oliver Lietz wrote: > > There is the assumption that if such a mapping is available the > > underlying service user is available as well - which unfortunately > > is > > wrong. In this sense we could also remove the whole concept again > > and > > simply assume that if the JCR resource provider is available, the > > service user is created. It's the same shaky assumption but just > > simpler :) > > AFAIR (I'm on holidays and have no time to check) the mapping is > registered > only when the service/system user is present. I had problems in > integration > tests where system users materialized after service user mapping > config was > processed and they failed.
Looking at the code I don't see this happening. I agree that we should make it work properly. Robert
