Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Security][LoginLink] Document enum support in signature properties #21770

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

Open
lacatoire wants to merge 2 commits into
base: 8.1
Choose a base branch
from
Open

[Security][LoginLink] Document enum support in signature properties #21770

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f473e05
[LoginLink] Document enum support in signature_properties
Jan 27, 2026
1de858a
add an example
Jan 28, 2026
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
33 changes: 33 additions & 0 deletions security/login_link.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -405,6 +405,39 @@ The properties are fetched from the user object using the
``requestLoginLink()`` controller, you can invalidate all login links
whenever a user requests a new link.

.. versionadded:: 8.1

Signature properties can be enum values (both ``UnitEnum`` and backed enums).
Changing the enum case automatically invalidates existing login links.

A common use case is to invalidate all existing login links when a user's
security-related state changes (for example after requesting a password reset).

For example, you can include an enum value in the signature properties::

enum LoginState: string
{
case ACTIVE = 'active';
case PASSWORD_RESET = 'password_reset';
}

class User
{
private LoginState $loginState;


public function getLoginLinkSignatureProperties(): array
{
return [
'login_state' => $this->loginState,
];
}
}


When the ``LoginState`` changes (e.g. from ``ACTIVE`` to ``PASSWORD_RESET``),
all previously generated login links for that user become invalid automatically.

Configure a Maximum Use of a Link
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
Loading