21.1. Authentication System Overview
21.1. ábra Anatomy of authentication system
21.1.1. Authentication database
The new authentication system stores authentication configurations in an SQLite
database file located, by default, at <profile directory>/qgis-auth.db.
This authentication database can be moved between QGIS installations without affecting other current QGIS user preferences, as it is completely separate from normal QGIS settings. A configuration ID (a random 7-character alphanumeric string) is generated when initially storing a configuration to the database. This represents the configuration, thereby allowing the ID to be stored in plain text application components, (such as project, plugin, or settings files) without disclosure of its associated credentials.
Megjegyzés
The parent directory of the qgis-auth.db can be set using the following
environment variable, QGIS_AUTH_DB_DIR_PATH, or set on the command line
during launch with the --authdbdirectory option.
21.1.2. Master password
To store or access sensitive information within the database, a user must define a master password. A new master password is requested and verified when initially storing any encrypted data to the database. When sensitive information is accessed, the user is prompted for the master password. The password is then cached for the remainder of the session (until application is quit), unless the user manually chooses an action to clear its cached value. Some instances of using the authentication system do not require input of the master password, such as when selecting an existing authentication configuration, or applying a configuration to a server configuration (such as when adding a WMS layer).
You can choose to save the password in the Wallet/Keyring of your
computer.
21.2. ábra Input new master password
Megjegyzés
A path to a file containing the master password can be set using the
following environment variable, QGIS_AUTH_PASSWORD_FILE.
21.1.2.1. Managing the master password
Once set, the master password can be reset; the current master password will be needed prior to resetting. During this process, there is an option to generate a complete backup of the current database.
21.3. ábra Resetting master password
If the user forgets the master password, there is no way to retrieve or override it. There is also no means of retrieving encrypted information without knowing the master password.
If a user inputs their existing password incorrectly three times, the dialog will offer to erase the database.
21.4. ábra Password prompt after three invalid attempts
21.1.3. Authentication Configurations
You can manage authentication configurations from Configurations in the Authentication tab of the QGIS Options dialog ().
21.5. ábra Configurations editor
Use the 
button to add a new configuration, the 
button
to remove configurations, and the 
button to modify existing ones.
21.6. ábra Adding config from within Configuration editor
The same type of operations for authentication configuration management (Add, Edit and Remove) can be done when configuring a given service connection, such as configuring an OWS service connection. For that, there are action buttons within the configuration selector for fully managing configurations found within the authentication database. In this case, there is no need to go to the configurations in Authentication tab of QGIS options unless you need to do more comprehensive configuration management.
21.7. ábra WMS connection dialog showing Add, Edit, and Remove authentication configuration buttons
When creating or editing an authentication configuration, the info required is a name, an authentication method and any other info that the authentication method requires (see more about the available authentication types in Authentication Methods).
21.1.4. Authentication Methods
Available authentications are provided by C++ plugins much in the same way data
provider plugins are supported by QGIS. The method of authentication that can
be selected is relative to the access needed for the resource/provider, e.g.
HTTP(S) or database, and whether there is support in both QGIS code and a
plugin. As such, some authentication method plugins may not be applicable
everywhere an authentication configuration selector is shown. A list of
available authentication method plugins and their compatible resource/providers
can be accessed going to and, in the
Authentication tab, click the 
Installed Plugins
button.
21.8. ábra Available method plugins list
Plugins can be created for new authentication methods that do not require QGIS to be recompiled. Since the support for plugins is currently C++-only, QGIS will need to be restarted for the new dropped-in plugin to become available to the user. Ensure your plugin is compiled against the same target version of QGIS if you intend to add it to an existing target install.
21.9. ábra Basic HTTP authentication configs
21.10. ábra ESRI Token authentication configs
21.11. ábra OAuth2 authentication configs
21.12. ábra PKI paths authentication configs
21.13. ábra PKI PKCS#12 file paths authentication configs
21.14. ábra Stored Identity authentication configs
Megjegyzés
The Resource URL is currently an unimplemented feature that will eventually allow a particular configuration to be auto-chosen when connecting to resources at a given URL.
21.1.5. Master Password and Auth Config Utilities
Under the Options menu () in the Authentication tab, there are several utility actions to manage the authentication database and configurations:
21.15. ábra Utilities menu
Input master password: opens the master password input dialog, independent of performing any authentication database command
Clear cached master password: unsets the master password if it has been set
Reset master password: opens a dialog to change the master password (the current password must be known) and optionally back up the current database
Clear network authentication access cache: clears the authentication cache of all connections
Automatically clear network authentication access cache on SSL errors: the connection cache stores all authentication data for connections, also when the connection fails. If you change authentication configurations or certification authorities, you should clear the authentication cache or restart QGIS. When this option is checked, the authentication cache will be automatically cleared every time an SSL error occurs and you choose to abort the connection
Integrate master password with your Wallet/Keyring: adds the master password to your personal Wallet/Keyring
Store/update the master password in your Wallet/Keyring: updates the changed master password in your Wallet/Keyring
Clear the master password from your Wallet/Keyring: deletes the master password from your Wallet/Keyring
Enable password helper debug log: enables a debug tool that will contain all the log information of the authentication methods
Clear cached authentication configurations: clears the internal lookup cache for configurations, used to speed up network connections. This does not clear QGIS’s core network access manager’s cache, which requires a relaunch of QGIS.
Remove all authentication configurations: clears the database of all configuration records, without removing other stored records.
Erase authentication database: schedules a backup of the current database and complete rebuild of the database table structure. The actions are scheduled for a later time, to ensure that other operations, like project loading, do not interrupt the operation or cause errors due to a temporarily missing database.
21.16. ábra DB erase verification menu
21.1.6. Using authentication configurations
Typically, an authentication configuration is selected in a configuration dialog for a network services (such as WMS). However, the selector widget can be embedded anywhere authentication is needed or in non-core functionality, like in third-party PyQGIS or C++ plugins.
When using the selector, No authentication is displayed in the pop-up menu control when nothing is selected, when there are no configurations to choose from, or when a previously assigned configuration can no longer be found in the database. The Type and Id fields are read-only and provide a description of the authentication method and the config’s ID respectively.
21.17. ábra Authentication configuration selector with no authentication
21.18. ábra Authentication configuration selector with selected config
21.1.7. Python bindings
All classes and public functions have sip bindings, except QgsAuthCrypto,
since management of the master password hashing and auth database encryption
should be handled by the main app, and not via Python.
See Security Considerations concerning Python access.