Backlog

00062666: OTP with leading PIN

0 vote

avatar

Hi all

Version 2024.1.31.0

We use OTP codes with a leading PIN in this format: <PIN><OTP>
Example: 1234987654

1234 is a static personal PIN
987654 is the OTP code

  • We have a RDS website, where we need to authenticate like described.
  • We have linked the password and the OTP settings from two separate records within the vault.


We are unable to configure to put a PIN in front of the OTP code (note: without using macros; we don't like macros because if stability reasons).

Would it be possible, to extend the properties page of a website to put a PIN in front of the OTP code?

rds_feature-request

Would be great if this sounds interesting for a dev to code.

Happy weekend
~Tom

rds_feature-request.png

All Comments (3)

avatar

Hello,

Thank you for the request. We will open an internal ticket for this.

Regards,

Hubert Mireault

avatar

Hello Tom H,

We've been exploring the possibility to implement your request, and we need more information as well as to clarify a few things before investigating this further.
We understand that you desire to add a static text before/after the OTP Code (the Append/Prepend to Pin). That behaviour is clear.
Here is what we need to clarify/ask (please answer using the numbers in the question):

  1. You mentioned that the PIN is a "static personal PIN". Do you need a PIN that is different for each user, or was a PIN bound to an entry sufficient? (If the PIN is set in the entry, any users from a shared database would all have the same PIN)
  2. If you could provide us with an instance as accurate as possible on how you wish the entire process to work, that would help us see if/how we can implement it.


Regards,

Jafran Majeau

avatar

Hi there

> You mentioned that the PIN is a "static personal PIN". Do you need a PIN that is different for each user, or was a PIN bound to an entry sufficient? (If the PIN is set in the entry, any users from a shared database would all have the same PIN)

There is a form on a website like seen below.

2024-08-09 22_57_54-Remote Desktop Manager [apps.thuinformatik.ch]

Username: A username
Password: A password
OTP: {a number/string called PIN}{a OTP token} [ example: 1234987654 ]

The password is the 1st factor
The OTP token is the 2nd factor
The PIN is the 3rd factor

  • User A has his own username -> Linked to a password entry in the vault called User A
  • User A has his own OTP -> Linked to a OTP entry in the vault called User A
  • User A has his own PIN -> Unknown from where it comes


  • User B has his own username -> Linked to a password entry in the vault called User B
  • User B has his own OTP -> Linked to a OTP entry in the vault called User B
  • User B has his own PIN -> Unknown from where it comes
  • etc..


> If you could provide us with an instance as accurate as possible on how you wish the entire process to work, that would help us see if/how we can implement it.

This is the properties page to configure a OTP token: I can not configure to prepend a PIN to a OTP token and give this value back to the OTP field in the website record.

cb6aaeb6-5ad4-41a8-b430-5da5035e9972

The same problem is with the properties page of a website (see initial post): I can not configure to prepend a PIN to the linked OTP token.

I don't know what would be the best option. I can say that the OTP token and the PIN are individual for each user of the website. Each user has it's own username/password and otp/pin.

The website to test with is here.

I hope this helps, otherwise I'm happy to help.

Best regards
Tom

cb6aaeb6-5ad4-41a8-b430-5da5035e9972.png

2024-08-09 22_57_54-Remote Desktop Manager [apps.thuinformatik.ch].png