1. Check Certificate Details:
   • Open the AnalyticsPlus application in a web browser.
   • Click the padlock icon in the address bar to view certificate details.
     
     
   • Check the Subject Alternative Name (SAN) field.
   • Only use the field values listed under SAN (such as hostname or IP or Alias URL) when specifying the Hostname in the ServiceDesk Plus integration page.
2. If Required SAN Value Is Missing:
   • Generate a self-signed SSL certificate with the required SAN values by following the below instructions.

     Steps:
     
     Log in to the server where your Analytics Plus application is installed.
     
     Open Command Prompt (on Windows) or Terminal (on Linux).
     Navigate to the following directory:
     <Analytics Plus Home>\bin
     Run the SSL generation script with the required SAN values: 
     genSSLCert.bat dns:<hostname>,ip:<IP address>,dns:<FQDN or Alias URL>
     
     
     Example:
     If your Analytics Plus server has:
     
     Hostname: analytics-server
     
     IP Address: 192.168.1.1
     
     FQDn or Alias URL: analytics-server.acmecorp.com 
     Run the following command:
     genSSLCert.bat dns:analytics-server,ip:192.168.1.1,dns:analytics-server.acmecorp.com
     
     Notes:
     We recommend including all possible identifiers (hostname, FQDN, IP address or Alias URL) in the SAN field.
     
     Use ip: for IP addresses.
     
     Use dns: for hostnames, FQDNs, or Alias names.
     
     Ensure your Analytics Plus build number is 5220 or above to use the genSSLCert script.
     
     Replace the values with those specific to your server environment.
     This also applies if you're planning to use a custom alias URL (e.g., analyticsplus.company.com) for integration.
     
     In that case:
     
     Include the alias under dns: while generating the self-signed certificate.
     
     Make sure to configure this alias URL under Settings → Configuration → Advanced Settings → Alias URL in AnalyticsPlus.
     

   • This command creates a self-signed certificate with the required SAN entries.
   • Restart the AnalyticsPlus Service.
3. Validate the Certificate:
   • After generating the self-signed certificate, check the SAN field again to confirm it includes the correct hostname, IP address or Alias URL.
   • Once validated, configure the integration between AnalyticsPlus and ServiceDesk Plus using the appropriate hostname, IP address, or alias URL.

1. Verify the SAN Values:
   • Navigate to Settings → SSL Configuration in AnalyticsPlus.
   • Check the SAN field to identify the valid values (hostname or domain name).
2. Create a Custom Alias URL:
   • Go to Settings → Configuration → Advanced Settings.
   • Configure a Custom Alias URL based on one of the SAN values (e.g., analyticsplus.company.com).
3. DNS Configuration:
   • Update your DNS server to resolve the custom Alias URL to the AnalyticsPlus server's IP address.
   • Ensure that the Alias URL is reachable from the ServiceDesk Plus server.
4. Firewall and Access Verification:
   • From the ServiceDesk Plus server, try accessing the AnalyticsPlus application using the new Alias URL.
   • Ensure that no firewall rules are blocking access to this custom URL.
5. Proceed with Integration:
   • Once the Alias URL is verified and accessible, use this URL to configure the integration between ServiceDesk Plus and AnalyticsPlus.
     

Important Note:
By default, most valid SSL certificates do not include IP addresses or hostnames unless explicitly added in the SAN (Subject Alternative Name) field. Therefore, it is mandatory to create and use a custom Alias URL that matches one of the SAN entries when integrating AnalyticsPlus with ServiceDesk Plus.

Tip:
While it is technically possible to obtain a valid SSL certificate that includes an IP address or hostname:

• Public CAs rarely issue certificates for private IP addresses (like 192.168.x.x or 10.x.x.x).
• Hostnames (FQDNs) are the preferred standard and are widely supported.

1. Remove the existing valid SSL certificate from AnalyticsPlus.
2. Then, generate a self-signed SSL certificate with the required IP address or hostname included in the SAN field by following the steps outlined in Scenario 1 above.