Hi,
I have created a new ISV license code according to all the steps documented in https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/isv-licensing. I am using a certificate issued by GoDaddy and added .cer file as a resource and to the license code. License file generation is completed successfully, but when I try to import the license file using the utility Microsoft.Dynamics.AX.Deployment.Setup.exe, utitlity fails with the message "The certificate associated with license <xxxxx> cannot be used to sign code". If I change the certificate format used from binary to base64 message changes to "The certificate associated with license <xxxxx> is not a trusted certificate".
I have no idea what could be the issue, CA certificate was added to local computer intermediate certification authorities, private key was added to trusted root certification authorities.
Thank you.
Best regards
CR
Hi Christian,
As of version 10.0.20, the key sizes higher than 2048 should be supported. What is the version of your build environment? Is that also 10.0.24? In that case, I would suggest you to log an incident for Microsoft Support.
Hi Andre,
I have acquired a EV code signing certificate from a known CA (SSL.com), but seems that 365 does not work with key sizes higher than 2048, throwing the error of certificate not trusted. I tried to check with a self-signed certificate using the same procedure of MS documentation and works with 2048, but not with 3072 or 4096. Do you know if there is a bug or issue related to that?
I am using product version 10.0.24 which supposedly allows those key sizes.
Hi, thank you for your answer. Indeed, Godaddy is no longer providing code signing certificates, so I had to acquire a certificate from another source.
The documentation mentions a "valid Authenticode certificate (X.509)". This is a code-signing certificate. Are you sure you are not using e.g. a SSL certificate or User/Client certificate? See also: www.keyfactor.com/.../
Thank you for your response. I have used a certificate in .cer extension encoded in SHA256 RSA with 2048 bit size, certificates asociated to license code were in both base64 and binary format, the private key is in .pfx extension and encoded in AES256-SHA256. I do not know if those values correspond to what you refer as the correct type of certificate.
Best regards.
Have you verified if you have the correct type of certificate used?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Sohaib Cheema 764 User Group Leader
Martin Dráb 619 Most Valuable Professional
André Arnaud de Cal... 603 Super User 2025 Season 2
