Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi, I'm using the Qlik Dev APIs to grab a user that exists in our Microsoft Entra (Azure AD) and create it in our Qlik Cloud. I can do it by making a POST request to "/v1/users". But then I need to assign them to Groups and I'm not seeing how I can do it.
The "/v1/users" allows me to assign the user to a Role but not a Group, and with the "/v1/groups", I can only view, create, patch, delete, etc said groups, not add a user to them.
Is there a way for me to add a user to a certain Group using the Qlik Dev APIs?
Group membership is determined by the Idp at the time of login. The group that the user belongs to come in the claim from the provider.
Group claims are not enabled by default in Qlik Cloud, you need to turn them on un QMC/settings on a tenant by tenant basis.
You also need to ensure your IdP configuration includes group claims.
Once that is all configured you can assign groups to have various authorisations in the tenant such as space permissions.
Group membership is determined by the Idp at the time of login. The group that the user belongs to come in the claim from the provider.
Group claims are not enabled by default in Qlik Cloud, you need to turn them on un QMC/settings on a tenant by tenant basis.
You also need to ensure your IdP configuration includes group claims.
Once that is all configured you can assign groups to have various authorisations in the tenant such as space permissions.
Nothing to add to Jonny's comment, but I am interested in why you wish to pre-provision the groups @marcelinoa ? Is there a reason you need them before the user session?
@DaveChannon I think it's a very specific situation of our client. Not everyone has yet used or accessed the Qlik envirenment, or may not do so, but it is still vital that they receive alerts from certain reports, but if the user has not yet accessed they don't get groups assigned to them, and won't receive the alerts.
But he will have them login just to "activate" the user since that seems to resolve the issue.
OK, so you have one other option and that is to use a JWT IdP to impersonate a login of the user. This will associate the user with their groups prior to login, but it's something you'd need to manage and run from your side (or via automations with custom code blocks).