DYMO Connect Service is failing to access the private key of the local cert when the application is installed by a domain administrator, but the logged in user is not the same user, or is less privileged. Issue does not present until a system reboot as the service is started under the administrators account following installation, but run as the logged in user on reboot.
This can be observed by using the diagnose command from the task tray.
Editing the permission on for the private key to 'DYMO Root CA (for localhost)' can resolve this. For example by granting read permissions to all domain users.
This instantly fixes the connectivity issue without even needing an application restart
I utilize this functionality for a corporate website, we've purchased and provided clients with hundreds of 450 LabelWriters, and have started adding 550 series LabelWriter for which we also plan to purchase several hundred of. With this we're started migrating from DLS8 to DYMO Connect and this issue burdens both our support staff and our clients, specifically some of our smaller clients with only contract IT staff that sometimes takes days or weeks to follow this simple work around.
Please enhance the installer so that the certificate works for all users of the PC or so that the installation user can select users/groups that can access the certificates private key.
Steps to reproduce.
Login to a domain managed machine as a unprivileged user
Run DYMO Connect installer
ON UAC prompt, login as a domain admin (Local Admin may also work)
Confirm DYMO connect is working with Diagnose button
Reboot
Login as unprivileged user
Run Diagnose and see SSL error
*Note, this issue was reported by me, 2 years ago, here. It was acknowledged by Dymo as an issue, but it remains unresolved, unpatched and a constant source of friction with customers.
DYMO Connect Service is failing to access the private key of the local cert when the application is installed by a domain administrator, but the logged in user is not the same user, or is less privileged. Issue does not present until a system reboot as the service is started under the administrators account following installation, but run as the logged in user on reboot.
This can be observed by using the diagnose command from the task tray.
Editing the permission on for the private key to 'DYMO Root CA (for localhost)' can resolve this. For example by granting read permissions to all domain users.
This instantly fixes the connectivity issue without even needing an application restart
I utilize this functionality for a corporate website, we've purchased and provided clients with hundreds of 450 LabelWriters, and have started adding 550 series LabelWriter for which we also plan to purchase several hundred of. With this we're started migrating from DLS8 to DYMO Connect and this issue burdens both our support staff and our clients, specifically some of our smaller clients with only contract IT staff that sometimes takes days or weeks to follow this simple work around.
Please enhance the installer so that the certificate works for all users of the PC or so that the installation user can select users/groups that can access the certificates private key.
Steps to reproduce.
*Note, this issue was reported by me, 2 years ago, here. It was acknowledged by Dymo as an issue, but it remains unresolved, unpatched and a constant source of friction with customers.