Authentication
To access private projects and sync your local State Tool with your ActiveState Platform account, you need to authenticate your State Tool installation.
Why Authentication is Required
Authentication is necessary to:
- Access private projects in your organization
- Sync local changes back to the Platform
- Share projects with team members
- Access your organization's managed distributions
How to Authenticate
To authenticate your State Tool with the ActiveState Platform:
state auth
This command will:
- Open your web browser to the ActiveState Platform login page
- Prompt you to sign in with your Platform credentials
- Generate an authentication token
- Automatically configure your local State Tool to use this token
Verify Authentication
To check if you're currently authenticated:
state auth --show
This will display your current authentication status and the associated user account.
Sign Out
To sign out and remove local authentication:
state auth --logout
Troubleshooting Authentication
Browser doesn't open automatically
If the browser doesn't open automatically during state auth, you can:
- Copy the URL displayed in the terminal
- Paste it into your browser manually
- Complete the authentication process
Authentication token expires
Authentication tokens have an expiration date. If your token expires:
- Run
state authagain to refresh your authentication - The State Tool will guide you through the re-authentication process
Corporate firewalls or proxies
If you're behind a corporate firewall, you may need to:
- Configure proxy settings for the State Tool
- Contact your IT administrator about allowlisting ActiveState domains
- See the network configuration troubleshooting guide for more details
Next Steps
Once authenticated, you can: