Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

For enabling public access to Compliance follow the instructions.

\uD83D\uDCD8 Instructions

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. collab.mosip.net

  2. api.collab.mosip.net

  3. compliance.collab.mosip.net

  4. pmp.collab.mosip.net

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:

  • No labels