Capture more errors from the backend and show error messages for them

[jredrejo]

Summary

In the wizard setup, when importing users from a remote facility

• Force validation in some cases that were not covered
• Better capture of the error messages provided by the backend
• Clean previous errors when the modal to use admin credentials is shown

References

Closes #11711

In reference to #11711 , the last point of the description:

when we have both the Username and Password fields displayed and I enter the username of a learner who was originally created without a password then it's not accepted as valid credentials and I have to import that learner signed in as an admin

has not being changed as it seems a correct behaviour of the application. When facility settings are changed, previous user not requiring a password to login can't login until they have a password. Importing them remotely should not be different. In any case, if @jtamiace has a better solution, perfect.

Reviewer guidance

Follow the steps @pcenov described in #11711

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.16.0b13.dev0_git.5.g484eb1e4.pex
Windows Installer (EXE)	kolibri-0.16.0b13.dev0+git.5.g484eb1e4-unsigned.exe
Debian Package	kolibri_0.16.0b13.dev0+git.5.g484eb1e4-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.16.0b13.dev0+git.5.g484eb1e4-0.3.0.dmg
Android Package (APK)	kolibri-0.16.0b13.dev0+git.5.g484eb1e4-0.1.0-debug.apk
TAR file	kolibri-0.16.0b13.dev0+git.5.g484eb1e4.tar.gz
WHL file	kolibri-0.16.0b13.dev0+git.5.g484eb1e4-py2.py3-none-any.whl

[rtibbles]

when we have both the Username and Password fields displayed and I enter the username of a learner who was originally created without a password then it's not accepted as valid credentials and I have to import that learner signed in as an admin

I think this is correct, and only allowing to do this on the Kolibri device the user is on and not remotely seems more secure.

[pcenov]

Hi @jredrejo while regression testing the import of individual user accounts I noticed that now if I select the 'Use an admin account' option, when I click the 'Back' arrow then I am brought back to the 'Import individual user accounts' page and I can't proceed because now the 'Username' and 'Password' fields are required.
This workflow was confusing previously as well but the admin was still able to click the 'Continue' button and proceed with the import. So it should be further discussed how to handle that case.

Here's a video of what I am doing:

2024-01-29_18-28-18.mp4

[jredrejo]

Hi @jredrejo while regression testing the import of individual user accounts I noticed that now if I select the 'Use an admin account' option, when I click the 'Back' arrow then I am brought back to the 'Import individual user accounts' page and I can't proceed because now the 'Username' and 'Password' fields are required. This workflow was confusing previously as well but the admin was still able to click the 'Continue' button and proceed with the import. So it should be further discussed how to handle that case.

Here's a video of what I am doing:

2024-01-29_18-28-18.mp4

@pcenov fixed!

[pcenov]

Thank you @jredrejo - manual QA passes, good to go!

[rtibbles]

All changes make sense, manual QA checks out. @marcellamaki I suspect we should merge this for 0.16.0.

[marcellamaki]

Yes - that sounds good to me @rtibbles. This seems worth including, and as @pcenov has done manual QA, I feel confident about us merging it in :)