* initial version of oidc
* fixed fetch and added missing fields
* fixed file upload
* added scopse
* added details
* added disable action and save
* updated to use new design based on discovery response
* new design
* set default value
* added tests
* fixed tests
* fixed labels
* changed direction to up
* upgrade cypress
* fixed delete now has dialog
* also check "unAssign"
* client type no longer required
* providers and group changes
* grp creation working
* moved create realm button ouside the dropdown
* sped up test and added cleanup
* Revert "moved create realm button ouside the dropdown"
This reverts commit e2076a5305808417de910ba8fada8e528e5c356a.
* make test re-runnable
* removed un needed navigation
* Fix misformed Cypress config for GitHub Action
* cleanup after test
* fixed cleanup
* temporary removed this test
* also remove user "new"
* try adding a wait for CI
* get different modal id
* add {force: true} to modal functions
* mv grp search last and ignore 401
* try using cy.get and disable video for testing
* add back video artifacts
Co-authored-by: mfrances <mfrances@redhat.com>
Co-authored-by: Jon Koops <jonkoops@gmail.com>
Co-authored-by: jenny-s51 <jshandel@redhat.com>
Restoring the original realm key provisioning process due to undesirable behaviour when using
on demand provisoning under load (duplicate keys created).
* email tab wip
* save username and pw info on auth toggle
* add email tab
* remove comments
* remove log stmt
* add help text
* adjust styles
* format
* fix conflicts and address PR feedback
* add back ref on reply to display name
* rebase and fix conflicts
* prevent save without sender email
* add className prop to formpanel
* only query realms endpoint once
currently the realm list query is expensive and we only need it once.
* fixed refresh issues
* fixed tests
* fixed imports
* fixed types
* removed strange non code
* reload instead
* added more realm tests
- add ForbiddenPage class for the assertion at the selenium test
- add assertion to selenium test
- GET requests for localization texts require at least one role for the realm
- Make GET requests for localization texts public, to display the admin UI correctly, even if the role view-realm is missing
when building product documentation
* Add the two referenced, but (so far) missing files to include,
* Define the attributes expected by metering labels
Signed-off-by: Jan Lieskovsky <jlieskov@redhat.com>