Hello all,
I'm running into an issue with Qlik Sense (February 2023 Patch 5) and AD authentication. We have a user who has two AD accounts: manager.locationX and firstname.lastname.
When he logs into the hub, using his firstname.lastname account, the authentication succeeds, but the hub doesn't load. Closer inspection of the logs reveals the following:
| Proxy |
INFO |
Stop session for user 'BRD\manager.locationX' . Session id = 'c0dea074-66a4-fc18-7351-4f787c968bde' and all dependents will be deleted. |
| Repository |
ERROR |
Access was denied for User: 'BRD\manager.locationX', SessionId: 'c0dea074-66a4-fc18-7351-4f787c968bde', Hostname: '::ffff:10.20.30.66', Requested access types: '', OperationType: 'UsageDenied' |
| Proxy |
INFO |
User authenticated. User 'BRD\manager.locationX' used authentication method 'ticket' and got session 'c0dea074-66a4-fc18-7351-4f787c968bde' |
| Repository |
ERROR |
Access was denied for User: 'BRD\manager.locationX', SessionId: 'c0dea074-66a4-fc18-7351-4f787c968bde', Hostname: '::ffff:10.20.30.66', Requested access types: '', OperationType: 'UsageDenied' |
| Proxy |
INFO |
Syncing user attributes for user 'BRD\manager.locationX' |
| Proxy |
INFO |
Start session for user: 'BRD\manager.locationX' |
It seems the authenticated session continues using his account manager.locationX, with which he is logged into his laptop. This account doesn't have user rights, and the attempt is rightfully stopped by the Repository and Proxy.
Is this usual behaviour from Qlik Sense?
