Arve Knudsen
cb62e69997
Chore: Convert API tests to standard Go lib ( #29009 )
...
* Chore: Convert tests to standard Go lib
Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
Co-authored-by: Will Browne <wbrowne@users.noreply.github.com>
2020-11-13 09:52:38 +01:00
Alexander Zobnin
8505d90768
Admin: New Admin User page ( #20498 )
...
* admin: user page to react WIP
* admin user page: basic view
* admin user page: refactor, extract orgs and permissions components
* admin user: change sessions actions styles
* admin user: add disable button
* user admin: add change grafana admin action
* user admin: able to change org role and remove org
* user admin: confirm force logout
* user admin: change org button style
* user admin: add confirm modals for critical actions
* user admin: lock down ldap user info
* user admin: align with latest design changes
* user admin: add LDAP sync
* admin user: confirm button
* user admin: add to org modal
* user admin: fix ConfirmButton story
* admin user: handle grafana admin change
* ConfirmButton: make styled component
* ConfirmButton: completely styled component
* User Admin: permissions section refactor
* admin user: refactor (orgs and sessions)
* ConfirmButton: able to set confirm variant
* admin user: inline org removal
* admin user: show ldap sync info only for ldap users
* admin user: edit profile
* ConfirmButton: some fixes after review
* Chore: fix storybook build
* admin user: rename handlers
* admin user: remove LdapUserPage import from routes
* Chore: fix ConfirmButton tests
* Chore: fix user api endpoint tests
* Chore: update failed test snapshots
* admin user: redux actions WIP
* admin user: use new ConfirmModal component for user profile
* admin user: use new ConfirmModal component for sessions
* admin user: use lockMessage
* ConfirmButton: use primary button as default
* admin user: fix ActionButton color
* UI: use Icon component for Modal
* UI: refactor ConfirmModal after Modal changes
* UI: add link button variant
* UI: able to use custom ConfirmButton
* Chore: fix type errors after ConfirmButton refactor
* Chore: revert Graph component changes (works with TS 3.7)
* Chore: use Forms.Button instead of ActionButton
* admin user: align items
* admin user: align add to org modal
* UI: organization picker component
* admin user: use org picker for AddToOrgModal
* admin user: org actions
* admin user: connect sessions actions
* admin user: updateUserPermissions action
* admin user: enable delete user action
* admin user: sync ldap user
* Chore: refactor, remove unused code
* Chore: refactor, move api calls to actions
* admin user: set user password action
* Chore: refactor, remove unused components
* admin user: set input focus on edit
* admin user: pass user into debug LDAP mapping
* UserAdminPage: Ux changes
* UserAdminPage: align buttons to the left
* UserAdminPage: align delete user button
* UserAdminPage: swap add to org modal buttons
* UserAdminPage: set password field to empty when editing
* UserAdminPage: fix tests
* Updated button border
* Chore: fix ConfirmButton after changes introduced in #21092
Co-authored-by: Torkel Ödegaard <torkel@grafana.com>
2020-01-13 17:10:19 +01:00
gotjosh
4181b30b75
API: Add createdAt and updatedAt to api/users/lookup ( #19496 )
...
* API: Add `createdAt` and `updatedAt` to api/users/lookup
In the past, we have added both `updatedAt` (#19004 ) and `createdAt` (#19475 ) to /api/users/:id
Turns out, api/users/lookup uses the same DTO for both. This fixes the serialization of both `createdAt` and `updatedAt`for this endpoint.
Also, adds a test to ensure no further regressions.
* Updated API documentation
2019-09-30 20:54:09 +01:00
Rafael George
e1b2bf711d
API: Add createdAt field to /api/users/:id ( #19475 )
...
It would help for auditing purposes to have the user's created date exposed via the API along with the other fields already exposed via the API.
2019-09-28 12:12:33 +01:00
gotjosh
fa007423e3
API: Add updatedAt to api/users/:id ( #19004 )
...
* API: Add `updatedAt` to api/users/:id
This adds the timestamp of when a particular user was last updated to
the `api/users/:id` endpoint.
This helps our administrators understand when was the user information last
updated. Particularly when it comes from external systems e.g. LDAP
2019-09-11 13:43:05 +01:00
Daniel Lee
193d468ed3
admin: adds paging to global user list
...
Currently there is a limit of 1000 users in the global
user list. This change introduces paging so that an
admin can see all users and not just the first 1000.
Adds a new route to the api - /api/users/search that
returns a list of users and a total count. It takes
two parameters perpage and page that enable paging.
Fixes #7469
2017-02-13 12:59:36 +01:00
