Duo Enterprise License Access Process for Staging Environment
This guide explains how to self-service Duo Enterprise license access in the staging environment for backend developers, SREs, and other engineers who need to test AI features.
Prerequisites
Section titled “Prerequisites”- Active staging.gitlab.com account, if you do not have one go to staging to sign in with your GitLab email account
- Existing Ultimate/Premium license on staging
- GitLab.org group membership
Access Request Process for Zuora Sandbox
Section titled “Access Request Process for Zuora Sandbox”Before you can manage licenses in Zuora, you’ll need access to the Zuora Central Sandbox environment:
- Create an Access Request issue in the access-requests project
- Request access to [Staging] Zuora Central Sandbox (Tenant ID: 10000796)
- Provide a justification (e.g., “Need to test Duo Enterprise licensing”)
- Your manager will need to approve the request with proper labels
After approval, a member of the fulfillment team will provision your Zuora access.
Self-Service Process
Section titled “Self-Service Process”Access License Management
Section titled “Access License Management”- Log in to customers.staging.gitlab.com using your staging.gitlab.com credentials
- Locate and copy your Zuora subscription ID (format: A-ABC123…)
Add Duo License Through Zuora
Section titled “Add Duo License Through Zuora”- Access Zuora through Okta SSO (Central Sandbox - Staging environment)
- Use search bar (or CMD+K) to locate your subscription using the Zuora ID
- Click “Create order”
- Select “Add product”
- Choose Duo Enterprise version
- Click the arrow next to the product
- Select desired renewal rate
- Check the box to confirm selection
- Click “Add product”
- Click “Activate”
Verify License Access
Section titled “Verify License Access”- Sign into staging.gitlab.com
- Navigate to any project
- Open Web IDE or Code Suggestions feature
- Confirm Duo functionality is active
Troubleshooting
Section titled “Troubleshooting”If you encounter issues, check the following:
| Symptom | Verification Steps | Resolution |
|---|---|---|
| Features not available | Check subscription status in customers.staging.gitlab.com | Follow self-service steps above |
| Need upgrade from Duo Pro | Check current license type in subscription details | Create new order for Duo Enterprise |
| Authorization errors | Verify Okta access and permissions | Contact #g_provision |
The GitLab AI Features Health Check will surface specific errors if there are issues with:
- License validation
- Feature availability
- Access permissions
Additional Information
Section titled “Additional Information”- Licenses are managed at the namespace level
- The gitlab-org namespace on staging has a custom setup
- Most developers should use staging environment rather than local setup
- Duo Enterprise is preferred over Duo Pro for complete feature testing
Related Documentation
Section titled “Related Documentation”- AI Features Documentation
- Code Suggestions Setup Guide
- License Management Guidelines for Code Suggestions
- CLOUD_CONNECTOR_SELF_SIGN_TOKENS environment variable
Support Channels
Section titled “Support Channels”For issues with self-service process:
- Primary Support: #g_provision Slack channel
- Secondary Support: #s_fulfillment Slack channel
- Documentation Issues: GitLab AI Documentation
- Keep subscription ID handy for future reference
- Automatic seat assignment is planned for future implementation
- Regular validation of license status is recommended