An organization is migrating its enterprise authentication framework to a modern cloud Identity Provider (IdP) supporting OpenID Connect (OIDC). However, several legacy internal web applications only support HTTP header-based authentication and cannot natively process OIDC tokens. Which of the following architectural components should be deployed between the legacy applications and the cloud IdP to translate federated identity assertions into secure local application headers?
- An Identity-Aware Proxy (IAP) acting as a reverse proxy to authenticate requests via the cloud IdP and inject validated identity headers to the target applicationsAnswer
- BA RADIUS server configured to convert OIDC tokens into AAA access requests for web application header injection
- CAn internal perimeter firewall enforcing IP-based Access Control Lists (ACLs) to implicitly trust incoming web session headers
- DAn OAuth 2.0 authorization server that re-writes HTTP header attributes during authorization code grant exchanges
Answer
An Identity-Aware Proxy (IAP) acting as a reverse proxy to authenticate requests via the cloud IdP and inject validated identity headers to the target applications
An Identity-Aware Proxy (IAP) acts as an intermediary reverse proxy. It intercepts user web traffic, redirects unauthenticated requests to the cloud IdP for OIDC authentication, and upon successful authentication, attaches verified identity attributes as secure HTTP headers before forwarding requests to legacy target applications.
Step-by-Step Solution
Key Concept
Identity-Aware Proxy (IAP) and legacy application integration in IAM architecture