2FA: DuoMobile: 1. Name = Windows Login not Productname; 2. Push Allow not available

Products Password Secure Ideas
, , , ,
1

What is a one sentence summary of your feature request?

2FA DuoMobile: 1. “PasswordSecure” as Productname in DuoMobile. 2. Pushlogin

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

We use mainly DuoMobile.

  1. The registration of the 2FA: QRCode Name after Registration is the Username. I have seen, that in Microsoft Authenticator it is PasswordSecure + Username. Could you please fix that?
  2. Other Software Products can send a Pushlogin. You try to login, the Authentication App asks you if you try to login, you say yes, you are logged in, you do not have to enter the token. Could you add this feature?

How do you currently solve the challenges you have by not having this feature?

  1. we manually rename the Productname to PasswordSecure
  2. we enter the token
5 Likes
2

As far as we know, cisco duo mobile, has you not listed as a partner company.

Neither Mateso Password Safe, nor Netwrix Password Secure
could your tech get in touch with them, so we could use their Push system with your software?

3

Hi Florian - thank you very much for sharing your suggestions and for taking the time to outline your use case with Duo Mobile.

Regarding the naming behavior during enrollment: Duo Mobile currently determines how the entry is displayed based on its own implementation. We’ve taken a closer look, and at the moment, this cannot be influenced from our side in a consistent way across all supported authenticator apps. We understand the desire for clearer labeling and will continue to monitor whether Duo provides new options that would allow us to improve this experience.

Concerning Duo Push: We appreciate you raising this capability and explaining how it would benefit your workflow. At present, our integration with Duo focuses on time-based one-time passwords, which ensure compatibility with a wide range of authenticator apps. Duo Push, however, requires a different type of partnership and technical integration that is not available to us today.

We will continue to watch developments in this area, and should the prerequisites change in the future, we’re open to reassessing what’s possible.

Thank you again for your thoughtful feedback… it truly helps us understand where additional value could be created. Please keep the ideas coming!

Cheers,
Sascha