Skip to content

Extra info for use of DateTime objects with login links #20920

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tjveldhuizen wants to merge 1 commit into from
Closed

Extra info for use of DateTime objects with login links #20920

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion security/login_link.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down