Login into Offline Client with Username, Password and OTP
Best Security for Login into Windows Offline Client to prevent unauthorized Access.
No Solution available
We could use that aswell. @Netwrix what is your take on that?
Would be great to get some Feedback. There ist another Idea with the same issue. (MFA for Offline Client - Password Secure / Ideas - Netwrix Community)
@Kristina.kaya
Thanks so much for raising this idea! 
We can definitely see the value in adding an additional authentication factor when logging into the Offline Client!
Before we explore implementation approaches and priorities, we’d like to gather a bit more feedback from the community:
Would a second factor based solely on TOTP (e.g., codes from an authenticator app) work for your offline use cases? This is a common offline MFA method that does not require an active network connection once the shared secret is provisioned.
We’re also thinking it would be best to make offline second-factor optional, so teams that don’t need it aren’t forced to take additional steps… but we’d appreciate your input on that as well.
Any thoughts on TOTP usability in your environments, or other offline MFA methods you’d like to see? Open feedback and examples of your specific scenarios would be really helpful!
Cheers,
Sascha
Hi Sascha,
TOPT is the easiest way for us to protect the clients’ offline database from unauthorized access.
This feature can be optional for our purposes.
Hello,
I am also strongly in favor of the offline database having an MFA option, preferably optional. For me, it is a very important security factor. Why can I secure the “normal” database with MFA but not the offline database? I have been waiting for this feature for 2 years… had it “wrapped up” with my supplier. 
TOTP is fine for me.
I would be very happy about a prompt implementation. Thank you. 
Hi,
an optional TOTP would be nice and enough for most customers.
Hi Sascha,
any further thoughts?
@Sascha
An MFA would certainly make sense for the offline client!