0 vote
On our datasource we have set two-factor TOTP Authentication as a requirement. I noticed every time I lose the network connectivity and the datasource gets disconnected, I have to renter the TOTP key. This is sometimes a bit annoying especially if I'm traveling around with my notebook.
Would It be possible to set a lifetime for the TOTP? Or to cache it as long as I do not close the application?
Hi Simon,
What data source type are we talking about? And how is the 2FA configured?
Best regards,
Xavier Fortin
Hi Xavier
Microsoft SQL Server. Two factor: TOTP using Google Authenticator.
Hi,
I do not believe this is possible at this moment. It might also just be a bug, we will investigate and post back when we have more information.
Best regards,
Xavier Fortin
Hi Xavier
Have you ever have had the chance to reproduce this issue. We still have this issue with the current version, when loosing network connection we have to re-enter the TOTP.
Regards
Simon
Hi simonschuermann,
Unfortunately, no. I'll raise the priority. That being said, some structural changes were made in another ticket (affecting the way we store the 2FA) that might have affected it. Those changes won't be available until the release of 2022.3 though. We'll try to find the time to reproduce the issue first.
Best regards,
Xavier Fortin
Hi again,
I took a few minutes to make some cursory testing. What I did was:
Is there something that does not really reflects what happens to you? Is there a delay that must be waited at one of the steps for the issue to occur?
To note that I'm testing with 2022.2.12.0.
Best regards,
Xavier Fortin
Thanks for checking. Having the same version. Yes it did not happened instantly when losing network connection. It might has to do with standby... I've checked all related settings, and found a promising setting:
I've unchecked the "On standby" checkbox. And will monitor the new behaviour. Will keep you posted
I can confirm the issue is resolved by unchecking the "On standby" checkbox :-)
Thanks anyway for your support.
Glad to hear you found a fix for your issue!
Please, do not hesitate to post again if you have any other issues.
Best regards,
Xavier Fortin