Hi,
As you can see in the log below the validity of the licence is checked (twice ?) every twenty second or so, the token is refreshed.
It spams the debug logs (and that’s a problem). What the point to do this check so often? This is crazy.e2024-03-20T14:01:20+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:01:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:01:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:01:50+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:01:50+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:01:50+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:02:03+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:02:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:02:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:02:20+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:02:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:02:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:02:50+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:02:50+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:02:50+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:03:03+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:03:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:03:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:03:20+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:03:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:03:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:04:01+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:04:01+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:04:01+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:04:03+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:04:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:04:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:04:20+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:04:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:04:20+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:04:50+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:04:50+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:04:50+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
/2024-03-20T14:05:03+0100] ]DEBUG] ]EventSubscriber\UpdateEventSubscriber:69]: Checking if route matches updates endpoint
/2024-03-20T14:05:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:61]: Deleting expired refresh tokens
/2024-03-20T14:05:03+0100] ]DEBUG] ]Core\Security\Authentication\Infrastructure\Repository\DbWriteTokenRepository:82]: Deleting expired tokens which are not linked to a refresh token
Hi
We changed this for 24.04. Currently each time a call is performed to APIs, there is a check to delete obsolete tokens.
Hi,
Sadly we going to upgrade to 23.10.
24.04 won’t have enough recoil to be an option, plus users still aren’t ready to not use the old pages as the new Resource Status page is too much buggy in 22.10 so it may have been widely adopted.
And what did you change exactly?
Last time we have a talk, you, Mathieu and me, you’ve talked of this 20s period about the licence check, so I really don’t understand. Is access to the APIs subject to the possession of a commercial licence?
And, if it has absolutely no connection with the licensing (?), I still don’t understand why it has to be checked so often. Tokens to access the API aren’t expiring on a 20 seconds basis. Do they ?!
>Currently each time a call is performed to APIs, there is a check to delete obsolete tokens.
Sounds absolutely crazy…
Hi
We have changed the purging of obsolete API tokens which were controlled at each access to the APIs by a parallel system which is responsible for doing this work less often in order to optimize performance.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.