Web UI tenant error after upgrade (The tenant 'XXXXXXX' is not enabled or does not exist.)

PAM Core
1

Hello everyone,

After upgrading our Segura PAM instance, we started experiencing an issue accessing the Web UI using our configured FQDNs.

When accessing either of the following URLs:

  • https://sgrpam01.mycompany.local/
  • https://segura.mycompany.local/

we receive the following error:

The tenant 'sgrpam01' is not enabled or does not exist.

When accessing the second URL, the error references the tenant segura instead.

The instance is running in Multi-Tenant mode. The existing tenant is senhasegura , and we can access the Web UI using https://senhasegura.mycompany.local/ .

DNS and hostname configuration:

  • DNS records exist for both sgrpam01.mycompany.local and segura.mycompany.local .
  • Both hostnames resolve successfully to the expected server IP address, 192.168.0.101 .
  • The DNS server addresses are configured on the Segura appliance (e.g., 192.168.0.10 and 192.168.0.11 ).
  • The /etc/hosts file on the Segura appliance also contains an entry mapping the appliance hostname to its local loopback address and hostname aliases.

SSL certificate:

  • The certificate is issued to segura.mycompany.local .
  • sgrpam01.mycompany.local is included as a Subject Alternative Name (SAN).

The issue appeared after the upgrade. We need to continue using both sgrpam01.mycompany.local and segura.mycompany.local .

Has anyone encountered this behavior after an upgrade? Is there a supported configuration to make both hostnames work with the existing tenant, or could this be related to a change in tenant resolution introduced by the upgrade?

Any guidance on the recommended fix would be greatly appreciated.