I think that you misunderstood me. My arguments are based on the fact that the login pass is similar to Usage CAL in QlikView
I found a good description of the restoration of the Pass
"n" Usage CAL
→ From the following day, n/28 numbers of UsageCAL will be recovered
→ After 28 days, "n" numbers of CALis recovered and available to use
Usage CAL count example
eg.1:Let's assume you have 1 Usage CAL. You used it and the counter starts.
→ After 1 day, counter becomes 1/28. After 2 days, counter becomes 2/28. After 5 days, counter becomes 5/28.........After 28 dyas, counter becomes 28/28. At this count(28 day period has passed), 1 CAL is recovered.
eg.2:Let's assume you have 5 Usage CAL. You used all and the counter starts.
→ After 1 day, counter becomes 5/28. After 2 days, counter becomes 10/28. After 6 days, counter becomes 30/28≒(Available 1 Usage CAL at this point)............After 28 days, counter becomes 140/28. At this point(28 day period has passed), 5 CAL is recovered.
Have "n=28" Login pass
Your used 8 login pass.
eg1.After 1 day, counter becomes 28/28 (Available 1 Login pass at this point). After 2 days, counter becomes 56/28 - 2 Login pass are recovered. We need 8 days to recover all login passes that were spent
eg2, In 1 day we add more login pass in pool and have n+n=56 login pass pool. Then after 1 day counter becomes 56/28= 2 (recovered 2 login pass). After 2 days, counter becomes 112/28 (4 login pass recovered). Needed 4 days to recover all login passes that were spent.
Attention to the issue.Is it fair to my statement is described in the eg2?
Possible by the addition of login pass in the pool to accelerate recover spent passes.