Accessing vIDM (VMware Identity Manager configurator page 8443 page) throws error "Failed to set admin password: No content to map due to end-of-input"

Products

• VMware Aria Suite

Issue/Introduction

When trying to access the vIDM (VMware Identity Manager configurator page on port 8443), an error message appears: "Failed to set admin password: No content to map due to end-of-input."

Attempting to set the admin password via CLI results in the same error.

     root@xx-xx-xx [ ~ ]# /usr/sbin/hznAdminTool setSystemAdminPassword
     Password:
     Last login: Mon Dec  2 09:10:18 UTC 2024 on ???
     Failed to set admin password: No content to map due to end-of-input
     at [Source: (File); line: 1, column: 0]

Environment

VMware Identity Manager 3.3.7

Cause

The vIDM configuration relies on the system.config-properties file. Any corruption or missing entries in this file can cause anomalies. Specifically, the referenced error message indicated that the values "clientId=Configurator__OAuthClient and application.initialized=true" were missing from the system.config-properties file.

Resolution

• Verify the configuration in the system-config.properties file located at /usr/local/horizon/conf/ and ensure that the following entries are present: clientId=Configurator__OAuthClient and application.initialized=true.
  
  
• If we do not see those, please go ahead and add them manually on the vIDM nodes which has issues on loading the https://<vIDM-FQDN>:8443/cfg/ page
  
  Example:
  root@vidmxx [ /usr/local/horizon/conf ]# cat system-config.properties
#Fri Jan 03 07:47:40 UTC 2025
clientId=Configurator__OAuthClient
suiteToken=aaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbjbxxxxxxxxxxxxxxxxxbbbbbbbbbbbbbbbbbcccccccccccccccccmmmmmmmmmmm4gdXNlciBlbWFpbCIsImlkcCI6IjIiLCJlbWwiOiJjb25maWdhZG1pbkBnc2xhYnMubG9jYWwiLCJjaWQiOiIiLCJkaWQiOiIiLCJ3aWQiOiIiLCJydWxlcyI6eyJleHBpcnkiOjE3MzU4OTA3NzUsInJ1bGVzIjpbeyJyZXNvdXJjZXMiOlsiKiJdLCJhY3Rpb25zIjpbImFjczpyZWFkUnVsZVNldHMiLCJkbTpyZWFkIiwidWc6cmVhZCIsImVudDpyZWFkIiwiY3RnOnJlYWQiLCJ0bnRzOnJlYWQiLCJycHQ6KiJdLCJjb25kaXRpb25zIjpudWxsfSx7InJlc291cmNlcyI6WyIqIl0sImFjdGlvbnMiOlsiKiJdLzzzzzzzzzzzzzzzzzzxxxxxxxxxxxxxxxfffffffffffffggggggggggggggggggggggggggxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxjoiMWQyMjE0NGEtN2YyYi00ZGZmLxxxxxxvvvvvvvvvvvvvvvvvxxxxxxxxxxxxxxxxRmes8xdddddddddddddddddddL10Yq8_cZtAcaeUQ_-xxxxxxxxxxxxxxxxxxssssssssssssssssssssssssssssdddddddddddddddddddddddddddde9P8b7QjBFVbjWTgANzuR632VGv3fQhUR-4_zxmCT2rqq_EiTR6N6PJg9A8M1Ite0YdruEbwWKIr4ef0OfCH6Lx0aAPiUbAnFoizPjQ2CbVfIAQX-057uTOtelr80Ww3EyZbQLSQuBvjM2a_j_f0raiBshfbphkgH3HUFr6um8LBPbQ5UuPxpeJ9fQwKHbeA
secure.clientSecret=aaaaaaaaaaaaazzzzzzzzzzzzzzbbbbbbbbbbbbbbbbbbhhhhhhhhhhhhhhhhu4pqGT9DQ\=\=
tenant.id=vidm01
application.initialized=true
root@vidm01 [ /usr/local/horizon/conf ]#

Additional Information

In case you continue to get the same error message even after following the above steps.

Validate the configuration in config-admin.json, idm-cacerts and system-config.properties files located in /usr/local/horizon/conf/ as per KB