Skip to content

Anonymous

My feedback

1 result found

  1. 136 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Instead of “require password” security control, we intend to support “Require OTP” requirement for public links (via SMS, Email, or TOTP). I wanted to share where we are headed. We do not plan on delivering this ask as is, but we do intend to solve the security use case behind it.

    Please comment if you disagree.

    An error occurred while saving the comment
    Anonymous commented  · 

    +100 on this. I have to create reports of unprotected links all the time , and then either disable it or inform their creators, it is so annoying and so unsecure in the first place.

    Come on guys, one checkbox in the enterprise admin area and one database query during public link creation with either forcing it or not - that is two hours of work, while you are still planning OTP for the next 5 or how many years? Seriously?

    OTP is not a solution for this anyway, we don't know many details about the recipient(s), that's why we use public link. If we would, we would invite the recipient(s) as a collaborator

    Anonymous supported this idea  · 

Feedback and Knowledge Base