Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jan 10, 2023 3:05:12 AM
Dec 11, 2019 5:07:01 PM
The License Monitor acquires license data from the Qlik Sense Repository Service (QRS) through QRS API calls. The requests to these end-points are by default made by the user running the Qlik Sense services, but the related data connections may have been configured to run with a custom user.
The user executing the API calls must fulfill two requirements;
Assign RootAdmin role to the user running Qlik Sense services
This is most often the only required action, since the license monitor app by default relies on user running Qlik Sense services.
Run monitor app connections with customer RootAdmin account.
NOTE: This set is only required if a custom data connection user is required to comply with local security policies.
Use a custom RootAdmin account for the Data Connections that start with monitor_apps_REST_*
Confirm that UDC filter include account used for data connections
Thank you so much, this worked for me.
Had been facing this exact issue for the past couple of days and then I added RootAdmin role to the service account which caused License Monitor application to reload successfully.
Got these access issues after installing new Qlik Sense servers (Febr 2024) and did not make sense why this one would fail. This initially fixed my reloads.
Although adding the RootAdmin role works this is not necessary and way to much rights, the AuditAdmin role is more than enough for access to the data connection.
Roles: SecurityAdmin, ContentAdmin and DeploymentAdmin work to.
The HubAdmin role does not have the appropriatie permissions to read License_*
If any Admin role assigned to the service user is a security issue.
Create a Security rule so the service user is permitted Read the Resource License_*
Also I think this has to be fixed within the product, now the service user is by default not able to access license information. And everybody has to figure out why the reload fails.