• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs Google Authenticator extension cannot be used for additional users

Bitpalast

Plesk addicted!
Plesk Guru
TITLE:
Google Authenticator extension cannot be used for additional users​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Onyx 17.5, 17.8
CentOS 7.6
​
PROBLEM DESCRIPTION:
The Google Authenticator extension is only available for the subscription user and the Plesk administrator. When a subscription user creates additional users with other roles (including a second subscription user who is entitled to do everything the original subscription user can do), Google Authenticator is not offered for that additional user.​
STEPS TO REPRODUCE:
Login in to a subscription, create an additional user. Then login with the additional user.​
ACTUAL RESULT:
Google Authenticator menu entry (link) is missing.​
EXPECTED RESULT:
Google Authenticator should be available for additional users, too.​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Back
Top