DevTest Portal Frequent Session Logouts

Products

• Service Virtualization

Issue/Introduction

Users of the DevTest Portal running in an K8s environment experience frequent, unexpected logouts. This may manifest as:

• A "Session Expired" dialog appearing while the user is actively working.
• A "Lost connection to Registry" dialog appearing in the UI.
• Users being kicked back to the login screen after a short period of inactivity (e.g., 2–20 minutes), despite higher timeout settings in IAM/Keycloak.

Environment

• Product: Broadcom Service Virtualization (DevTest)
• Versions: 10.8.4.1 and earlier 10.8.4 service packs
• Deployment: Docker / AWS / Kubernetes

Cause

This issue was identified as a product defect. The Portal UI incorrectly triggered a session timeout or connection-loss dialog if the Registry became momentarily non-responsive or if certain authentication handling errors occurred.

Resolution

This issue is resolved in the DevTest 10.8.4.2 service pack images. The update includes improved logging for authentication failures and changed UI behavior to prevent premature session timeouts when the registry is busy.

Steps to Apply the Fix

1. Generate Registry Token:

   • Log in to the Broadcom Support Portal.
   • Navigate to the "My Downloads" page.
   • Generate a new Registry Token for Docker authentication.

2. Authenticate Docker:

   • Run the following command using your support credentials and the generated token:
     bash

      

     docker login sv-docker.packages.broadcom.com -u [Your-Email] -p [Your-Token]

3. Pull Updated Images:

   • Update your deployment to pull the 10.8.4.2 tags for the following components:
     bash

      

     docker pull sv-docker.packages.broadcom.com/sv/portal:10.8.4.2docker pull sv-docker.packages.broadcom.com/sv/lisa:10.8.4.2docker pull sv-docker.packages.broadcom.com/sv/config-server:10.8.4.2docker pull sv-docker.packages.broadcom.com/sv/enterprise-dashboard:10.8.4.2

   Note: The iaam and vscatalog images do not have mandatory changes for this fix and may remain on version 10.8.4.1.

4. Redeploy:

   • Restart your containers/pods using the new image versions.

Additional Troubleshooting

If logouts persist after the upgrade, verify the following in your IAM (Keycloak) Realm Settings:

• SSO Session Idle: Ensure this is set to your desired timeout (e.g., 8–12 hours).
• Access Token Lifespan: Verify this is not set to an extremely short interval.