VIP auth hub Adminconsole login hangs after upgraded from v.3.3.1 to v.3.4.4

Products

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

Issue/Introduction

After upgraded VIP auth hub from v.3.3.1 to v.3.4.4, Adminconsole login hangs.

Azserver log shows error like below:

{"timestamp":"yyyy-mm-ddT15:48:49.395694Z","type":"log","level":"warn","thread":"##########","msg":"SessionService.getSession: Failed to locate Session with sid: .......}

{"timestamp":"yyyy-mm-ddT15:48:49.989557Z","type":"log","level":"warn","thread":"##########","msg":"populateSystemContextForPolicyEvaluation: Unable to obtain 'sessionStartTimeMillisjwtservice' from thread context's value 'null'. Error: Cannot parse null string","api":.....}

 

Environment

VIP auth hub: 3.3.1 to 3.4.4

Resolution

If manual updates of the vip auth hub database schema are required, make sure "helm upgrade" has the following flag set. 

Missing them will cause updated database schema not being picked up during deployment.

--set ssp.featureFlags.dataseed.skipSchemaInit='true' \
--set ssp.featureFlags.dataseed.enabled='true' \

Additional Information

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/vip-authentication-hub/3-4/Installing/upgrading-services.html