We recommend certificates are supplied to AppsAnywhere in .PFX (Personal Information Exchange) format as this format is password protected by default. The password associated with the .PFX file must be securely provided.
Certificates in different formats and articles with instructions on converting them are usually provided by the certificate authority e.g.,
If required, see Generating a certificate request (csr).
Applying SSL Certificates
Once the certificate has been provided by the certificate issuer, the .pfx file should be securely saved alongside the certificate request (csr) and key.
If SSL is terminated at the load balancer, the certificates only need to be applied on there. Otherwise, a member of the AppsAnywhere team will apply them on the servers.
Renewing SSL Certificates
When certificates are renewed, they will need to be updated on the services that host them, whether this is the load balancer or the AppsAnywhere servers.
If they are hosted on the load balancer, the team that manages the load balancer will be responsible for updating the certificates. This is possible without intervention form AppsAnywhere Support.
Otherwise, new certificates will need to be saved in the AppsAnywhere share, or one of the servers. A support ticket should then be raised to provide the certificate password and arrange a time for a member of the AppsAnywhere team to update it. No service outage is required, providing the load balancer is setup with health checks.