A user that is in the Public role (essentially their user account is disabled) does not clearly see that they are restricted. When a user account is created on a newly deployed Proxeus instance, they are assigned to the Public role even though the default option seems to be "Creator" in the settings.
Steps to reproduce
Create a user account on a freshly installed Proxeus instance. Or create a user account, then as administrator set its role to "Public".
Expected behaviour
The user should be told that an administrator needs to upgrade their account for them to be able to access some parts of the Proxeus application.
Actual behaviour
Log in and try to modify the account details, e.g. changing your Name. You will get a cryptic error message, and in the logs, a 401 Unauthorized pops up.
A user that is in the Public role (essentially their user account is disabled) does not clearly see that they are restricted. When a user account is created on a newly deployed Proxeus instance, they are assigned to the Public role even though the default option seems to be "Creator" in the settings.
Steps to reproduce
Create a user account on a freshly installed Proxeus instance. Or create a user account, then as administrator set its role to "Public".
Expected behaviour
The user should be told that an administrator needs to upgrade their account for them to be able to access some parts of the Proxeus application.
Actual behaviour
Log in and try to modify the account details, e.g. changing your Name. You will get a cryptic error message, and in the logs, a 401 Unauthorized pops up.
Thanks to @javany for discovering this problem.