Release : 4.2
Component : API PORTAL
You can update config to new host name. You can change portal host name by modifying /opt/apim-portal-4.2.9.1-final/config.sh; however, it is not possible to change the tenant id.
All ephemeral containers will switch to new host within a stack. There are few entries in the database however, that we use for cors as well as redirect to papi.
Are you running MySQL or postgres?
For gateway enrollment, this is also optional step, all the sync routes are in the cluster-wide properties, you just have to make sure marching outbound SSL cert Is imported after pointing it to new host.
Setting up proxy for url rewrite and ssl termination in front of the on-prem portal to mimic our custom domain feature in saas.
We can provide sample entry for ngnix on what needs to be changed in the rewrite rule. This is probably the best approach tried and tested in the field.
Here is a sample entry for ngnix in the rewrite rule?
server {
listen 8443 ssl;
server_name {{ (env "DOMAIN") }};
server_tokens off;
ssl_certificate /etc/nginx/conf.d/{{ (env "DOMAIN") }}.crt;
ssl_certificate_key /etc/nginx/conf.d/{{ (env "DOMAIN") }}.key;
set $my_host {{ (env "TENANT_URL") }};
# Include real_ip block
include /etc/nginx/real_ip.conf;
# Proxy Headers
proxy_set_header HOST $my_host;
proxy_set_header ORIGIN $scheme://$my_host;
proxy_set_header REFERER $scheme://$my_host;
include /etc/nginx/proxy_headers.conf;
location / {
proxy_pass https://127.0.0.1:8443$request_uri;
proxy_redirect $scheme://$my_host/ $scheme://$http_host/;
}
}