Auth Configs

Auth Configs is the central hub for managing authentication and credentials across all your integrations. Whether you're connecting to popular OAuth2 providers, enterprise databases, or custom APIs, Auth Configs provides secure, reusable credential management that powers your workflows and agents.

Overview

Auth Configs serves as the foundation for all authentication in FlowGenX. When you connect an application, create a workflow integration, or set up an agent toolkit, Auth Configs handles the secure storage and management of your credentials.

Why Auth Configs?

• Centralized Management: Store all credentials in one secure location
• Reusability: Use the same auth config across multiple connections and workflows
• Security: Enterprise-grade encryption and access control
• Automatic Refresh: OAuth tokens are automatically refreshed before expiration
• Audit Trail: Track who accessed what and when

Authentication Types

FlowGenX supports three primary categories of authentication configurations, each designed for different integration scenarios.

OAuth2 Provider

OAuth2 Provider auth configs enable secure connections with platforms that support the OAuth 2.0 protocol. FlowGenX includes pre-configured support for the most popular providers, and you can add custom OAuth2 configurations for any compliant service.

Supported Providers

FlowGenX supports a wide range of OAuth2 providers out of the box:

Creating an OAuth2 Provider Config

1. Navigate to Auth Configs: Go to Integration Studio → Auth Configs
2. Click Create New: Select "OAuth2 Provider" as the type
3. Select Provider: Choose from the list of supported providers or select "Custom OAuth2"
4. Configure Credentials:
   • Client ID: Your OAuth application's client ID
   • Client Secret: Your OAuth application's client secret
   • Scopes: Select the permission scopes required for your integration
5. Authorize: Click the authorization button to complete the OAuth flow
6. Save: Your auth config is now ready to use

Custom OAuth2 Configuration

For OAuth2 providers not in our pre-built list, you can create a custom configuration:

OAuth2 Features

• Automatic Token Refresh: Access tokens are automatically refreshed before expiration
• Scope Management: Request only the permissions your integration needs
• Secure Storage: Tokens are encrypted at rest and in transit
• Multi-Account Support: Connect multiple accounts from the same provider

Native Connector

Native Connectors provide pre-built, secure authentication forms for 100+ popular integrations. These connectors handle the complexity of connecting to databases, message brokers, file storage systems, and other enterprise services.

Supported Categories

Creating a Native Connector Config

1. Navigate to Auth Configs: Go to Integration Studio → Auth Configs
2. Click Create New: Select "Native Connector" as the type
3. Select Connector: Browse or search for your target system
4. Fill Authentication Form: Complete the connector-specific form with your credentials
5. Test Connection: Verify the connection works before saving
6. Save: Your native connector auth config is ready

Connector Configuration Examples

PostgreSQL Database:

Amazon S3:

Kafka:

Webhook Support

Native Connectors can include webhook configuration for connectors that support real-time triggers:

Custom Authentication

For APIs and services with non-standard authentication requirements, Custom auth configs provide flexible options to handle any authentication scheme.

Custom Auth Types

No Authentication

Use this option for public APIs or internal services that don't require authentication.

{
  "type": "no_auth",
  "name": "Public Weather API"
}

OAuth 2.0 (Manual)

Configure OAuth 2.0 manually for providers not in our pre-built list:

API Key

Simple key-based authentication with flexible placement options:

Example Configuration:

{
  "type": "api_key",
  "name": "Stripe API",
  "config": {
    "api_key": "sk_live_...",
    "key_name": "Authorization",
    "location": "header",
    "prefix": "Bearer "  // Optional prefix
  }
}

Bearer Token

Token-based authentication commonly used with JWTs:

Example Configuration:

{
  "type": "bearer_token",
  "name": "Internal Service Auth",
  "config": {
    "token": "eyJhbGciOiJIUzI1NiIs...",
    "header_name": "Authorization",
    "prefix": "Bearer "
  }
}

Basic Auth

Username and password authentication (Base64 encoded):

Choosing the Right Auth Type

Use this guide to select the appropriate authentication type for your integration:

Managing Auth Configs

Viewing Auth Configs

All your auth configs are displayed in the Auth Configs section with:

• Name: Your custom name for the config
• Type: OAuth2 Provider, Native Connector, or Custom
• Provider/Connector: The specific provider or connector
• Status: Active, Expired, or Error
• Last Used: When the config was last used
• Connections: Number of connected apps using this config

Editing Auth Configs

You can update auth configs at any time:

1. Click on the auth config to open details
2. Click Edit to modify settings
3. Update credentials or configuration
4. Test the updated configuration
5. Save changes

Refreshing Credentials

For OAuth2 configs, you may need to re-authorize if:

• Tokens have expired and cannot be refreshed
• Permissions have been revoked
• Scopes need to be updated

Click Re-authorize to initiate a new OAuth flow.

Deleting Auth Configs

Before deleting an auth config:

1. Check that no connected apps are using it
2. Remove or reassign any dependent connections
3. Click Delete and confirm

Security Features

Encryption

All credentials are encrypted using industry-standard encryption:

• At Rest: AES-256 encryption for stored credentials
• In Transit: TLS 1.3 for all network communication
• Key Management: Regular key rotation and secure key storage

Access Control

Control who can view and manage auth configs:

Audit Logging

All auth config operations are logged:

• Creation and deletion events
• Credential updates
• Authorization flows
• Access attempts
• Token refresh events

Best Practices

Troubleshooting

Common Issues

Testing Connections

Use the built-in test feature to diagnose issues:

1. Open the auth config
2. Click Test Connection
3. Review the test results
4. Check error messages for specific issues
5. Update configuration and test again

Next Steps

Summary

Auth Configs is your central hub for managing all authentication across FlowGenX:

• OAuth2 Provider: Connect with popular OAuth2 services like Google, Microsoft, and Salesforce, or configure custom OAuth2 providers
• Native Connector: Use pre-built authentication forms for 100+ databases, message brokers, file storage systems, and enterprise applications
• Custom: Create flexible authentication configurations for APIs with API keys, bearer tokens, basic auth, or no authentication

With enterprise-grade security features including encryption, access control, and audit logging, Auth Configs ensures your credentials are managed securely while providing the flexibility to connect to any service your workflows need.