Overview
Authentication commands manage your App Store Connect API credentials. Credentials are stored securely in the system keychain when available, with a config file fallback.Authentication Resolution
Credentials are resolved in this order:- Selected profile (keychain or config)
- Environment variables (fallback for missing fields)
--strict-auth or ASC_STRICT_AUTH=true to fail when sources are mixed.
Commands
asc auth init
Create a template config.json for authentication.
Overwrite existing config.json
Write config.json to
./.asc in the current repo instead of ~/.ascOpen the App Store Connect API keys page in your browser
asc auth login
Register and store App Store Connect API key credentials.
Friendly name for this key
App Store Connect API Key ID
App Store Connect Issuer ID
Path to private key (.p8) file
Store credentials in config.json instead of keychain
When bypassing keychain, write to
./.asc/config.jsonValidate credentials with a lightweight API request
Skip JWT and network validation checks
asc auth switch
Switch the default authentication profile.
Profile name to set as default
asc auth logout
Remove stored API credentials.
Remove all stored credentials (default behavior)
Remove a named credential
asc auth status
Show current authentication status.
Output format:
table, jsonShow detailed storage information
Validate stored credentials via network
asc auth doctor
Diagnose authentication configuration issues.
Output format:
text, jsonAttempt to fix issues where possible
Confirm applying fixes (required with
--fix)Environment Variables
ASC_KEY_ID- API Key IDASC_ISSUER_ID- Issuer IDASC_PRIVATE_KEY_PATH- Path to .p8 fileASC_PRIVATE_KEY- PEM-encoded private keyASC_PRIVATE_KEY_B64- Base64-encoded private keyASC_BYPASS_KEYCHAIN- Set to1,true,yes,y, oronto bypass keychainASC_STRICT_AUTH- Set totrue,1,yes,y, oronto fail on mixed credential sourcesASC_PROFILE- Select a named profile
