Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Deallocate a token for deleted user

Hi,

This question has been discussed before but hasn't been fully solved.

Is this a bug? Is there a solution for that issue?

This is the thread - deallocate a token for deleted user

I'm experiencing the same issue.

A deleted user due to changes in the user directory connector (or I deleted the user myself due to modifications in the connector) is allocated to a token, but because it is deleted, the deallocation button is disabled and the token can't be released

See image in the attached file.

Thanks.

8 Replies
miguel_rojas_i2
Partner - Contributor II
Partner - Contributor II

I used this script

update public."Users" set "Deleted" = false where "ID" = 'user-id' using pgAdmin

And then restart the Qlik Sense Repository Service.

After that you can deallocate the token in the QMC

Anonymous
Not applicable
Author

Thanks Miguel for your reply.

I'm new to Qliksens.

Please explain this:

update public."Users" set "Deleted" = false where "ID" = 'user-id' using pgAdmin


Where should I run the script  (if it is a script because the full line does not look like a script)?

If it is a configuration, where can I find the Update public users configuration?

I would be grateful if you could be specific about what steps to take.


Thanks.

Oren.



miguel_rojas_i2
Partner - Contributor II
Partner - Contributor II

Hi Oren

This is an sql script that i executed in the Qlik Sense internal database using pgAdmin tool, remember that Qlik Sense's internal data base is postgresql.

You will need the postgresql admin credentials used during Qlik sense installation.

Anonymous
Not applicable
Author

Thanks Miguel,

This is grate. I'll check it out this sunday.

Although it seems like a bug to me..

Qliksense is a great tool, very flexible and straightforward.

It doesn't feel write that i should go so under the hood for this is a very

easy scenario to get into.

Anyway, thanks again and a grate weekand.

Oren.

‫בתאריך יום ה׳, 8 ביוני 2017 ב-20:54 מאת ‪Miguel Angel Rojas Mejia‬‏ <‪

qcwebmaster@qlikview.com‬‏>:‬

rittermd
Master
Master

Keep in mind that tokens are designed to be quarantined for 7 days when a user is removed.  A login token is quarantined for 28 days after it is used.

If you go around this you are probably violating your license agreement.

miguel_rojas_i2
Partner - Contributor II
Partner - Contributor II

Hi, thanks for your comment but this is actually a very weird scenario. Once the user is removed from the Operating System, not from Qlik, the token is kind of lost because you can't deallocate it or put ir in quarantine, it is just lost.

After i run the script the deallocate button is enabled and now you can release the token and if the conditions apply it is put in quarantine for 7 or 28 days depends on the token configuration like you said.

rittermd
Master
Master

Ok.  I have not run into that.

Anonymous
Not applicable
Author

Hi All.

I finally got some help with this from my local Qliksens representation.

Apparently, Deallocate a deleted user is a known bug that needs to be handled by Qliksens support.

They need to RDP your server and run the script for you.

Good luck.