search

dymosoftware / DCD-SDK-Sample

DYMO Connect SDK Samples
Other
60 stars 26 forks source link

Unable to connect to DYMO Connect #49

Open EdwardFinn opened 2 years ago

EdwardFinn commented 2 years ago

Issue is actually with DYMO Connect, but DYMO Customer Care redirected me here.

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. image

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. image

This instantly fixes the connectivity issue without even needing an application restart image

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

  1. Login to a domain managed machine as a unprivileged user
  2. Run DYMO Connect installer
  3. ON UAC prompt, login as a domain admin (Local Admin may also work)
  4. Confirm DYMO connect is working with Diagnose button
  5. Reboot
  6. Login as unprivileged user
  7. Run Diagnose and see SSL error
dymosoftware commented 2 years ago

I was aware of this issue recently, and I added this issue into backlog for more investigation. DYMO Connect web service took a big step from WCF Service Host with .NET Framework 4.5 to Kestrel which is a cross-platform web server for ASP.NET Core 3.1. You know, this issue will be fixed after adding either "Everyone" user or a domain user group with "Read" permission on the localhost private certificate.

ashleybot commented 2 years ago

I only have local admin privileges to update and maintain the software. Larger organizations like mine do not give everyone permissions to create domain user groups or modify permissions for other users. Do you have a timeline on this update?

MikeB-007 commented 1 year ago

I'm not convinced that taking the private key, and making it public is really a valid solution. I'd like to see this not be required.

EdwardFinn commented 1 year ago

Following up hoping for an update. This issue continue to burden our support teams as our customers install your software and it ceases to function after the first reboot/logout, requiring us to hand hold them through remediation.

Fhrosty commented 1 year ago

Following up as well. A company I'm doing work for has heavy several dozen 450 turbos and heavy reliance on the javascript framework. Now that Microsoft has completely removed Internet Explorer, this company cannot continue using an older solution as a workaround. I have tried a fresh install of Dymo Connect 1.4.3.131 and get the same error as the original poster reported almost a year ago.

EdwardFinnNMS commented 1 year ago

This continues to be an ongoing pain point for my organization. Before we abandon DYMO for another vendor, is there any timeline for resolution?