← Back to Portfolio
MuleSoft Security Model
A comprehensive security architecture demonstrating OAuth2 Client Credentials flow, JWT enforcement at the API Gateway, and Role-Based Access Control (RBAC) linking Anypoint platform users to granular permissions.
flowchart TD
Client[Client Application] -->|1. Request Token| AuthZ[OAuth2 Authorization Server]
AuthZ -->|2. Issue JWT| Client
Client -->|3. API Request + JWT| Gateway[MuleSoft API Gateway]
Gateway -->|4. Validate Token Signature| AuthZ
Gateway -->|5. Apply Security Policies| Policy[API Manager Policies]
Policy -->|6. Forward Request| Backend[(Backend API / Microservice)]
subgraph RBAC[Anypoint Role-Based Access Control]
User[Platform User] -->|Assigned To| Role[Custom Role]
Role -->|Contains| Perm1[API Owner Permission]
Role -->|Contains| Perm2[Env Admin Permission]
end
classDef default fill:#fff,stroke:#cbd5e1,stroke-width:1px,color:#1e293b;
classDef auth fill:#eff6ff,stroke:#3b82f6,stroke-width:2px,color:#1d4ed8;
classDef gw fill:#f0fdf4,stroke:#22c55e,stroke-width:2px,color:#15803d;
classDef rbac fill:#fef2f2,stroke:#ef4444,stroke-width:2px,color:#b91c1c;
class AuthZ auth;
class Gateway gw;
class RBAC rbac;