As part of the agreement of granting a customer offline license usage, the customer is required to regularly upload User Assignment log files. This essentially replicates the user assignment data which is sent to Qlik in a manual process.
Applicable Products:
Qlik Sense Enterprise on Windows
QlikView
Licensed with a long term offline license.
⚠️ FYI: All information regarding user subject (user information) is hashed using SHA256 to prevent Qlik from accessing the original data. (The information is encrypted both in transit and at rest). ⚠️
Data transmitted in the log files:
User Assignment Log File Content
Data Stored In Logs
|
Data Element
|
Comment
|
Sample Data
|
|
Signed License Key
|
|
See above
|
|
Allotment name
|
Professional / Analyzer
|
“professional”
|
|
Subject
|
Domain / User ID;
if this an add or delete transaction. By delete the subject will be removed immediately. An internal id will be used to secure sync to other deployments using the same Signed License Key. The internal id will disappear within 60 days after a delete transaction.
(This information is stored for all assigned users until such a time that the assignment is deleted at which point it is deleted. The information is used for synchronizing assignments across deployments in order to facilitate the single-license-multi-deployment scenario. It is encrypted in transit and at rest.)
|
“acme\bob” user name included in hashed form in the log files and will show as something like:
“a24a2f2b67c5e051bcb6cd2d7a9f7ebe”
|
|
User agent
|
Build by the License service version (operating system) and Product (e.g. QSEfW, QCS, QSEfE, ADBI, Qlik Core, QV)
|
Licenses/1.6.4 (windows) QSEfW
|
|
Source
|
Hashed ID to make each deployment unique, e.g. a Qlik Sense Enterprise on Windows and a Qlik Sense Enterprise on Kubernetes will have different Source ID's
|
fbe89d02-6d24-4595-915e-c52ce76f2195
|
|
Sync metadata
|
Versioning information about the subjects and list of subjects to manage the synchronization process.
To review the information, copy the message content of the log and decode it using a base64 decoder.
|
{ "source": "my assignments",
"bases": [{ "license": "1234 1234 1234 1234",
"version": 0 }], "patches": [{
"instance": "", "version": 0,
"license": "1234 1234 1234 1234", "allotment": "analyzer", "subject": \\generated4, "created": "2019-04-18T10:01:35.024031Z" }
|
Related Content:
