Skip to main content
Solved

Licence validity insane checking

  • March 20, 2024
  • 3 replies
  • 103 views
S

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.

[2024-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
 

Best answer by lpinsivy

Hi @Stéphane no, “tokens” do not mean license.

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.

 

3 replies

lpinsivy
Centreonian
Forum|alt.badge.img+21
  • lpinsivy
  • Centreonian
  • 1120 replies
  • March 22, 2024

Hi @Stéphane this is not about licenses but tokens to access to API.

We changed this for 24.04. Currently each time a call is performed to APIs, there is a check to delete obsolete tokens.

S
  • Stéphane
  • Author
  • 266 replies
  • March 22, 2024

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…

lpinsivy
Centreonian
Forum|alt.badge.img+21
  • lpinsivy
  • Centreonian
  • 1120 replies
  • Answer
  • March 25, 2024

Hi @Stéphane no, “tokens” do not mean license.

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.

 


Terms & ConditionsCookie settingsAccessibility statement