- This topic has 27 replies, 4 voices, and was last updated 2 years, 9 months ago by .
- You must be logged in to reply to this topic.
Yes, I use RDS-GW-WEB. ######. Fr
https://RDS-GW-WEB.######. Fr
But, does not work
Which certificate should be put ?
That of the RDS-BRK or RDS-GW-WEB server?
Next time would be nice if you switch WMS GUI to English before doing a screenshot 😉
Are you using self-signed certificates on each RDS server? Aren’t you using a Certificate Authority? That way you would just have to install the CA root cert to all clients.
CG
Sorry, next time I will switch the interface to English.
I mainly use self-signed certificates
For information, I’m going to version 3.2.1 for test
Hi,
The update has not changed anything
Hello,
I am going through an ADCS but it does not work either
Hi,
It is resolved
I correctly reassigned my certificate on my RDS-BRK server
Thk you
Good morning everyone.
Could somebody find a fix for this?
Before , in thinOS 8.6 and FTP server, we had this settings on the [email protected]
VDIBroker=https://BROKERNAME.<fqdn> AutoConnectList=”Remote-Application-Needed”
ConnectionBroker=Microsoft
AddCertificate=brokername.cer
Now that we use ThinOs 9, we tried all suggestions here but all the time, Wyse end with message “Connection failed to broker https://BROKERNAME.<fqdn> error ==>Error:Error”
Broker certificate was uploaded and used. We tried with
-brokername
-FQDN broker name
-https://brokername
-https://FQDN broker name
None worked. Only when removing the ‘S’ from https, event log display a message related to certificate that is not matching
Thanks for your suggestions
Emmanuel
Do you use a self-signed certificate for the broker, or do you have a full CA set up? Or do you use official certificates?
CG
Hi, I’m using a self-signed certificate
E.
and you importing this certificate to the Thin Client, correct?
Yes, and I can see it well imported on the Wyse device. When displaying it from the Thin client we can see that it’s the good one
Thank you
E.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |