keycloak

There was an error where someone was trying to sign up using the thirdparty recipe and postgres rejected the query cause of value too long for type character varying(128) - and in the thidparty table, only the third_party_user_id column has 128 chars limit.

Error log reference:

[https://app.zenhub.com/files/231921809/8968d6d6-bcdd-48d8-aa60-fd556e934acd/download](https://app.zenhub.com/files

https://sonarcloud.io/summary/overall?id=sirixdb_sirix

We will need a page with documentation on how to set up a client in Keycloak using public open-id connect. For more information about this feature see: #91

Describe the bug

From the current admin console, it is possible to implement role-based policies with the following requests being issued:

{type: "role", logic: "POSITIVE", decisionStrategy: "UNANIMOUS", name: "Test policy",…}
decisionStrategy: "UNANIMOUS"
logic: "POSITIVE"
name: "Test policy"
roles: [{id: "dcd91634-b0d2-4656-b68b-a00acc1060fx"}]
0: {id: "dcd91634-b0d2-4656-b68b-

consent_screen_text is available on the keycloak_openid_client_scope resource, but it's missing from keycloak_openid_client.
It is settable on keycloak:

Hi, I am using this amazing plugin with Vue 2 + Composition API.
The problem is - $keycloak not available in context.
In setup(props, context), in context.root there is no information about $keycloak.

The only one way to solve this is on creating a Vue instance, create a watcher, which "sync" results from the $keycloak to my store and then, I will have an information in the setup, but it's o