The authentication backend used in the engine is case insensitive (e.g. ldap)
I login with a userId with all uppercase characters, e.g. "PETER".
And create collections or private entities
I don't see the collections if I login with an all lowercase userId, "peter" although I'm the same user.
I should see the same resources being the same user.
- any authorizations should not depend on the case of the userId/Name input by the user, we should always resolve the actual userId from the authentication backend
Authorizations in the engine are as well case-sensitive, so we shouldn't implement different behavior there yet. But we can resolve this issue by normalizing the userId on successful login/authentication.