SOP: Make compliance publically available in any env

Owned by Chandra Keshav Mishra, created
Last updated: Jun 01, 2023 by Swati (Unlicensed)
1 min read

How to make CTK publically available?

 

Pre-req

Ensure that all the deployment steps are followed as given here

(mosip/mosip-compliance-toolkit (github.com).

add Ui readme link

 Instructions to be followed in your deployment environment

DNS Mapping Changes:

  1. onboarder.collab.mosip.net ----> public ip of nginx server

  2. collab.mosip.net ----> public ip of nginx server

  3. pmp.collab.mosip.net ----> public ip of nginx server

  4. iam.collab.mosip.net ----> public ip of nginx server

Nginx Server changes:

Add below mentioned domains in server_name section of pubic nginx server.

  1. yourdomain.mosip.net

  2. api.yourdomain.mosip.net

  3. compliance.yourdomain.mosip.net

  4. pmp.yourdomain.mosip.net

  • Note: replace “yourdomain” appropriately.

Istio changes

  1. update the gateways for below mentioned modules to point to public:

    1. pmp

    2. compliance

    3. iam

    4. landing

  2. Update the following virtual service to point to public ip:

    1. partnermanager

    2. policymanager

    3. toolkit-service

  3. Update istio gateway in compliance toolkit envoyFilter compliance-toolkit-set-cookie-header to public gateway.

    workloadSelector: labels: istio: ingressgateway

Config map changes for UI part

  1. Update compliance-toolkit-ui.json to point to api.collab.mosip.net instead of api-internal.collab.mosip.net.

  2. Update pmp config.json to point to api.collab.mosip.net instead of api-internal.collab.mosip.net.

Configuration changes for pmp ui and compliance UI: