-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Role Error for new User #482
Comments
also delete the AD_User_Roles when a role is deleted. metasfresh/metasfresh-webui-api-legacy#482
note: implemented. Additionally, the AD_User_Roles records will be deleted when the AD_Role is deleted. |
rolled on w101 |
[#905](metasfresh/metasfresh-webui-frontend-legacy#905) Add/ Remove KPI Widget functionality for User Dashboard [#486](metasfresh/metasfresh-webui-api-legacy#486) dashboard: support "position" when PATCHing a dashboard item [#482](metasfresh/metasfresh-webui-api-legacy#482) No Role Error for new User [#481](metasfresh/metasfresh-webui-api-legacy#481) Sticky empty Filter in modal overlay. [#485](metasfresh/metasfresh-webui-api-legacy#485) backend: refactor sticky filters [#949](metasfresh/metasfresh-webui-frontend-legacy#949) Board: adding a card as last is not user friendly] [#469](metasfresh/metasfresh-webui-api-legacy#469) Picking prototype (v2) [#923](metasfresh/metasfresh-webui-frontend-legacy#923) Packageables window: up/down arrows are working weird [#945](metasfresh/metasfresh-webui-frontend-legacy#945) dashboard: react to websocket notifications [#933](metasfresh/metasfresh-webui-frontend-legacy#933) Disable quick actions button while running the action (v2) me.45
IT |
Is this a bug or feature request?
Bug (low prio)
What is the current behavior?
Sometimes a freshly created user, is not directly useable after creation. When login then the error "No Roles" is returned.
Which are the steps to reproduce?
a) Login as Admin. Open The window User. Create a new User as System User w/ Login and Password. Logout. Try to Login as new User. Must fail because no Role is assigned. Wait for the error message. Now login again as Admin. Go to window Role. Assign the newly created user to a Role. Logout. Try to Login as newly created User. The error from before about the "No Role" still persists. Do a Swagger Cache reset, and you can login again.
What is the expected or desired behavior?
Shall be able to login w/o cahce reset.
The text was updated successfully, but these errors were encountered: