Certificate file errors (PEM, private key, password)
Errors when you choose your own certificate file for an App ID connection, and how to make a file the app accepts.
The easiest way is to let the app create the certificate (Connections → App ID → Create certificate) and upload its .cer file to the app registration. If you use your own certificate:
| Message | Fix |
|---|---|
| The certificate file must be a PEM file that contains both the certificate and its private key (not password-protected). | Convert it. From a .pfx: openssl pkcs12 -in cert.pfx -out cert.pem -nodes – the result holds both parts with no password. |
| The private key in the file does not belong to the certificate. | The file mixes two certificates. Export the certificate and its own key again. |
| AADSTS700027 when testing | The public part (.cer) isn't uploaded to the right app registration – see Microsoft sign-in errors. |
Keep the PEM file private: anyone with it can sign in as the app. The app stores its own certificates protected for your Windows account.
Was this article helpful?
Updated 2026-10-26