Slow Response and 503 Errors Loading Authentication Hub Swagger

Products

• Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

When attempting to load the Authentication Hub/IDSP API Swagger interface on versions 3.4.4 or 4.0.0, the response time is significantly delayed, sometimes exceeding 45 seconds. This often leads to HTTP 503 Service Unavailable errors when the service is positioned behind a proxy with shorter timeout configurations.

Environment

• Product: Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)
• Versions: 3.4.4, 4.0.0

Cause

The Swagger container may experience resource exhaustion or an "Out of Memory" (OOM) exception while generating the API documentation. Insufficient CPU or RAM allocation at the cluster level can also contribute to the generation latency.

Resolution

1. Check Logs: Review the Swagger pod logs for explicit java.lang.OutOfMemoryError messages.
2. Verify Cluster Sizing: Ensure the environment meets the minimum requirements for its deployment size.
3. Temporary Workaround: A rollout restart of the Swagger container can clear the memory state and temporarily allow the interface to load, though load times may still be near the 20-second mark Authentication Hub Swagger slow response.
4. Upcoming Fix: A permanent optimization for Swagger response performance is scheduled for the Authentication Hub 4.0.2 release, tentatively expected in April 2026.