Using LDAP registry on Mobile Foundation deployed on IBM Cloud Private (ICP)

When Mobile Foundation (MFP) Server Helm chart is deployed on IBM Cloud Private it uses basicRegistry along with various other configuration details. This user registry is good enough for basic development and testing environments, but for production scenarios LDAP registry is used.

This blog focuses on how to use Apache Directory Server as an LDAP registry against the Mobile Foundation server that is deployed on IBM Cloud Private (or IBM Cloud Kubernetes Service, IKS).

This blog post focuses on how to use the Apache Directory Server as an LDAP Registry with Mobile Foundation Server on ICP and assumes the following:

a) User has an MFP setup on IBM Cloud Private loaded with IBM Mobile Foundation Passport Advantage Archive on ICP.

b) User has the knowledge of LDAP Registry.


  1. [Optional] Make sure the configured LDAP Registry works with MFP devkit and the MFP console is accessible to the ldap users instead of basic users that comes Out-of-box.
  2. From the Apache Directory Studio, make sure that the LDAP is configured correctly. For instance this article uses the following ldap setting.

    Test Apps Script

  3. Create registry.xml as follows

     [root@masternode1 ~]# mkdir -p usr-mfpf-server/config
     [root@masternode1 ~]# cd usr-mfpf-server/config

    This creates the following directory structure that can be used to customize the image on the ICP for modifying the registry.xml

     ├── config
     │   └── registry.xml
  4. Create a Dockerfile to overwrite jvm.options as follows

     FROM mycluster.icp:8500/default/mfpf-server:
     COPY jvm.options /opt/ibm/wlp/usr/servers/config/registry.xml
  5. Create a file registry.xml with LDAP registry configuration as follows:

     <?xml version="1.0" encoding="UTF-8"?>
     <ldapRegistry id="ldap" host="yathendra.local" port="10389" ignoreCase="true" baseDN="dc=ibm,dc=com" ldapType="Custom" recursiveSearch="true" sslEnabled="false" bindDN="uid=admin,ou=system" bindPassword="secret">
     <customFilters userFilter="(&amp;(uid=%v)(objectclass=inetOrgPerson))" groupFilter="(&amp;(member=uid=%v (objectclass=groupOfNames))" userIdMap="*:uid" groupIdMap="*:cn" groupMemberIdMap="ibm-allGroups:member;ibm-allGroups:uniqueMember;groupOfUniqueNames:uniqueMember;groupOfNames:member"/>
      <group name="mfpadmingroup">
      	<member name="adminuser"/>
      <group name="mfpconfiggroup">
      	 <member name="configUser_mfpadmin"/>
      <member name="MfpRESTUser"/>
      <member name="Push_MFPLDAPPOC"/>
      <member name="Admin_MFPLDAPPOC"/>

    Note: Make sure the right user and group details are used according to your own LDAP server settings.

  6. Build docker image with a new tag name (say

     # docker build . -t mfpf-server:

    This updates the existing mfp-server docker image with the customized registry.xml.

  7. Log in to the ICP cluster and docker registry via commandline:

    # bx pr login -a https://<icp_cluster_ip>:8443 --skip-ssl-validation -u admin -p xxxx -c <mycluster-account>
    # docker login mycluster.icp:8500 -u admin -p xxxx
  8. Push the new image to the ICP container repository as follows:

    # docker tag mfpf-server: mycluster.icp:8500/default/mfpf-server:
    # docker push mycluster.icp:8500/default/mfpf-server:
  9. Check the available Mobile Foundation Server deployment on Kubernetes as follows:

     kubectl get deployments
     NAME                                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
     mfpserver-ibm-mfpf-server-prod         2         2         2            2           5d
  10. Now update Mobile Foundation Server kubernetes deployment mfpserver-ibm-mfpf-server-prod to use the customized image.

    kubectl edit deployments mfpserver-ibm-mfpf-server-prod
  11. Replace - image: mycluster.icp:8500/default/mfpf-server: with - image: mycluster.icp:8500/default/mfpf-server:

  12. Once the image is updated in the kube configuration, the mfp server pods are deleted and recreated automatically using the new configuration. Make sure that all the pods are running and ready using the command below:

    kubectl get pods
  13. Log in to the ICP Console with one of the configured LDAP user (here adminuser) and make sure the login is successful and all the services are up and running from the Mobile First Server Operations Console.

The above set of instructions are applicable for using any other LDAP servers like IBM Directory Server, Microsoft Active Directory Server etc.

For more details on Configuring LDAP user registries in Liberty, refer to the documentation

Last modified on November 04, 2018