We have changed the way the rsd admin role is assigned to users. Since version v 2.4.0 the account id of rsd admin user need to be defined in the admin_account table. This is done as security improvement measure.
During the development it is more suitable to automatically add first person to have rsd_admin role.
I would like to propose the following approach for development mode:
Add RSD_ENV variable to authentication service
When RSD_ENV=development is defined in the .env file all of the authentication services (at lease SURCconext and Local) should assign rsd_admin role to first user logged in (if admin_account is empty add users account id).
@cmeessen, @fembau and @jcohen02 Do you agree to this proposal or maybe you have some other suggestion how to make rsd_admin role easily accessible during the development?
We have changed the way the rsd admin role is assigned to users. Since version v 2.4.0 the account id of rsd admin user need to be defined in the admin_account table. This is done as security improvement measure.
During the development it is more suitable to automatically add first person to have rsd_admin role. I would like to propose the following approach for development mode:
RSD_ENVvariable to authentication serviceRSD_ENV=developmentis defined in the .env file all of the authentication services (at lease SURCconext and Local) should assign rsd_admin role to first user logged in (if admin_account is empty add users account id).@cmeessen, @fembau and @jcohen02 Do you agree to this proposal or maybe you have some other suggestion how to make rsd_admin role easily accessible during the development?