Why does signing in look different?
Overview
When launching Plannix Studio or running commands in the Plannix Build CLI, you will notice a streamlined, modern sign-in interface. With the launch of The Plannix Subscription, all authentication services have been consolidated into one secure identity architecture.
Legacy vs Unified authentication
| Authentication Capability | Legacy Setup | Unified SSO (Current) |
|---|---|---|
| Login Experience | Separate logins for editor, CLI, and dashboard | 1-Click browser SSO across all tools |
| Token Exchange Protocol | Static API tokens stored on disk | OAuth 2.0 PKCE with cryptographic rotation |
| Hardware Key & 2FA Support | SMS / TOTP only on web | FIDO2, WebAuthn & Touch ID/Face ID |
| Headless & CI/CD Authentication | Full user passwords required | Scoped Service Tokens (least-privilege) |
Why the sign-in experience changed
Historically, developers maintained disconnected credentials across the web dashboard, the IDE code editor, and the CLI terminal. Unification solves this fragmentation:
- Single Sign-On (SSO): Log in once in your browser, and both your editor and terminal are authenticated instantly.
- Enterprise identity: Compatible with corporate Okta, Google Workspace, and Microsoft Entra ID providers.
- Workspace switching: Easily toggle between personal open-source work and company repositories from the same user session.
The unified authentication flow
When you log in via the desktop application or command line:
- Your client launches your default web browser pointing to
accounts.plannix.web.id. - You authenticate using your email, Passkey, or corporate SSO identity.
- Upon approval, the browser exchanges a cryptographic OAuth 2.0 PKCE token via local loopback to your development client.
- Your client confirms the link and displays your active workspace.
CLI authentication flags
The Plannix Build CLI offers specialized flags for headless or containerized environments:
| Command / Flag | Description | Use Case |
|---|---|---|
plannix login | Standard interactive login via default browser | Local developer workstation |
plannix login --auth-code | Prints an authorization URL and prompts for pasted code | VPNs blocking local loopback ports |
plannix login --no-browser | Outputs URL for authorization on another machine | Remote SSH bastion or headless Linux VM |
plannix logout | Revokes active session tokens from the local machine | Shared team workstations |
BashTerminal
# Interactive browser sign-in
$ plannix login
Opening accounts.plannix.web.id in your browser...
[OK] Logged in as alex@company.com (Workspace: Plannix Team)Troubleshooting sign-in issues
If you encounter difficulties logging in:
Local Loopback Blocked: Some VPNs or corporate proxies block local loopback callbacks (e.g.
http://127.0.0.1:4040). If the browser completes login but your terminal hangs, pass the --auth-code flag to manually paste your token:plannix login --auth-codeEnhanced security and session tokens
Unified sign-in introduces industry-standard security safeguards:
- Zero plain-text password storage on client machines.
- Hardware token 2FA (YubiKey, WebAuthn, Touch ID) enforcement.
- Automatic session expiration and remote revocation from the Plannix Console.