Client registration failure in Platform UI console

This version of documentation is no longer updated. For the latest information, see the following links:
- Continuous Delivery (CD) documentation
- Support Cycle-2 (SC-2) documentation

Client registration fails in Platform UI console When you upgrade the foundational services version 3.22 or version 3.23 to foundational services version 4.x.x.

Symptoms

You might fail to register the client in Platform UI console in the following scenarios:

• When you upgrade the foundational services version 3.22 or version 3.23 to foundational services version 4.x.x and migrate more than one LDAP.

• When you have more than one LDAP before upgrading foundational services version 3.22 or version 3.23 to foundational services version 4.x.x.

Workaround

• Check the platform-auth-service pod configuration. You might see that some files have wrong entries. To check the pod configuration, run the following command:

    for i in $(oc get pod -l app.kubernetes.io/instance=platform-auth-service --no-headers|awk '{print $1}');do oc exec -it $i -- ls /config/configDropins/defaults/;done
  

  The sample output:

    Defaulted container "platform-auth-service" out of: platform-auth-service, init-mongodb (init)
    federated.xml  keystore.xml  ldap-cp4ba-prod-default-4776.xml
  

• Restart platform-auth-service pods.

    oc delete pod $(oc get pod -l name=platform-auth-service --no-headers|awk '{print $1}')
  

  Once the pod is deleted, wait for some time and then restart the platform-auth-service pods.

• Then, restart platform-identity-provider pods.

    oc delete pod $(oc get pod -l name=platform-identity-provider --no-headers|awk '{print $1}')
  

Once the pod is deleted, wait for some time and then restart the platform-identity-provider pods.