From c382b3933018d527752ddfec05218d128223234f Mon Sep 17 00:00:00 2001
From: Thijs-jan Veldhuizen <779998+tjveldhuizen@users.noreply.github.com>
Date: Sat, 26 Apr 2025 11:59:33 +0200
Subject: [PATCH] Update login_link.rst

---
 security/login_link.rst | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/security/login_link.rst b/security/login_link.rst
index 4ee1773d4e0..a9f22fbc92a 100644
--- a/security/login_link.rst
+++ b/security/login_link.rst
@@ -468,7 +468,10 @@ The properties are fetched from the user object using the
     invalidating logic to your login links. For instance, if you store a
     ``$lastLinkRequestedAt`` property on your users that you update in the
     ``requestLoginLink()`` controller, you can invalidate all login links
-    whenever a user requests a new link.
+    whenever a user requests a new link. If you use DateTimeInterface
+    objects, make sure to add ``lastLinkRequestedAt.timestamp`` to the
+    signature properties, so it does not fail on different instances of
+    the object.
 
 Configure a Maximum Use of a Link
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~