diff options
| author | Ryan Weaver <ryan@thatsquality.com> | 2015-05-17 17:27:01 -0400 |
|---|---|---|
| committer | Ryan Weaver <ryan@thatsquality.com> | 2015-09-20 19:24:20 -0400 |
| commit | 87752f2f460528718bbb691b1739a32368141c28 (patch) | |
| tree | d89d2fb55661bfb7685e932a1cdee515f4ece2ee /Guard/GuardAuthenticatorInterface.php | |
| parent | c4e11448bfba32d64ed4534b52e1a3958e9c2625 (diff) | |
| download | symfony-security-87752f2f460528718bbb691b1739a32368141c28.zip symfony-security-87752f2f460528718bbb691b1739a32368141c28.tar.gz symfony-security-87752f2f460528718bbb691b1739a32368141c28.tar.bz2 | |
Renaming the tokens to be clear they are "post" and "pre" auth - also adding an interface
The reason is that the GuardAuthenticationProvider *must* respond to *all* tokens
created by the system - both "pre auth" and "post auth" tokens. The reason is that
if a "post auth" token becomes not authenticated (e.g. because the user changes between
requests), then it may be passed to the provider system. If no providers respond (which
was the case before this commit), then AuthenticationProviderManager throws an exception.
The next commit will properly handle these "post auth" + "no-longer-authenticated" tokens,
which should cause a log out.
Diffstat (limited to 'Guard/GuardAuthenticatorInterface.php')
0 files changed, 0 insertions, 0 deletions