This document is under revision.
Summary
Error
Probe server get errors: Failed to get credential for id 14_1_CMS - Could not fetch credential with id 14_1_CMS from Confidential Manager Client
There are the errors in Security.cm.log:
2021-05-18 16:27:26,325 INFO [pool-3-thread-1] - Exception while trying to read authorized folders names from cm server with the following message: Problem getting authorized folders
2021-05-18 16:27:26,325 DEBUG [pool-3-thread-1] - Exception:
globalStatus = NO_STATUS
at com.hp.sw.bto.ast.security.cm.api.CMRestClientAPIsImpl.getAuthorizedFolderNames(CMRestClientAPIsImpl.java:807)
at com.hp.sw.bto.ast.security.cm.api.CMClientCacheProxy.updateCache(CMClientCacheProxy.java:300)
at com.hp.sw.bto.ast.security.cm.api.CMClientCacheProxy$CacheUpdateThread.run(CMClientCacheProxy.java:276)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Fix
This is a common issue for all the OBM 2020.10 release, need to fix it by changing the ucmdb pod algorithm to SHA1.
Please follow the steps to change the setting back to SHA1 before install a probe.
Command:
Kubectl edit deployment [itom-ucmdb-server-123] -n [namespace]
And then change MAM_SERVER_SSO_MAC_ALGORITHM_NAME and MAM_SERVER_SSO_PBE_DIGEST_ALGORITHM to SHA1
After save it, the pod is automatically recreated.