Connector Authentication

​

Authentication Methods

​

No Authentication

{
  "auth_config": {
    "type": "none"
  }
}

​

Bearer Token

{
  "auth_config": {
    "type": "bearer",
    "token": "sk-abc123..."
  }
}

​

Basic Authentication

{
  "auth_config": {
    "type": "basic",
    "username": "user",
    "password": "pass"
  }
}

​

API Key (Custom Header)

{
  "auth_config": {
    "type": "api_key",
    "header_name": "X-API-Key",
    "key_value": "your-key"
  }
}

​

OAuth 2.0

{
  "auth_config": {
    "type": "oauth2",
    "provider": "custom",
    "authorization_url": "https://auth.example.com/oauth/authorize",
    "token_url": "https://auth.example.com/oauth/token",
    "client_id": "your-client-id",
    "client_secret": "your-secret",
    "scopes": ["read", "write"]
  }
}

​

Configuring Authentication

​

REST Connector

1. Connectors > Select connector
2. Click Authentication
3. Choose method
4. Enter credentials
5. Click Test
6. Click Save

​

MCP Registry

1. Connectors > Select connector
2. View required credentials (shown during setup)
3. Enter API key or authorize OAuth
4. Connector tests automatically

​

Custom MCP

1. Connectors > Select connector
2. Click Authentication
3. Set headers or environment variables
4. Provide credentials
5. Test connection

​

Encryption

​

At Rest

• Encryption key managed by Noorle
• Credentials never logged
• Safe to store in configuration

​

In Transit

• End-to-end encryption
• Certificate validation
• No credential exposure

​

Display

• Display only last 6 characters
• Example: sk-abc123...
• Full key shown only when first created

​

OAuth 2.0 Flow

• User never shares password
• Credentials stay on service
• Automatic refresh
• Revocable at any time

​

Scope Management

OAuth scopes: ["repo", "user:email"]

• ✓ Access repositories
• ✓ Read email addresses
• ✗ Delete repositories (not requested)
• ✗ Modify settings (not requested)

​

Credential Rotation

​

Rotate Bearer Token

1. Generate new token from service
2. In connector, click Edit Authentication
3. Update token value
4. Test new token works
5. Save

​

Rotate OAuth Token

1. Connector auto-rotates OAuth tokens
2. No action needed
3. Old token revoked automatically
4. New token fetched before expiry

​

Rotate API Keys

1. Generate new key from service
2. In connector, click Edit Authentication
3. Update key value
4. Test works
5. Optionally disable old key at service

​

Testing Authentication

1. Connectors > Select connector
2. Click Test
3. Select operation/tool
4. Provide sample input
5. Execute
6. Verify success

• Credentials are correct
• Token hasn’t expired
• Key has required permissions
• Service is online

​

Common Auth Issues

​

”Invalid Credentials”

• Double-check API key or token
• Verify correct auth type
• Check if secret characters copied correctly
• Try regenerating token/key

​

”Insufficient Permissions”

• OAuth scopes may be too limited
• Re-authorize with more scopes
• Check service role/tier
• Verify account permissions

​

”Token Expired”

• OAuth tokens auto-refresh (should be automatic)
• Bearer tokens: manually update
• Check if service revoked access
• Re-authorize OAuth flow

​

”Authentication URL Not Found”

• OAuth endpoints may have changed
• Check service documentation
• Verify correct provider configuration
• Try custom OAuth setup

​

Security Best Practices

​

API Keys

• Treat like passwords
• Store in secret manager, not code
• Rotate regularly (quarterly)
• Use minimum scope/permissions
• Disable unused keys immediately

​

OAuth

• Review scopes before authorizing
• Revoke access if no longer needed
• Check authorized apps regularly
• Only use for necessary integrations

​

Multi-factor Authentication

• GitHub
• Stripe
• Cloud services

​

Audit Log

1. Connectors > Select connector
2. View Activity tab
3. Check recent usage
4. Alert on suspicious activity

​

Credential Deletion

1. Delete the connector entirely
   • Credentials removed
   • Service revoked (if OAuth)
   • Cannot undo

2. Update to different auth method
   • Old credentials replaced
   • Previous method no longer used
   • Still cannot undo

​

Integration-Specific Auth

​

Stripe

• Type: Bearer
• Token: sk_live_... or sk_test_...
• Source: https://dashboard.stripe.com/account/apikeys

​

GitHub

• Type: Bearer
• Token: Personal access token from https://github.com/settings/tokens
• Scopes: repo, read:org

​

Slack

• Type: OAuth 2.0 or Bearer
• OAuth scopes: chat:write, channels:read
• Token: Xoxb-… (bot token)

​

Next Steps

• REST Connectors
• MCP Registry
• Custom MCP
• Parameter Mapping