Skip to content
DOCS

Get your plugin signed

Set up code signing for macOS and Windows before your first release, in the right order, and check it worked.

freqlab.co only lists plugins whose files are signed, and notarized on macOS, and signed plugins open without security warnings. Your cloud builds do the signing; you set up the credentials once.

Start early. Windows signing needs Microsoft to check your identity, which takes 1 to 20 business days. Set up Windows first, and do macOS while you wait. Azure checks individuals in the US and Canada only, and organizations in some countries: see Sign for Windows.

Windows: Azure Artifact SigningLink to this section

About $9.99 a month. You need a paid Azure subscription.

  1. Create an Artifact Signing account, give yourself the Identity Verifier role, and start your identity validation. Then wait for it to show Completed.
  2. Create a certificate profile and an app registration, and give the app the signing role.
  3. Add it in Signing credentials on creator.freqlab.co.

Every step, with Azure's exact menus: Sign for Windows. A .pfx certificate isn't trusted by Windows, so its builds show as Not signed.

macOS: an Apple Developer API keyLink to this section

The Apple Developer Program costs $99 a year. No Mac needed.

  1. Enroll in the Apple Developer Program.
  2. Create a key under Team Keys in App Store Connect, with the Developer role, and download its .p8 (only once).
  3. Add it in Signing credentials, download the certificate request, create a Developer ID Application certificate at Apple as the Account Holder, and upload it back.

Every step: Sign and notarize for macOS.

Check it workedLink to this section

  • Your macOS credential shows Valid until with a date (not Pending certificate). Your Azure credential shows Active, with its certificate profile.
  • Start a cloud build with your credentials picked for both platforms. When it finishes, its files show Signed, and Notarized on macOS.

Keep it workingLink to this section

Freqlab emails you before a certificate expires, but it can't see two Azure dates. Put them in your calendar: the client secret (up to 24 months) and the identity validation. See Keep it working.

Next: Pass the Freqlab Standard, the other thing freqlab.co checks.