I’m writing you because I want to use https instead of http protocol when my users connect to QSDA. The idea is to use a ssl certificate signed by my internal CA. QSDA Security isn’t enabled.
I followed the instructions mentioned in the link below with no luck (QSDA Help), I mean when I enabled SSL protocol the certificate opened or assigned isn’t the one I chose using the netsh command.
Do you have any idea about what I’m wrongly doing?
The netsh should only be used when the QSDA Auth is enabled. (the help says it will do not harm – incorrect for many customers – I will update the help).
Currently if you have not enabled QSDA Auth, the certificate selection is made by matching the host name used in the URL with the first certificate found with the same exact or wildcard name used as either subject or alternate name. There is no way to bind to a specific certificate, like by using a thumbprint. Do you have such a requirement?
After implementing HTTPS and QSDA Auth I saw that everytime we open the QSDA url using https an error response appears 2 seconds and then QSDA is opened. If without closing the browser I open again QSDA I don’t see any error however, if I close the browser and open again QSDA the same error appear. This behavior is happening when I use MS Edge, I don’t have noticed it with Firefox. Here you have an example with MS Edge (sorry is in Spanish).
I don’t have seen any error on this log. I think it’s something that happens between MS Edge and QSDA webpage. Have you tested it with MS Edge? Like I said, with Firefox it doesn’t happen. And it started to happen when I enabled https.
I guess that something configured in MS Edge is avoiding in a first step to open QSDA. Like I said, with Firefox I don’t see that issue.
On the other hand I noticed that enabling QSDA Auth the performance is worse than without it. So finally I have disabled https and QSDA Auth till I find where is the issue. Are you aware about a performance deterioration when QSDA Auth is enabled?