Thanks for the kind words, Robert! I’m glad the implementation works well for you.
Since the MFA code prompt is triggered by a custom authentication request on the SSH protocol level, we actually don’t know if a MFA code will be requested until we get the authentication request on the client side. Therefore it will not be possible to figure this out beforehand and let the client display a different message at that point. Sorry!
okay, finally got this working today and first impressions are good.
A few suggestions
When adding the MFA users and the standard windows “Select Users or Groups” comes up, it would be good to default to Entire directory if the server is in a domain. An alternate would be to detect where in the tree the last search was performed from and repeat the use of that node unless changed.
Adding a number of domain users gets old real quick when having to keep switching from the local server to the domain
I’d like the ability to add both the user_id and the cache timeout to the MFA userlist via the column chooser. In general I think you should have the option of seeing every value presented in the user that exists in the edit field for a user
All in all this is really promising and I’m looking forward to seeing where it ends up ! It helps enormously with the sell job to management both of Royal TS and RoyalServer
We have no specific date right now. We are currently reworking the Royal Server console UI and we are not really sure how long this will take but we aim for May, hopefully April.
as our Security Company push us to move away from Royal TS if not MFA implement, can you please indicate a deadline for the official release ? We need to indicate this info in order to have internal approval for a security exception. aka accept the risk for some time …
I can’t really tell the exact date, sorry. All I can say is that we are currently working on finalizing everything for the release. I surely hope it will be before the end of August - probably/hopefully earlier.