Login fails with blank "Could not login:" error when QGIS auth manager is not initialised
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- authentication
Research direction
Start from the plugin's login flow and find where credentials are stored through the QGIS authentication manager and where the Could not login: dialog is created. Check how those failures are handled alongside existing network and wrong-password errors. Done means an uninitialised or unusable auth manager produces a clear message, while successful login and the existing error messages still work.
Written by the indexing model from the issue text.
Description
Context
On a fresh QGIS 4.2.x install, logging in through the plugin fails with an empty Could not login: dialog.
The user's network and credentials are fine: browser login works, and a wrong password in the plugin returns the expected server error. The problem is that the plugin fails to save the credentials to the QGIS authentication manager when the manager isn't properly initialized. These failures aren't caught, so login ends with no explanation.
Support ticket: https://support.merginmaps.com/odoo/all-tickets/17068
Related: #937 (network issue, but its screenshot shows the same auth manager error), #325, #656, #804
Solution
Detect when the QGIS auth manager isn't usable or credentials can't be stored, and show the user a clear message explaining what went wrong and how to fix it, instead of a blank error.
Acceptance Criteria
- If the auth manager isn't initialised, the user gets a clear error message
- The
Could not login:dialog never shows an empty message - Login with a working auth manager still succeeds
- Network and wrong-password errors still show their existing messages
- Dominant language
- Python
- Stars
- 45
- Forks
- 21
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/qgis-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/qgis-plugin#848 · 1 comment ·
-
Project history and Remove locally fail in projects with long paths on Windows (> 260 characters)Openbug windows
Difficulty 3/5 1-2 days Newbie friendliness 55/100
MerginMaps/qgis-plugin#967 ·
-
View changes and schema check use the wrong base copy for GeoPackages in subfoldersPossibly taken @harminius claimed this 6 days ago. Openbug
MerginMaps/qgis-plugin#963 · 1 assignee ·
-
Error when syncing project.Possibly taken @harminius claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 54/100
MerginMaps/qgis-plugin#960 · 2 comments · 1 assignee ·
-
@mm_project_version is not updatedPossibly taken @harminius claimed this 20 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
MerginMaps/qgis-plugin#947 · 1 assignee ·
All issues in MerginMaps/qgis-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
auto-reported bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
soup airgap-bundle --bundle-size-cap nan, inf or a cap above ~1.67e299 GiB stops with an internal ValueError/OverflowError (exit 1) instead of a usage errorPossibly taken @Keshemir claimed this today. Openbug claimed difficulty:2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MakazhanAlpamys/Soup#3045 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dagster-io/skills#80 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day