Secure Shibboleth Integration in AKS Migration: Preserving Authentication Workflows and Network Security

Introduction The migration of applications from virtual machines (VMs) to Kubernetes, particularly Azure Kubernetes Service (AKS), represents a strategic shift toward achieving scalability, resource optimization, and cloud-native capabilities. However, this transition introduces significant challenges when integrating legacy authentication systems such as Shibboleth . The primary objective is to preserve existing authentication workflows while ensuring network security and operational efficiency within the Kubernetes ecosystem. Failure to address these challenges can result in unauthorized access, disrupted user workflows, and increased operational overhead, potentially undermining the benefits of migration. The Shibboleth-Kubernetes Integration Challenge In the source scenario, the existing architecture comprises a Shibboleth Service Provider (SP) and Apache running on a VM. Apache facilitates authentication via Shibboleth, appending user identity headers to requests forwarded to the