symfony-security - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Added placeholders to all log messages instead of hardcoded values	Martin Hasoň	2015-12-29	1	-1/+1
\|
*	Write the log message on a single line againn	Diego Agulló	2015-11-03	1	-4/+1
\|
*	Check whether $this->logger is not null on GuardAuthenticationListener	Diego Agulló	2015-11-01	1	-1/+6
\|
*	Making all "debug" messages use the debug router	Ryan Weaver	2015-09-26	1	-8/+8
\| \| \| \| \|	Only the "auth success" and "auth failed" messages remain at info. That's consistent with AbstractAuthenticationListener
*	Updating behavior to not continue after an authenticator has set the response	Ryan Weaver	2015-09-26	1	-0/+6
\| \| \| \| \| \| \|	This mirrors the behavior in core: if a listener sets a response (on success or failure), then the other listeners are not called. But if a response is not set (which is sometimes the case for success, like in BasicAuthenticationListener), then the other listeners are called, and can even fail.
*	Fixing a bug where having an authentication failure would log you out.	Ryan Weaver	2015-09-20	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	This solution is a copy of what AbstractAuthenticationListener does. Scenario: 1) Login 2) Go back to the log in page 3) Put in a bad user/pass You should still be logged in after a failed attempt. This commit gives that behavior.
*	Adding logging on this step and switching the order - not for any huge reason	Ryan Weaver	2015-09-20	1	-3/+7
\|
*	meaningless author and license changes	Ryan Weaver	2015-09-20	1	-2/+11
\|
*	A few more changes thanks to @iltar	Ryan Weaver	2015-09-20	1	-4/+4
\|
*	Adding periods at the end of exceptions, and changing one class name to ↵	Ryan Weaver	2015-09-20	1	-1/+1
\| \| \| \|	LogicException thanks to @iltar
*	Updating interface method per suggestion - makes sense to me, Request is ↵	Ryan Weaver	2015-09-20	1	-2/+2
\| \| \| \|	redundant
*	Thanks fabbot!	Ryan Weaver	2015-09-20	1	-11/+11
\|
*	Renaming the tokens to be clear they are "post" and "pre" auth - also adding ↵	Ryan Weaver	2015-09-20	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Initial commit (but after some polished work) of the new Guard ↵	Ryan Weaver	2015-09-20	1	-0/+180
	authentication system