- If this is enabled when user is created user should be prompted to change password
- Fix is to switch from Steve user create to Norman user create
- #2524
- Also fixes issue where description was not saved if there was no custom model
- the api does not allow the signed in user to deactivate/delete themselves
- ensure that we don't show these options by checking user isn't the signed in one
- ideally this should be done via the api by removing the 'remove' link for the signed in user
- when deleting multiple resources, and confirm enabled, prompt for a random resource name for confirmation
- random resource name will always be visible, for the case where there are more than 5 to delete
- Improved process to declare which resource requires confirmation
- i10n'd some text
- Update Users list with actions
- Add User create/edit page
- Add User details page
- Brought over user/principal global role validation from ember world
- edit yaml didn't show yaml because a schema wasn't defined
- edit yaml didn't save because the update link wasn't correct
- saving yaml didn't update the models in the stores
- not all input elements were passed the mode when looking at the config view
- the select and array list components had visual issues in view mode (didn't show the values and the buttons didn't line up well)
- cloning failed due to cleanForNew not accounting for the template property
https://github.com/rancher/dashboard/issues/2111#issuecomment-777066167
Constraints were failing to clone because cleanForNew didn't remove `this.constraint` which casued the save method to attempt to save the existing constraint instead of creating a new constraint.
This enables models to be able to create their own cleanForNew method to remove custom props if necessary.
rancher/dashboard#2341
- Add groups page with table to the auth product
- Allow user to assign roles to groups previously without roles or edit
groups with existing roles
Comments
- I haven't added any special ux for the case where there's no auth
provider and therefore no groups
- ./components/GlobalRoleBindings.vue will be updated when the same
component is used for assign global roles to a user principal
- ./components/GlobalRoleBindings.vue ln 139 Couldn't create a binding
without the generateName metadata property. Have given this a
`ui-` prefix. Is this correct?
- In order to determine which global roles are bound to each principal
(so we can filter by principals that have them).. we go out and fetch
ALL role bindings. Is this too costly?
- On the groups page the 'refresh' button is quite big, we should
consider reducing this