Skip to main content

Node Provider Authentication

Learn how to authenticate as a QuikDB node provider and manage your credentials securely.

Create Your Node Provider Account​

Before using the CLI, you'll need a QuikDB node provider account:

  1. Sign up at nodes.quikdb.com
  2. Verify your email address
  3. Complete your provider profile setup
  4. Generate an API token from your dashboard

CLI Authentication​

Interactive Login​

The easiest way to authenticate:

# Interactive authentication
quikdb-nodes auth

# Follow the prompts to enter your token

Direct Token Authentication​

If you have your API token ready:

# Authenticate with token
quikdb-nodes auth --token YOUR_API_TOKEN

Verify Authentication​

Check if you're properly authenticated:

# Check authentication status
quikdb-nodes auth status

# View current user info
quikdb-nodes info

Node Provider Token Management​

Generate New Token​

From your QuikDB node provider dashboard:

  1. Navigate to Settings → API Tokens
  2. Click Generate New Token
  3. Select Node Provider permissions
  4. Give it a descriptive name
  5. Copy the token immediately (you won't see it again)

Using Environment Variables​

For automation and multi-node setups:

# Set environment variable
export QUIKDB_TOKEN="your_api_token_here"

# CLI will automatically use the environment variable
quikdb-nodes info

Token Security Best Practices​

  • ✅ Store tokens securely - Never commit tokens to version control
  • ✅ Use environment variables - Especially for multiple nodes
  • ✅ Rotate tokens regularly - Generate new tokens periodically
  • ✅ Use descriptive names - Name tokens by their purpose/location
  • ❌ Don't share tokens - Each node should have unique tokens when possible

Configuration File​

The CLI stores your authentication in ~/.quikdb-nodes/config.json:

{
  "version": "1.0.0",
  "endpoint": "https://api.quikdb.com",
  "token": "encrypted_token_here",
  "nodeProvider": {
    "id": "provider_12345",
    "email": "provider@example.com",
    "name": "Node Provider Name"
  },
  "lastUpdated": "2024-01-01T12:00:00.000Z"
}

Manual Configuration​

You can also manually edit the config file:

# View current configuration
quikdb-nodes config show

# Set specific values
quikdb-nodes config set endpoint "https://api.quikdb.com"
quikdb-nodes config set token "your_token"

# Reset configuration
quikdb-nodes config reset

Authentication Troubleshooting​

Invalid Token​

If you get authentication errors:

# Check token validity
quikdb-nodes auth status

# Generate a new token from dashboard
# Then re-authenticate
quikdb-nodes auth --token NEW_TOKEN

Connection Issues​

If you can't connect to QuikDB:

# Test connectivity
quikdb-nodes info --network

# Check endpoint configuration
quikdb-nodes config show

# Try with debug mode
quikdb-nodes --debug auth status

Permission Denied​

If operations fail with permission errors:

  1. Check token permissions - Ensure your token has necessary scopes
  2. Verify account status - Make sure your account is active
  3. Contact support - If issues persist

Multiple Environments​

Development vs Production​

Use different tokens for different environments:

# Development environment
export QUIKDB_TOKEN="dev_token_12345"
quikdb-nodes auth

# Production environment  
export QUIKDB_TOKEN="prod_token_67890"
quikdb-nodes auth

Team Management​

For teams:

  • Individual tokens - Use separate tokens for each node when possible
  • Descriptive naming - Name tokens by location/purpose (e.g., "home-server-1")
  • Environment separation - Keep development and production tokens separate

Logout​

To remove stored credentials:

# Logout from CLI
quikdb-nodes auth logout

# This removes the stored token but doesn't revoke it
# To fully revoke, delete the token from your dashboard

Next Steps​

After authentication:

  1. List your node in the marketplace
  2. Monitor your node performance
  3. Optimize your earnings

Need help? Check our Support Guide or join our Discord Community.