Login golden path is generating error logs in server
Field Tab
Scrum
Field Tab
Scrum
Description
In the current implementation, the strategy we are using to detect if a site exists is calling moodle's /login/token.php url without any arguments and making sure that we get the "correct" error message.
The problem with this approach is that an error log will be generated in the moodle site, and we're polluting the error log as part of the golden path.
This may be the only approach for older moodle sites, but in newer versions we could be reading the site's public info or even create specific endpoints for this. So this strategy could be left as fallback when nothing else is available.
Minor
In the current implementation, the strategy we are using to detect if a site exists is calling moodle's
/login/token.phpurl without any arguments and making sure that we get the "correct" error message.The problem with this approach is that an error log will be generated in the moodle site, and we're polluting the error log as part of the golden path.
This may be the only approach for older moodle sites, but in newer versions we could be reading the site's public info or even create specific endpoints for this. So this strategy could be left as fallback when nothing else is available.