[FrameworkBundle] Add login() and logout() to WebTestCase #35644
Conversation
nicolas-grekas
changed the title
|
Does this require the login_form authenticator is enabled in the firewall? Given that the Guards are more recommended now a days, would it be easier to pass in a |
|
|
| { | ||
| $config = sprintf('security.firewall.map.config.%s', $firewallName); | ||
|
|
||
| if (!$browser->getContainer()->has($config)) { |
There was a problem hiding this comment.
I just tried it and this will always return false, since the security.firewall.map.config.* services are private.
I have a question: is there a way to make the $browser->getContainer() return the same container as static::$container so we can retrieve private services? I don't know the impact in performances or anything since I don't really understand how it is managed internally. @nicolas-grekas, any idea?
This would be transparent for the end user, and still make sure that anyone could retrieve any service from the client when the container is an instance of the TestContainer (and of course, there will be an additionnal check here)
|
Closing in favor of #35997 |
6 participants
Followup of #28065
As a side-note, the two added
protectedmethods are supposed to be overriden by the developer if needed.getLoginToken()might be overriden if the user wants to use a token different than theUsernamePasswordToken, like aPostAuthenticationGuardTokenor any other kind of token that is available in its security config (like Oauth, SymfonyConnect, etc.). Someone might also use aPreAuthenticatedTokenand use theAuthenticationManagerto->authenticate()it and retrieve the result.authenticateToken()might be overriden in cases where setting a cookie has no effect, like when authentication is stateless or based on internal systems (when creating JWT tokens and use internal secrets to do so, or other cases I can't imagine).The
login()method returns theTokenInterfacein case the user might need it for further use, such as directly retrieving the logged inUserobject for instance, in order to make more assertions if the current functional tests is doing actions on the User.