Move enforcer functionalities to Envoy filters

[Tharsanan1]

Description

The current APK architecture employs a Java-based Enforcer for enforcing security, handling analytics, and managing tracing functionalities. However, Java's memory-intensive nature increases deployment costs and limits scalability. This high memory consumption makes APK less marketable to customers who seek lightweight and cost-effective solutions for API gateway needs.’
The following sub tasks are needed to be completed to start the removing functionalities from enforcer and moving to envoy filters.

• Competitor analysis on how they achieve features supported in enforcer
• POC on golang filter to test External http calls, External Redis calls
• Finalize the solution on how we are going to implement each filters in envoy

The following features needs to be implemented in envoy filters and removed from enforcer

• XDS client - Spin up XDS client in go-enforcer to get API, JWT Issuer and configs from adapter #2668
• JWT
• Oauth2
• MTLS
• APIKey
• Token revocation
• Token caching
• Subscription Validation
• Scope validation
• Backend JWT
• Backend JWKS
• CORS
• Subscription ratelimit
• AI Backend based Ratelimit
• AI Subscription based Ratelimit
• Analytics
• Graphql
• APIDefinition

Affected Component

None

Version

No response

Related Issues

No response

Suggested Labels

No response