No matter what name I enter for a server name it is changed to local host. I don't have this problem in the other configurators. I was told I can not use localhost for SSL servers because it does not match what the authority has on file.
No matter what name I enter for a server name it is changed to local host. I don't have this problem in the other configurators. I was told I can not use localhost for SSL servers because it does not match what the authority has on file.
Hi Chad, can you give me more details regarding the mobile server version? We were not able to reproduce this issue on the latest version. Have you opened a support case yet?
Version 10.4.1.114590
I have not opened a support case, it is not causing any problems at the moment. But it concerns me that something is overriding what I enter into the field.
I enter into the new connection field subdomain.domain.com and the repository name into the repository field.
I click Add
The prompt comes up for Authentication and the Server Name gets populated with what I typed into the new connection field for 1 second, then it is overridden by "localhost"
I have tested 5 times, the wait time before overwrite is almost exactly 1 second and always the same.
After filling out the authentication window, the server name remains localhost.
Since we enabled SSL connections on the Laserfiche Service (we are not even using it locally, only for network connections) other Laserfiche utilities will not connect using the name localhost. I do not know why, this is why we now use the subject name of the certificate (bound to port 443) regardless of if we are using SSL to connect to LFS or not, it seems to be a new requirement.
In the past, we only need to worry about using the proper name when utilizing the certificate.