IntegrationAdvancedoauthconnected-appsecurity
Implement OAuth connected app patterns for secure integrations
Real World Scenario
Integration users with System Administrator profiles were used for MuleSoft connections until security audit flagged excessive privileges.
Expected Answer
• Dedicated integration user with minimum permission set—never Sys Admin
• JWT bearer flow for headless server integrations without refresh token storage
• Web server flow only where user delegation genuinely required
• IP restrictions and certificate-based connected app policies
• Separate connected apps per integration for credential rotation isolation
• Token lifetime and refresh policies aligned to security standards
• Regular access review disabling unused connected apps
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Dedicated integration user with minimum permission set—never Sys Admin. JWT bearer flow for headless server integrations without refresh token storage. Pick based on your integration pattern and team capability. Integration user sprawl with admin rights is breach waiting—architects enforce least privilege per connected app. Optimize for scale and operational observability.
Architect Perspective
Integration user sprawl with admin rights is breach waiting—architects enforce least privilege per connected app.