Appearance
Account security and CI publishing
For contributor build dependencies, the local glob mitigation and expiring audit decision, see Build dependency security. Production container scans separately inspect OS packages, Node packages and the AWS credential helper.
For organisation membership, app permissions and the separate platform portal, see Organisations and access.
Open Account security in the dashboard. MFA uses standard time-based authenticator codes, compatible with common authenticator apps. It helps protect stolen passwords; it is not phishing-resistant authentication.
Email and password fields
Both sign-in portals and account dialogs validate email addresses before submitting. Leading and trailing spaces are removed from email addresses. The server applies the same validation and treats email addresses without regard to letter case.
New passwords must contain 14–256 characters and cannot consist entirely of spaces. Spaces within a password are preserved. Existing passwords are checked exactly as entered; signing in does not impose the new minimum length on an older password.
Use the eye button to show or hide a password while entering it. Passwords are hidden again when a form resets or its dialog closes. These controls also work with a keyboard and retain password-manager autocomplete.
Enable an authenticator
Enter your password, add the displayed setup key to your authenticator, then enter its six-digit code. Enrollment expires after ten minutes. MFA becomes active only after verification. Save the ten recovery codes in your password manager: they are shown once and each can be used once.
Enabling or disabling MFA signs out all sessions and revokes all automation credentials for the account. Disabling requires your password and a fresh authenticator or unused recovery code. Used authenticator codes cannot be replayed, including the code used during enrollment: wait for the next code before signing in.
The server encrypts authenticator secrets using a domain-separated key derived from its persistent session secret. Recovery codes and publishing tokens are stored only as hashes. Keep the deployment's encrypted backups and secret files together under operator-controlled recovery procedures. Changing or losing the session encryption secret without migration makes existing authenticator seeds unreadable. A password reset revokes sessions and tokens but does not remove MFA. Use a saved recovery code if your authenticator is unavailable; do not treat a password reset as a factor bypass.
Create a scoped publishing credential
Enable MFA first. You must be an organisation administrator or have Publisher access to the selected app. Select the app and deployment, then choose Create credential in Account security. Give it a name and an expiry of 7, 30 or 90 days. Choose publishing and/or native build registration. Creation requires password and a fresh factor. Viewers can manage their own account security but cannot create publishing credentials for a view-only app.
Organisation membership includes Viewer access to all the organisation's apps and deployments. Seeing an app does not grant publishing rights. An administrator must grant Publisher for that specific app. Removing Publisher returns the member to Viewer and revokes the app's publishing credentials; removing organisation membership removes read access as well.
Save the displayed token as a CI secret named OTA_TOKEN. In the same protected CI environment, set OTA_TOKEN_SERVER to the HTTPS origin shown with the token, for example https://ota.example.com. Both values belong in trusted CI settings outside the checkout; do not load them from a project-controlled .env file. The helper then reads them automatically:
sh
node ota.cjs publish ios --deployment StagingThe helper rejects a missing or mismatched OTA_TOKEN_SERVER before sending a token, even if --server was supplied. This prevents a changed ota.config.json from redirecting the credential to another host. Existing CI jobs must add this origin when updating the helper; no token regeneration is needed. The legacy names PUSHOTA_TOKEN and PUSHOTA_TOKEN_SERVER remain accepted for migration. Configure the token through your CI's secret settings, not in the command, project configuration, shell history or repository. Keep the matching signing private key in your publishing environment's secret storage as well. A token alone cannot sign a package.
A token belongs to exactly one account, app and deployment. Staging tokens cannot publish to Production, read other channel keys, promote, roll back, edit releases, change signing settings, manage collaborators or mint credentials. These actions remain in the dashboard. Native registration is app-wide metadata and needs its separate scope. Credentials are revalidated for existence, expiry, MFA and current app/deployment scope at storage transaction boundaries, including immediately before publication commits. Revocation blocks new requests and prevents an in-flight upload from publishing after revocation. Temporary uploaded bytes may remain until cleanup. Revocation does not undo an already committed release.
Normal CLI use prompts for your authenticator code when required. Password-on-stdin automation is rejected for MFA accounts; use a scoped token. For a non-MFA account, password-on-stdin requires an explicit trusted --server address. Tokens are never written to the helper's session files.
Permissions bind to immutable app and deployment IDs. Renaming an app or using the same display name in another account does not grant access. The CLI also pins the app ID in ota.config.json; a different identity stops the command before publishing or native registration.
Signing keys and project isolation
Private keys are separated by server and immutable app ID. Two apps with the same display name receive independent keys. Existing name-based keys are reused only when their public key matches the authorized app's registered key. Rerun setup with the updated helper to pin the app ID and safely migrate that matching key; the original remains available for older checkouts. A newly created or recreated app does not inherit a name-based key automatically.
Keep OTA_HOME outside every project. The helper resolves existing directory links before writing, so a linked path into the current project is rejected. Do not share a private directory with untrusted local users. Back up keys securely; the server holds public keys only. Losing the private key requires restoring it with --private-key or creating a new app trust identity in a new native store build.
Older management access keys are a separate legacy authentication mechanism. New scoped credentials do not silently revoke those keys; audit and remove unused legacy keys before broadening production access. MFA protects the dashboard login and new credentials, not separately configured external identity providers.
Implementation references: RFC 6238 and OWASP MFA guidance.