There are problems around the UMC and also around the IC in 23.4 and 24.4. Paths are not correct and there are errors in configuration files about ports, paths to cert files and more. I am currently writing up the issue and want to open a call.  This week I am unfortunately fully occupied with work. Hopefully I can deliver a workaround on Friday evening.

/oes-rest/api/v1/management-services is part of oes-rest service(microfocus-umc-backend.service) make sure that this service is enable and running 

Also related to - ps aux | grep edirapi

We have called out that edirapi is deployed as docker container so the conf file will be available in the docker container

The edirapi process you’re seeing with ps aux is the containerized process

How to Verify Containerized Processes:

To confirm that edirapi is running in a container:

    Use docker top <container_id_or_name> to see the processes running inside the container.
    Cross-check the PID shown in docker top with the one listed in your ps aux command.

    From OES24.4 - 

    # ps aux | grep edirapi
      35753     4117  0.0  0.3 1762176 37012 ?       Ssl  Nov11   0:02 /opt/novell/eDirAPI/sbin/edirapi -config /etc/opt/novell/eDirAPI/conf/edirapi.conf

    # docker top identityconsole-oes
      UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
      35753               4117                4094                0                   Nov11               ?                   00:00:02            /opt/novell/eDirAPI/sbin/edirapi -config /etc/opt/novell/eDirAPI/conf/edirapi.conf

    Here the PID are same this verify that this is Containerized Process

We can check the file is present in container or not -

# docker exec -it identityconsole-oes sh
sh-5.1$ ls /etc/opt/novell/eDirAPI/conf/edirapi.conf
/etc/opt/novell/eDirAPI/conf/edirapi.conf

That is confusing ...

maybe you want to check how GWWEB does its configuration. There is a link to the (main) file system to store the config files, log, et.al.

Can this (let the config in the container) be the reason too, that there are no logrotate config for the redis.log?

host2:/etc/logrotate.d # l /var/opt/novell/log/umc/redis/notice.log
-rw-rw---- 1 root redis 8168342396 12. Nov 09:35 /var/opt/novell/log/umc/redis/notice.log

WTF ... 9GB ?

1573:M 12 Nov 2024 09:36:15.420 # Error accepting a client connection: error:1417C086:SSL routines:tls_process_client_certificate:certificate verify failed

There are millions of such lines ...

And as addon ... they have found that the UMC is not the worthy replacement for iManager ... now we need identityconsole, too .... OMG it is frustrating ....

BTW: OES (this means Open Enterprise SERVICES!!!) is a distributed environment for needed basic services file, print, etc. And so you need a distributed administration environment! You have SLP, NCP and eDir. You should ground the services on this! It is not necessary to develop a new base with the same features. (eDir is a distrubuted partitionized database. It is perfect for such littel dataparts as config for a AdminUI ... It is not useful to create a new db env. which has to be replicated etc.)

Check the existing concepts and develop this way.

</rant>

Sorry, but sometimes I am frustrated ... now I go back and lay under my desk ... ;-)