I don't know if already followed the steps decribed in the second bloc of this link:
Also, if it is already done, as soon as 3 anonymous user already connected to the hub, they will have a token assigned to each one of them and you will run out of tokens..
Thank you for your time and for the clarifications.
I Was completely out on this one or it is true when yuo don't configure login access rule ?
Because I know it is possible the give anonymous tokens acces, when we have 10 tokens and 10 users for example , each time a user connects, he take automatically a token.(a dedicated token).
I will try to not complicate things and not hold you back too much.
here is the scenario.
100 tokens, 100 users (AD, local, doesn't matter).
Instead of giving manually each user a licence throught the licence section, I want every user when accessing first time the hub, gets automatically a token (without requesting an administrator).
how this scenario is different in terms of configuration (rules type maybe) compared to the one described in this thread.
meant 30 users at the same time without editing capabilities, what for my purposes looked great.
So far I've shared the link to my app with just 7 or 8 people. How can we be running out of our 30 user passes?
Can you share a screenshot of the License Summary page?
At the outset, this isn't how Login Access Passes Work. From https://help.qlik.com/en-US/sense/September2017/Subsystems/ManagementConsole/Content/create-login-access.htm:
A login access pass allows an identified or anonymous user to access the hub for a maximum of 60 continuous minutes per 28-day period. If the user exceeds the 60-minute time limitation, the user connection does not time out. Instead, another login access pass is used. If no more login access passes are available, the session is discontinued.
This means that the use case for Login Access Passes is either anonymous or infrequent usage.
What was configured was 30 access passes in a 28 day period. If they are getting license denials then that suggests that the pool of token(s) assigned for that Login Access rule is running out due to usage.
Thank you very much, guys. I see it was all a misunderstanding from me of the "anonymous login" concept. I now see that if someone is going to do an extensive use of the app, they should get a user access with credentials. Even if they're going to have only "viewer" roles.
I appreciate the clarifications from all of you. Very helpful.