From 7479720f5834bfcf306c4e45ea20c23be9d2c956 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gast=C3=B3n=20Fournier?= <gaston@getunleash.io>
Date: Tue, 29 Jul 2025 12:48:41 +0200
Subject: [PATCH] chore: better logging of failed tokens (#10425)

When querying invalid tokens we might catch them for a while to reduce
database load. Being able to identify the token can help understanding
what's going on or the client using that token

Log looks like:
```
[INFO] /services/api-token-service.ts - Token default:development.3ef3... rate limited until: Tue Jul 29 2025 09:53:47 GMT+0000 (Coordinated Universal Time)
```
---
 src/lib/services/api-token-service.ts | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/lib/services/api-token-service.ts b/src/lib/services/api-token-service.ts
index ca1752eca1..0ade354860 100644
--- a/src/lib/services/api-token-service.ts
+++ b/src/lib/services/api-token-service.ts
@@ -171,9 +171,10 @@ export class ApiTokenService {
                 stopCacheTimer();
             } else {
                 this.logger.info(
-                    `Not allowed to query this token until: ${this.queryAfter.get(
-                        secret,
-                    )}`,
+                    `Token ${secret.replace(
+                        /^([^.]*)\.(.{8}).*$/,
+                        '$1.$2...',
+                    )} rate limited until: ${this.queryAfter.get(secret)}`,
                 );
             }
         }