It sounds like you have the most up-to-date information. I do hope that during your contacts with Support you’ve submitted your feature requests so they can be considered as we plan future work on the Windows integrations.
My information is also already old. I guess about 2 month… but no updates after that.
Well, will email them again… and otherwise… shame… but like I said… probably that we will dump duo.
Last update, was that the registery keys aren’t working because of an DUO update… and that the latest DUO (2.3.0) is set the limit to 8 hours. But, because of change of things, it is not easy to fix that without changing something in the authentication framework…
as I have read… installing the duo-rdgateway on our session host, will give someproblems with the duo trusted ip policy?
Yes I agree, installing on the session host means that Duo is not aware of the originating IP address, all sessions originate from the gateway… So you cannot have trusted IP. That is the reason we cannot use it on the session hosts. We need trusted IP because there are many shared computers at head office and these computers are locked down.
Maybe this is a push from their sales team to get you to license every single user of shared computers at a trusted site?
I can confirm that 184.108.40.206 with the reg keys from support is working, I have set a 24 hour session limit and have had no complaints for months now.
Not sure if I am at risk for not installing any updates though.
I have send support an email about the register keys.
“Currently there is not a way to adjust this timeout. I can add you to the feature request for supporting a configurable session timeout if you would like.”
Can someone give me the register keys so our customers can use DUO without complaining about being kicked from the servers.
How did you get the registry keys to resolve this issue? Also, what version of windows server are you currently using with the windows registry keys? I’m having timeout issues with a Windows Server 2012 R2 gateway server with DUO Authentication for Remote Desktop Gateway 220.127.116.11.
Is someone able to share the reg keys that resolved the issue? Duo support advise there is no fix, this is just not acceptable for our users, we are getting so many complaints. Suggestions to use the RDSH agent don’t really work for us, as this doesn’t pass through the IP so we cannot do location whitelisting.
We have the same issue, battling with Duo support for them to provide the registry keys for RD Gateway 18.104.22.168. Please can you share the registry keys?
Thanks everyone for keeping this topic alive. @DuoKristina I know we have all been asking for this feature with support and our Account Executives. My account executive didn’t make it sound like there is a way to be “added” to the feature request. Maybe someone at Duo can refer to this thread if they need proof of the need for this feature.
If your AE did not know how to add you to the existing feature request, contact Support. They definitely know how to do that.
Wanted to jump in and ensure we set some expectations around RDG and session timeout. It is a feature we would like to address in the future, but do not have a definitive timeline for beginning development.
To set some context about where we are today, we previously attempted to add this feature to our RDG application. The implementation did not work consistently and will be removed from the product in a future update. In the meantime, we continue to work to address this feature in the correct manner.
This may not be the answer you would like to read today but any registry setting to alter default timeout behavior may break in future updates and in its current state is unsupported.
We ask that the registry setting not be shared as this is an unsupported configuration and may result in unexpected behavior.
If you are looking to be added to the feature request around this, as @DuoKristina said please contact support and they will be more than happy to help.
Any update on this at all?