Troubleshooting
Problem
Symptom
If you check any one of the Assist studio/technician/admin-console pod logs that are in Assist name space mas-{{instanceId}-assist, for example for the {{instanceId}}-ema-studio pods, the following types of errors exist:
UnhandledPromiseRejectionWarning: JwksError:
Unknown authentication strategy "jwtStrategy"
Cause
The pods restart for Assist components and the pods connect to the MAS coreidp service to get the jwks keys, but a networking intermittent issue occurs and the unhandled promise exception is not caught and causes the following error: Unknown authentication strategy “jwtStrategy”
Getting the jwks key during the pod startup involves a one-time connection. After the pod gets the jwks key and then start, it will not connect to coreidp again to get the jwks key.
Resolving The Problem
Log in to the Red Hat OpenShift Container Platform cluster and run the following command to reboot the related (studio,technician,admin-console) pods in Assist namespace (project).
oc get pods -n mas-{{instanceId}-assist | grep -Ei ‘studio|technician|admin-console’ |awk ‘{print $1}’ |xargs oc -n mas-{{instanceId}-assist delete pods
After those pods are restarted, you can log in to Assist. You can check the pods status is running the following command:
oc get pods -n mas-{{instanceId}-assist | grep -Ei ‘studio|technician|admin-console’
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
20 July 2022
UID
ibm16605273