summaryrefslogtreecommitdiffstats
path: root/Guard/Token/GuardTokenInterface.php
Commit message (Collapse)AuthorAgeFilesLines
* Making GuardTokenInterface extend TokenInterfaceRyan Weaver2015-09-261-1/+3
| | | | | This makes some of our type-hints more honest: i.e. where we look for a GuardTokenInterface, but really also expect it to implement TokenInterface.
* meaningless author and license changesRyan Weaver2015-09-201-1/+10
|
* Tweaking docblock on interface thanks to @iltarRyan Weaver2015-09-201-3/+4
|
* Thanks fabbot!Ryan Weaver2015-09-201-1/+1
|
* Renaming the tokens to be clear they are "post" and "pre" auth - also adding ↵Ryan Weaver2015-09-201-0/+15
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.