Docs · App & code signing
Cross-platform CLI (preview)
0.1.x installs anonymously from the public API (GET /v1/public/cli/versions/{version}) or the
setup-liminal-keys Action — no GitHub token.
Pin semver and SHA-256 per runner OS/arch. Mac codesign still uses the Host app and sign@v1.
Install (GitHub Actions)
Pin version and sha256 for this runner (example: 0.1.10, Ubuntu x64). Metadata:
https://api.liminalkeys.com/v1/public/cli/versions/0.1.10.
- uses: LiminalKeys/setup-liminal-keys@v1
with:
version: "0.1.10"
sha256: "c9495db59e9433fcb2ac118b9a4e7d18421714da7d42780a39f6af9899c711d5"
Install (manual / curl)
Download via the API asset URL, verify SHA-256 against metadata, then add to PATH (Windows: liminal-keys-win-x64.exe).
curl -fsSL "https://api.liminalkeys.com/v1/public/cli/versions/0.1.10/assets/liminal-keys-linux-x64/download" -o liminal-keys
shasum -a 256 liminal-keys # expect c9495db59e9433fcb2ac118b9a4e7d18421714da7d42780a39f6af9899c711d5
chmod +x liminal-keys
Tenant admin (admin)
Sign in with the dedicated CLI public client (CIAM user flow — not the Console SPA). Session is stored locally for subsequent admin commands.
liminal-keys admin login
liminal-keys admin logout
Workspace tenant id
liminal-keys admin platform me
Requires an linked workspace. Use the printed tenant GUID for LIMINAL_KEYS_TENANT_ID and OIDC audience https://api.liminalkeys.com/t/<tenant-guid>.
ASC key import requires Active or Comped entitlement on your workspace (see Console Billing).
App Store Connect keys
In App Store Connect → Users and Access → Keys, create a key with access to upload builds. For team keys we recommend the App Manager role (enough for uploads). Admin keys also manage users and settings CI does not need. Liminal Keys cannot read a key’s role — confirm in App Store Connect. Download the .p8 once.
Import reads the file from disk and never prints key material. Choose --key-type team or individual. Console import supports Check with Apple before save; the CLI validates format on upload.
liminal-keys admin asc import --file ~/Downloads/AuthKey_ABCDE12345.p8 --key-id ABCDE12345 --issuer-id 00000000-0000-0000-0000-000000000000 --key-type team --display-name "Acme iOS upload"
Note the returned Liminal key UUID (66666666-7777-8888-9999-aaaaaaaaaaaa in examples).
Allow mint (policy rule)
In Console Policy rules, choose Issue App Store Connect upload tokens, pick the imported key, subject CI workload (trusted issuer), select your GitHub trust, then Apply policy. Or draft the same allow rule from the CLI:
liminal-keys admin asc allow-mint --asc-key-id 66666666-7777-8888-9999-aaaaaaaaaaaa --ci-trust-id bbbbbbbb-cccc-dddd-eeee-ffffffffffff --apply
CI: mint and upload
After enroll, mint a JWT valid for about 10 minutes (expMinutes=10). Successful mints appear in Activity as asc_token_issued (masked token metadata — not the JWT).
liminal-keys asc token --asc-key-id 66666666-7777-8888-9999-aaaaaaaaaaaa --json
liminal-keys upload --ipa dist/Acme.ipa --bundle-id com.example.acme
Set repository variable LIMINAL_KEYS_ASC_KEY_ID to the Liminal UUID from import (not Apple’s 10-character Key ID).
CI enroll and sign (digest)
liminal-keys ci enroll --tenant-id 11111111-2222-3333-4444-555555555555 --ttl 60m --identity <cert-sha1> --json
liminal-keys sign --identity <cert-sha1> --file dist.bin
liminal-keys ci unenroll --json
Always run ci unenroll in a final step with if: always(). Requires permissions: id-token: write for GitHub OIDC.
Sample workflows
ASC broker smoke (Ubuntu: enroll → mint → Apple GET /v1/apps).
Release templates may expose asc_mint_smoke_only to run mint checks without a full archive, and asc_upload_mode: p8-altool as a legacy fallback when the broker path is unavailable.
Related: CI overview · CI reference