2-Factor Authentication at Database Level
I had initially posted this in the Feature Request but perhaps it is a bug instead of a feature.
When attempting to setup 2 factor authentication for a database connection so that it is per user rather than per application it prompts you to link your google authenticator as soon as you select that as the method. The problem with this lies in the case where you are attempting to create a .rdd file to be distributed to people. RDD files support someone changing the username/password even when locked but you obviously not want to distribute an RDD file with a pre-linked authenticator. Is there a method to create an RDD file that will prompt the user to link an authenticator to the datasource? Attempting to turn on force 2-factor from the datasource settings requires you to have pre-configured it in the database settings.
All Comments (3)
Hello,
You would need to follow the steps below:
1- With your administrator account, configure a 2FA to access the datasource
2- Enable the Force 2FA in the Data Source Settings
3- Go back in File -> Data Sources and duplicate your data source
4- Put the 2FA to none and adjust the username/password the proper you want to distribute the data source configuration
5- Save the data source configuration
6- Export this as a .rdd and distribute it to your users
When your users will try to connect on the data source, they will receive an message that they need a 2FA to connect.
At this point, they would need to go in File -> Data Sources and edit the data source to add the 2FA authentication to access the data source.
Best regards,
Jeff Dagenais
But if the datasource is locked they won't be able to go in and edit it. Is there a way do to this with a locked datasource?
Hi,
We would need a button to configure the 2FA even when the data source is locked. I will add this to our todo list.
Regards
David Hervieux