as discussed here https://github.com/qwc-services/qwc-oidc-auth/issues/2 , i moved this issue from oidc to data service
...
We use qwc services (qwc-docker as well as qwc-services on Kubernetes). We started with the db-auth-service for authorization and switched to the qwc-oidc-auth later. Now the field type for username doesn't match for the "edit_user_field" to automatically update the editing user.
I think the matter is the different definition of identity.
For qwc-oidc-auth the identity is defined as:
identity = {'username': username, 'groups': groups}
app.logger.info(identity)
# Create the tokens we will be sending back to the user
access_token = create_access_token(identity)
as discussed here https://github.com/qwc-services/qwc-oidc-auth/issues/2 , i moved this issue from oidc to data service ... We use qwc services (qwc-docker as well as qwc-services on Kubernetes). We started with the db-auth-service for authorization and switched to the qwc-oidc-auth later. Now the field type for username doesn't match for the "edit_user_field" to automatically update the editing user.
I think the matter is the different definition of identity. For qwc-oidc-auth the identity is defined as:
For qwc-db-auth the identity is defined as:
Can data service be changed to handle both formats of identity?