baic_dashboard/.env.example
michael 117a68a223 Configure MSAL redirect URI explicitly via environment variables
Added VITE_REDIRECT_URI and VITE_REDIRECT_URI_DEV environment variables to provide explicit control over Azure AD redirect URIs. Updated authConfig.js to use these variables with automatic environment detection (development vs production).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-18 09:27:13 -06:00

35 lines
1.2 KiB
Text

# Domain Configuration
# The domain where your application will be deployed (without protocol)
DOMAIN=yourdomain.com
# The base path for the application (must start and end with /)
BASE_PATH=/dashboard/
# Azure AD Configuration
# Get these values from your Azure AD app registration
# Portal: https://portal.azure.com > Azure Active Directory > App registrations
AZURE_TENANT_ID=your-tenant-id-here
AZURE_CLIENT_ID=your-client-id-here
# Backend Configuration
# Port on which the backend server will run
BACKEND_PORT=5001
# Make.com Webhook
# The webhook URL that provides your data
MAKE_WEBHOOK_URL=https://hook.eu1.make.celonis.com/your-webhook-id
# Frontend Build Configuration (used by Vite)
# These VITE_ prefixed variables are embedded at build time
# They should match the values above
VITE_DOMAIN=yourdomain.com
VITE_BASE_PATH=/dashboard/
VITE_BACKEND_PORT=5001
VITE_AZURE_TENANT_ID=your-tenant-id-here
VITE_AZURE_CLIENT_ID=your-client-id-here
# Azure AD Redirect URIs
# Production redirect URI - must match what's registered in Azure AD
VITE_REDIRECT_URI=https://yourdomain.com/dashboard/
# Development redirect URI (used when running locally)
VITE_REDIRECT_URI_DEV=http://localhost:5173