We have a similar problem, even with a backup and restore to a new system, the problem with the missing token in the link remains
we could observe in the debug log that the token is generated and also stored in the DB.
old
D, [2024-03-20T13:23:32.012764#362396-141880] DEBUG -- : Token Exists? (0.2ms) SELECT 1 AS one FROM `tokens` WHERE `tokens`.`token` = 'tocken123.....' LIMIT 1
D, [2024-03-20T13:23:32.013460#362396-141880] DEBUG -- : Token Create (0.2ms) INSERT INTO `tokens` (`user_id`, `token`, `action`, `created_at`, `updated_at`) VALUES (246, 'tocken123.....', 'PasswordReset', '2024-03-20 12:23:32.011000', '2024-03-20 12:23:32.011000')
new bevor import
D, [2024-03-20T12:16:38.319623#3270-141960] DEBUG -- : TRANSACTION (0.1ms) BEGIN
D, [2024-03-20T12:16:38.320013#3270-141960] DEBUG -- : Token Exists? (0.2ms) SELECT 1 AS one FROM "tokens" WHERE "tokens"."token" = $1 LIMIT $2 [["token", "tocken456....."], ["LIMIT", 1]]
D, [2024-03-20T12:16:38.321663#3270-141960] DEBUG -- : Token Create (0.9ms) INSERT INTO "tokens" ("user_id", "token", "action", "created_at", "updated_at") VALUES ($1, $2, $3, $4, $5) RETURNING "id" [["user_id", 3], ["token", "tocken456....."], ["action", "PasswordReset"], ["created_at", "2024-03-20 12:16:38.318000"], ["updated_at", "2024-03-20 12:16:38.318000"]]
D, [2024-03-20T12:16:38.325725#3270-141960] DEBUG -- : TRANSACTION (3.5ms) COMMIT
D, [2024-03-20T12:16:38.330479#3270-141960] DEBUG -- : Translation Load (0.5ms) SELECT "translations".* FROM "translations" WHERE "translations"."locale" = $1 AND "translations"."source" = $2 LIMIT $3 [["locale", "de-de"], ["source", "Notification"], ["LIMIT", 1]]
D, [2024-03-20T12:16:38.331217#3270-141960] DEBUG -- : Translation Load (0.2ms) SELECT "translations".* FROM "translations" WHERE "translations"."locale" = $1 AND "translations"."source" = $2 LIMIT $3 [["locale", "de-de"], ["source", "Manage your notification settings"], ["LIMIT", 1]]
D, [2024-03-20T12:16:38.334080#3270-141960] DEBUG -- : Send notification to: test@test.de (from:Zammad Helpdesk <noreply@172.x.x.x>/subject:Zurücksetzen Ihres Zammad Helpdesk Passworts)
before we did the restore on the new system, we tested the password forget. in the database the pilbic.token is stored in a different format than in the database of the old non-functioning password forget.
old
COPY public.tokens (id, user_id, persistent, token, action, name, preferences, last_used_at, expires_at, created_at, updated_at) FROM stdin;
36 61 f token123 PasswordReset \N \N \N \N 2023-07-31 14:27:25.079+02 2023-07-31 14:27:25.079+02
39 98 f token123 PasswordReset \N \N \N \N 2023-08-21 11:30:22.245+02 2023-08-21 11:30:22.245+02
41 97 f token123 PasswordReset \N \N \N \N 2023-09-04 08:23:35.454+02 2023-09-04 08:23:35.454+02
43 232 f token123 PasswordReset \N \N \N \N 2023-10-04 11:29:04.202+02 2023-10-04 11:29:04.202+02
......
new before import
COPY public.tokens (id, user_id, persistent, name, token, action, preferences, last_used_at, expires_at, created_at, updated_at) FROM stdin;
2 3 f \N token123 PasswordReset \N \N \N 2024-03-20 12:16:38.318 2024-03-20 12:16:38.318
\.
maybe this is the cause?
We have not yet been able to solve the problem.
