After upgrading portal to 5.1.2 the tenant with a different subdomain as the one specified in portal.conf does not work
search cancel

After upgrading portal to 5.1.2 the tenant with a different subdomain as the one specified in portal.conf does not work

book

Article ID: 269857

calendar_today

Updated On:

Products

CA API Developer Portal

Issue/Introduction

After upgrading portal to 5.1.2 the tenant with a different subdomain as domain specified in  the portal.conf does not work 

We upgraded from 4.5  after the upgrade to 5.1.2 the tenant is not reachable  anymore , the other tenant with tenant.portaldomain works as expected.

 

Environment

Release : 5.1.2

Cause

In portal 5.1.2 the nginx is restricted to only allow access for tenants with the portal domain name only

Resolution

You can set CONFIG_HOST_ALLOWED_DOMAINS="tenant.customdomain.com" in your portal.conf and restart the portal stack .

 

Additional Information

Keep internal as the custom domains set in tenant.json is not officialy supported