As the JS adapter has evolved, it now tries to add an iframe element to the document body during initialization.
When used like in the basic example as before, there will be an JS error, as the document body is not yet available.
So we've to wait until the document is loaded, thus the initialization is put in a function and the function will be called upon body.onload()
* poc of possible way to change form dynamically
* fixed detail routs
* Update src/components/form-access/FormAccess.tsx
Co-authored-by: Stan Silvert <ssilvert@redhat.com>
* Update src/components/form-access/FormAccess.tsx
Co-authored-by: Stan Silvert <ssilvert@redhat.com>
* Update src/components/form-access/FormAccess.tsx
Co-authored-by: Stan Silvert <ssilvert@redhat.com>
* added more form access and logic for Controller
* render switches for boolean types
* better render of `<Controller` wrapped components
* added isDisabled property
* added test
* small refactor
* fixed types
* TextArea doesn't support isDisabled
* when field is disabled, disable button as well
* added jsdoc
Co-authored-by: Stan Silvert <ssilvert@redhat.com>
* initial version of the role mapping create form
[marvel](https://marvelapp.com/prototype/f0e8fih/screen/72042619)
* fixed format
* changed to typeahead
* format
* group by
* review fixes
* added group and divider
* change name to realm name
- Add parameters idpAlias and idpUserId to the resource /{realm}/users and allow it to be combined with the other search parameters like username, email and so on
- Add attribute "federatedIdentities" to UserEntity to allow joining on this field
- extend integration test "UserTest"
When LDAP user federation is configured in read-only mode, it is not
possible to set required actions for users from LDAP.
Keycloak credential model allows for registering OTP devices when LDAP
ist configured with "Import Users" flag enabled. Registering OTP devices
needs to be done via the account management console and works as
expecetd. However, it fails, if a user has to register aN OTP device
during login (i.e. within the authentication flow), because the OTP Form
Authenticator tries to enforce OTP registration via setting the
corresponding required action for the user. That fails, because the user
is read-only.
To work around this, the required action is set on the authentication
session instead.
