Ensure that all the deployment steps are followed as mentioned in the README.md files of the below repositories:
Below are details of some additional steps that you may need to follow so as to make CTK publicly available post the regular deployment.
Update the DNS records for the below mentioned domains to point to the public IP of nginx server associated with the corresponding cluster.
onboarder.sandbox.mosip.net ----> public IP of nginx server for Mosip cluster
sandbox.mosip.net ----> public IP of nginx server for Mosip cluster
pmp.sandbox.mosip.net ----> public IP of nginx server for Mosip cluster
iam.sandbox.mosip.net ----> public IP of nginx server for Observation cluster
Add the below mentioned domains in server_name
section of pubic nginx server.
sandbox.mosip.net
api.sandbox.mosip.net
compliance.sandbox.mosip.net
pmp.sandbox.mosip.net
Note: Replace “sandbox” appropriately.
Update the below mentioned istio ingress gateway to point to public IstioOperator:
Change spec.selector.istio: ingressgateway-internal to spec.selector.istio: ingressgateway as shown in the image below.
pmp-gateaway
compliance-toolkit-ui-gateway
keycloak
landing-page
Update below mentioned Istio virtualservice to add public gateway in spec.gateways:
3. Update Istio gateway in compliance toolkit EnvoyFilter compliance-toolkit-set-cookie-header to public gateway.
Update compliance-toolkit-ui.json to point
to api.sandbox.mosip.net
instead of api-internal.sandbox.mosip.net
.
Update pmp config.json
to point to api.sandbox.mosip.net
instead of api-internal.sandbox.mosip.net
.
Add mosip.api.external.url=https://${mosip.api.public.host}
property in compliance-toolkit-default.properties
file.
Update mosip.iam.module.redirecturi=${mosip.api.external.url}/v1/toolkit/login-redirect/
property in compliance-toolkit-default.properties
file.
Update mosip.iam.module.redirecturi=${mosip.api.external.url}/v1/partnermanager/login-redirect/
property in partner-management-default.properties
file.