Signing credentials
How code signing and notarization work for cloud builds, which option to pick for macOS and Windows, and what happens when a credential is missing or expires.
Cloud builds can sign your plugins with your own credentials, so they open without security warnings. Signing is optional: unsigned builds still work, but macOS blocks them until the user allows them, and Windows shows a SmartScreen warning. freqlab.co only lists signed releases, notarized on macOS.
Open Signing credentials in your account.
Pick an optionLink to this section
| Platform | Option | Cost | What users see |
|---|---|---|---|
| macOS | API Key (recommended) | Apple Developer Program, $99/year | Signed and notarized. No Mac needed to set up |
| macOS | Certificate (.p12) | Apple Developer Program, $99/year | Signed and notarized. Needs a Mac to export the certificate |
| Windows | Azure Artifact Signing (recommended) | Azure, $9.99/month (Basic) | Signed, and Windows trusts it, so SmartScreen warns less |
| Windows | Certificate (.pfx) | Your own certificate | Signed, but shows as Not signed: Windows doesn't trust a certificate exported as a .pfx |
Setup steps: Sign and notarize for macOS and Sign for Windows.
Signing and notarizationLink to this section
- Signing stamps your plugin with your identity, so macOS and Windows know who made it and that it hasn't changed.
- Notarization (macOS only) sends each signed build to Apple, which checks it and approves it. Both macOS options notarize with your App Store Connect API key.
Your credentialsLink to this section
- Each platform can have up to 5 credentials. The first one you can use becomes the Default (an API Key becomes it once its
.ceris uploaded, if you have no other default); Set as default changes it. - Enable and Disable turn one on or off without deleting it. You can't make a disabled credential the default, and disabling the default hands it to your newest enabled one.
- Update replaces a credential's files or details. To switch to another option, delete it and add a new one.
- A
.p12or.pfxis checked when you save it. If it can't be opened with the password you gave, or a macOS one isn't a Developer ID certificate, it isn't saved and you're told why. - In an organization, only the owner or an admin can change its credentials. Members see a note that the owner or an admin manages them, and can still use them for builds.
Your secrets are encrypted with a key kept in a dedicated vault, and only used to sign your builds.
Which credential a build usesLink to this section
When you start a cloud build in Freqlab Studio or Freqlab Express, you pick the credential for each platform, or None for an unsigned build. The picker starts on your default, or on None if you have no enabled credential for that platform. It only lists enabled credentials, so an API Key still waiting for its .cer isn't offered until you upload it.
| If the credential is | The build |
|---|---|
| Expired | Fails before it starts: update it with a new certificate |
| Deleted or disabled after you started the build | Fails, saying the credential was deleted or disabled. Pick another and build again |
Waiting for its .cer, and you have no other enabled one for that platform | Fails, asking you to upload the .cer (pick None to build unsigned) |
| None, or you have none for that platform | Isn't signed |
ExpiryLink to this section
Certificates show Valid until, then Expires in N days in the last 30 days, then Expired. In the last 30 days Freqlab also emails you daily (for an organization's credential, the owner), and your Dashboard lists it under things that need you.
Freqlab can't warn you about everything that expires:
- Azure client secrets and identity validations: see Sign for Windows.
- A revoked App Store Connect key: notarization fails until you update the credential with a new one.