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

Consider removing WSSE and adding token-redirect cookbook article #5253

Closed
weaverryan opened this issue May 13, 2015 · 1 comment
Closed
Labels
actionable Clear and specific issues ready for anyone to take them. Security

Comments

@weaverryan
Copy link
Member

Hi guys!

On twitter (https://twitter.com/nesl247/status/597838638521679873) a friend of mine read the WSSE article about authentication, which meant his job was VERY hard to accomplish a fairly simple thing (he redirects to external system - like OAuth - which then redirects back with a token that's used for authentication). In our conversation, we identified a few problems:

A) The WSSE article should be very difficult to find or maybe should be removed. We have a warning on top, but it was clearly not enough

B) We should add an article about creating a token auth system that redirects externally, like OAuth. It's not clear at first that the redirect to the external system should be done by a simple route/controller with RedirectResponse. Once you understand that redirecting to the external service doesn't involve security, it becomes much more obvious that http://symfony.com/doc/current/cookbook/security/api_key_authentication.html can be used for this very easily

Thanks!

@weaverryan weaverryan added Doc Request actionable Clear and specific issues ready for anyone to take them. labels May 13, 2015
@javiereguiluz
Copy link
Member

I'm closing this in favor of #10423 where we are updating all the Security docs, including the "custom authentication provider" article. See https://github.com/symfony/symfony-docs/pull/10423/files#diff-b4ef99f8c1bf7772d4d387dcd63d949f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actionable Clear and specific issues ready for anyone to take them. Security
Projects
None yet
Development

No branches or pull requests

3 participants