Logging in to vCenter errors out with : "An error occurred while fetching identity providers"
search cancel

Logging in to vCenter errors out with : "An error occurred while fetching identity providers"

book

Article ID: 425884

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Comprehensive checks confirm that all vCenter certificates are valid and not expired.
  • Logging into Vcenter shows error  "An error occurred while fetching identity providers"
  • As per logs the entries look similar to:

     /var/log/vmware/trustmanagement/trustmanagement-svcs.log


    2026-01-19T08:35:00.514Z [inventoryPermissionConverterScheduler-1 [] ERROR com.vmware.vcenter.trustmanagement.migration.InventoryPermissionConverter  opId=] VPXD AuthZ inventory permission conversion failed
    com.vmware.vim.sso.client.exception.ServerCommunicationException: Error communicating to the remote server http://localhost:1080/sts/system-STSService
            at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:996) ~[wstClient.jar:?]
            at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:902) ~[wstClient.jar:?]
            at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:509) ~[wstClient.jar:?]
            at com.vmware.vcenter.trustmanagement.vapi.impl.setup.ServiceUtil.getHokToken(ServiceUtil.java:247) ~[libservice.jar:?]
            at com.vmware.vcenter.trustmanagement.vapi.impl.setup.ServiceUtil.getAuthenticatedSsoAdminClient(ServiceUtil.java:233) ~[libservice.jar:?]
            at com.vmware.vcenter.trustmanagement.migration.InventoryPermissionConverter.getCurrentSsoDomains(InventoryPermissionConverter.java:120) ~[libservice.jar:?]
            at com.vmware.vcenter.trustmanagement.migration.InventoryPermissionConverter.convertAliasPermissions(InventoryPermissionConverter.java:91) [libservice.jar:?]
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_422]
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_422]
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_422]
            at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_422]
            at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84) [spring-context-5.3.42.jar:5.3.42]
            at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-5.3.42.jar:5.3.42]
            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_422]
            at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_422]
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_422]
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_422]
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_422]
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_422]
            at java.lang.Thread.run(Thread.java:750) [?:1.8.0_422]
    Caused by: com.vmware.vim.sso.client.exception.ServerCommunicationException: Error communicating to the remote server http://localhost:1080/sts/system-STSService
            at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:226) ~[wstClient.jar:?]
            at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:120) ~[wstClient.jar:?]
            at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:983) ~[wstClient.jar:?]
            ... 19 more
    Caused by: com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 503: Service Unavailable
            at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:310) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:259) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:217) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:250) ~[?:1.8.0_422]
            at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289) ~[?:1.8.0_422]
            at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:198) ~[wstClient.jar:?]
            at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:120) ~[wstClient.jar:?]
            at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:983) ~[wstClient.jar:?]
            ... 19 more

Environment

VMware vCenter Server 8.x

Cause

 

The vmware-sts-idmd or vmware-stsd service has entered an unhealthy state and is no longer responding to requests on its internal socket.

 

Resolution

Restarting all services on Vcenter resolves the issue:


service-control --stop --all && --start --all

Powered by Wolken Software