traditional form login is bound to username/password. Let's say we want a custom login in the future based on username, password and some other field. Using a custom guard this would be easy (as it scales), compared to refactoring form_login to guard.
We can also do both "for demo purposes":
/login
/login-special ? we need a use case for this (some 3rd field, next to email/password)
traditional form login is bound to username/password. Let's say we want a custom login in the future based on username, password and some other field. Using a custom guard this would be easy (as it scales), compared to refactoring form_login to guard.
We can also do both "for demo purposes":
/login/login-special? we need a use case for this (some 3rd field, next to email/password)Otherwise im leaning to drop form_login here.
https://knpuniversity.com/screencast/new-in-symfony3/guard-authentication