You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
In a couple of services, there's the check for a explicit root user, via userId === "root". Is this correct? I would have expected that the root user is disabled and the services are used via respective authenticated users in their role.
The text was updated successfully, but these errors were encountered:
@jzakotnik If it is correct depends on a criterion I suppose.
In the email service, root can create, read, update, and delete email addresses. On the other hand, frontend doesn't expose a way for root user to read or modify these. I think it reflects conflicting design decisions, and as you wrote, root access in the email service to user's addresses should be disabled.
Provisioning and migration are necessary.
Frontend uses the check to i.a. limit the actions root can do (root can't create projects).
In a couple of services, there's the check for a explicit root user, via
userId === "root"
. Is this correct? I would have expected that the root user is disabled and the services are used via respective authenticated users in their role.The text was updated successfully, but these errors were encountered: