Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Making GuardTokenInterface extend TokenInterface | Ryan Weaver | 2015-09-26 | 1 | -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 changes | Ryan Weaver | 2015-09-20 | 1 | -1/+10 |
| | |||||
* | Tweaking docblock on interface thanks to @iltar | Ryan Weaver | 2015-09-20 | 1 | -3/+4 |
| | |||||
* | Thanks fabbot! | Ryan Weaver | 2015-09-20 | 1 | -1/+1 |
| | |||||
* | Renaming the tokens to be clear they are "post" and "pre" auth - also adding ↵ | Ryan Weaver | 2015-09-20 | 1 | -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. |