FQDN change of the VIP AuthHub after the initial deployment

Products

• VIP Authentication Hub

Issue/Introduction

When running AuthHub, how to change the FQDN of the AuthHub after its deployment?

Environment

VIP Auth Hub

Release Oct.05

Resolution

At first glance, update the FQDN of AuthHub following these steps:

1. Get new certs for the new FQDN and do the usual step to create a secret with the certs;
2. Redeploy the ssp chart using regular upgrade procedure to specify new Ingress FQDN
   
   - Do "helm get values <releasename> -n <namespace>  > values.yaml";
   - Update values.yaml to specify new host FQDN and Secret (if new secret):
              
          ssp:
            ingress:
              host: <new host>
              tls:
                secretName: <new secret if necessary>
                    
   - Do "helm <releasename> -n <namespace>  -f values.yaml";
              
     - As this is not a real data schema upgrade but rather just an environment config upgrade, its Ok to add the option to skip the data schema upgrade:
        
                --set ssp.featureFlags.dataseed.enabled=true
   
   
3. Get Access Token for System Client and update the FQDN system setting :
   
   
   https://{{sspMgmtHost}}/system/admin/v1/Settings

   Body

   {
      "name": deploymentServiceProviderFQDN",
      "value": "myhost-ssp.sspdev.dev.broadcom.com",
      "origin": "global"
   },