• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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