Has anything changed for signing modules for 8.3?
I signed an upgraded module with the same tools that work for 8.1, but uploading the module has issues:
Not intentionally, can you share the module so we can take a look?
The next reboot prompted to accept the certificate and the module loaded. So, there was something about the module import process that prevented or did not allow the certificate to be accepted. Chicken and egg issue perhaps.
Side note: the gateway the module is loaded on is in some sort of extreme resource constraint on cpu. To the point that loading a designer will sometimes timeout, and even restarting the gateway can timeout. We are working to resolve this before drawing any additional conclusions on the module’s behavior.
For sure - I can share the module if it would be helpful.
Did you have the unsigned version of the module installed already? This has happened to me, before in that situation, just uninstall the unsigned one, restart and install the signed one.
I had attempted the unsigned install, but I had not enabled debug mode, so it would not install that way. Perhaps it got far enough to cause the issue.
That will definitely cause the issue, for some reason it does all the certificate stuff before checking the signed or unsigned check. A reboot normally fixes this from memory.
I think there is still work being done on IAs side with this mechanism.
@Kevin.Herron Do you know if this behaviour is in an existing ticket in your system?
Can't find it, but may not be searching the right terms.
What's the repro steps here? Install the unsigned version of a module without -Dignition.allowunsignedmodules=true, then follow up with a signed version and you get a blank dialog like this? Something else?
Yes, and also I believe if you have the unsigned module installed already and try installing the signed module, it will do the same dialog.
Different module file names? If so, maybe this:
