[6.x]: alpha.10 - No front-end login controller

[white-lukas]

What happened?

Description

Looks like the action route for users/login is not available anymore in craft 6?
How should front-end logins be handled?

Craft CMS version

6.0.0-alpha.10

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

No response

[linear-code]

CMS-2263

[brianjhanson]

The route is now POST {cpTrigger}/login instead, so /admin/login by default. Now that I'm writing this having that set to cpTrigger is maybe a little odd for a front-end login, so that may change, but it should work for the moment.

[white-lukas]

Yeah, if you set cpTrigger to something completely random as extra security, so it's not easily accessible. It would be counter productive to expose the cpTrigger that way.
Or having IP block on the cpTrigger might also give problems than

[AugustMiller]

I think we may have talked in Discord about this… but I'll summarize here:

The loginPath setting now defaults to null, disabling front-end login. Users would have to discover the CP/admin login page in order to sign in (but nothing changes about their capabilities when using that form).

To preserve 5.x behavior, set loginPath to login. Craft will use its built-in system templates if you have not provided your own.

---

Edit: I am pretty sure I made the same error when reading this the first time as I just did. 🫠 Since then, Brian and Brandon appear to have added back actions/users/login (bf77a1a), support for POST {loginPath} (bcd734c), and fixed the logic was preventing the front-end views from resolving (#19229)!