Login fails with blank "Could not login:" error when QGIS auth manager is not initialised

Open Beginner friendly
#953 0 comments 0 reactions 0 assignees View on GitHub

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

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/qgis-plugin

All issues in MerginMaps/qgis-plugin

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.