You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content at https://docs.qgis.org/3.34/en/docs/user_manual/auth_system/auth_considerations.html is quite confusing. Most of it is a brainstorming aimed at QGIS developers of what should be ideally be implemented, but is not. So it doesn't really belong to user documentation. This is more something to put in design notes of the authentication system in the qgis/QGIS source code, for developers.
I believe only the first sentence "Once the master password is entered, the API is open to access authentication configs in the authentication database, similar to how Firefox works. However, in the initial implementation, no wall against PyQGIS access has been defined. This may lead to issues where a user downloads/installs a malicious PyQGIS plugin or standalone app that gains access to authentication credentials." should be let in the user documentation.
The text was updated successfully, but these errors were encountered:
Description
The content at https://docs.qgis.org/3.34/en/docs/user_manual/auth_system/auth_considerations.html is quite confusing. Most of it is a brainstorming aimed at QGIS developers of what should be ideally be implemented, but is not. So it doesn't really belong to user documentation. This is more something to put in design notes of the authentication system in the qgis/QGIS source code, for developers.
I believe only the first sentence "Once the master password is entered, the API is open to access authentication configs in the authentication database, similar to how Firefox works. However,
in the initial implementation,no wall against PyQGIS access has been defined. This may lead to issues where a user downloads/installs a malicious PyQGIS plugin or standalone app that gains access to authentication credentials." should be let in the user documentation.The text was updated successfully, but these errors were encountered: