Forum Replies Created
-
Posts
-
Morning,
DUO offer a free (up to 10 user) account with full MFA functionality. You have the option of switching from the trial to free account yourself in their portal. As well as our work account I set a free account up for home use and have all our home devices using it for free. For support, I’ve always found them very helpful even with the free account – maybe that’s changed since being taken over by Cisco, but they helped me last week when I was looking to get the second password field working in OpenConnect on Linux.
Looking to see if we can set the default option to ‘push’ via the firewall, therefore taking the Wyse out of the equation. But not keen on making config changes to production environments at the moment – don’t want to risk bringing anything down.
Rgds
That is indeed a shame. Openconnect under LINUX does support the second password field to specify the ‘push’ statement. Are you aware if any of the new Dell thin-clients are able to support this?
Its a shame if not and would suggest not moving with the times. HP thin clients are working well with MFA.
If anyone else struggling with this, its because the collection name needs to be enclosed with quote marks, something ConfGen is not doing, so in the RDSH Collections Box, you need to type “Collection_Name” or edit the generated WNOS file and manually add the ” ” marks. Thanks to Ronak & Fred for sticking with this and keeping me looking for a solution…….
Example:
VDIBroker=farm.domain.local
ConnectionBroker=Microsoft RDCollections=”EXAMPLE_Collection”
SignOn=YesThat would be ideal, but I know that changes and feature enhancements usually take some time to come to fruition. I think I’m stuck with the multiple wnos.ini option as I need to deploy next week.
Thanks.
Hi,
#1 So, the WDM server has the SSL cert installed. When I browse and use the WebGUI there are no complaints about the SSL cert. – All good. As I mentioned I have imported the CA Root, Intermediate and Server cert to the ThinOS terminals and they appear correctly. However, still getting the warning. Resolved temporarily by setting securitypolicy=low in WNOS.ini – Far from ideal and I’d prefer if these things worked as I’d hoped.
#2 I think Wyse / Dell are really missing a trick here. Now I have to go down the route of multiple WNOS.ini files. Can’t do this using the AD method so going to use the serial number or Mac address method.
Oh well, if was easy everyone would be doing it……..
