Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SecurityBundle] Fix HTTP Digest auth not being passed user checker #17559

Merged
merged 1 commit into from Jan 27, 2016
Merged

[SecurityBundle] Fix HTTP Digest auth not being passed user checker #17559

merged 1 commit into from Jan 27, 2016

Conversation

SamFleming
Copy link
Contributor

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

Wasn't sure if this was a bug so posted here http://stackoverflow.com/q/35022776/727236. However, after comparing the 2.3 branch and 2.8 branch I think it was a bug.

When trying to use http_digest on Symfony 2.8 you're greeted with the error Argument 2 passed to Symfony\Component\Security\Core\Authentication\Provider\DaoAuthenticationProvider::__construct() must be an instance of Symfony\Component\Security\Core\User\UserCheckerInterface.

The exact same security.yml works fine on v2.3.37.

Comparing the branches for the SecurityBundle I found that commit 05be5da1710ab681a04334d58126f8c3d431e3cb added the ability to configure a user checker on a per firewall basis. It seems that this commit seems to have missed updating the HttpDigestFactory (although it did update the other factories such as the HttpBasicFactory).

Testing this in my Symfony 2.8 app now works. However, I haven't been able to figure out what unit tests to write confirming this, does anyone with more experience on the SecurityBundle have any pointers?

Commit 05be5da1710ab681a04334d58126f8c3d431e3cb added the ability to
configure a user checker on a per firewall basis. However, that commit seems to
have missed updating the HttpDigestFactory.
@fabpot
Copy link
Member

fabpot commented Jan 27, 2016

Thank you @SamFleming.

@fabpot fabpot merged commit 517a9a2 into symfony:2.8 Jan 27, 2016
fabpot added a commit that referenced this pull request Jan 27, 2016
…r checker (SamFleming)

This PR was merged into the 2.8 branch.

Discussion
----------

[SecurityBundle] Fix HTTP Digest auth not being passed user checker

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

Wasn't sure if this was a bug so posted here http://stackoverflow.com/q/35022776/727236. However, after comparing the 2.3 branch and 2.8 branch I think it was a bug.

When trying to use `http_digest` on Symfony 2.8 you're greeted with the error `Argument 2 passed to Symfony\Component\Security\Core\Authentication\Provider\DaoAuthenticationProvider::__construct() must be an instance of Symfony\Component\Security\Core\User\UserCheckerInterface`.

The exact same `security.yml` works fine on v2.3.37.

Comparing the branches for the SecurityBundle I found that commit 05be5da1710ab681a04334d58126f8c3d431e3cb added the ability to configure a user checker on a per firewall basis. It seems that this commit seems to have missed updating the HttpDigestFactory (although it did update the other factories such as the [HttpBasicFactory](symfony/security-bundle@05be5da#diff-5f3e10fcc9de40dd09a8f3df3bdc9316)).

Testing this in my Symfony 2.8 app now works. However, I haven't been able to figure out what unit tests to write confirming this, does anyone with more experience on the SecurityBundle have any pointers?

Commits
-------

517a9a2 Fixed HTTP Digest auth not being passed user checker
@fabpot fabpot mentioned this pull request Feb 3, 2016
@fabpot fabpot mentioned this pull request Feb 28, 2016
@SamFleming SamFleming deleted the http_digest_fix branch October 1, 2016 21:04
@SamFleming SamFleming restored the http_digest_fix branch October 1, 2016 21:04
@SamFleming SamFleming deleted the http_digest_fix branch October 1, 2016 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants