Flexera Library Updates - URLs required

[emtmeta]

One of customer wants the exact URLs to be whitelisted for all FNMS library updates , are the below URLs are correct or there are more ?

• https://www.managesoft.com:443/support/Compliance/RecognitionAfter82.cab
• https://www.managesoft.com:443/support/Compliance/EOSL.cab
• https://www.managesoft.com:443/support/Compliance/PURL.cab
• https://update.managesoft.com:443/ProductUseRights 

Reagrds,

Junaid Vengadan

[kclausen]

@emtmeta - The following information can be found in the Installing FNMS On-Premises document:

Note: If your server has Internet access controlled through a proxy server, the following URLs must be accessible:
• For the ARL: https://www.managesoft.com:443/support/Compliance/RecognitionAfter82.cab
• For the EOSL library: https://www.managesoft.com:443/support/Compliance/EOSL.cab
• For the SKU library: https://www.managesoft.com:443/support/Compliance/PURL.cab
• For the PURLs: https://update.managesoft.com:443/ProductUseRights, including access to any subdirectories of this that may be returned to your server in response to its initial request.

For backward compatibility, the HTTP protocol is also supported, with a server-side redirect being issued to the relevant HTTPS address. If you choose to use HTTP protocols, the corresponding addresses must also be authorized through your proxy server; but HTTPS support remains a requirement.

[kclausen]

@emtmeta - The following information can be found in the Installing FNMS On-Premises document:

Note: If your server has Internet access controlled through a proxy server, the following URLs must be accessible:

For the ARL: https://www.managesoft.com:443/support/Compliance/RecognitionAfter82.cab

For the EOSL library: https://www.managesoft.com:443/support/Compliance/EOSL.cab

For the SKU library: https://www.managesoft.com:443/support/Compliance/PURL.cab

For the PURLs: https://update.managesoft.com:443/ProductUseRights, including access to any subdirectories of this that may be returned to your server in response to its initial request.

For backward compatibility, the HTTP protocol is also supported, with a server-side redirect being issued to the relevant HTTPS address. If you choose to use HTTP protocols, the corresponding addresses must also be authorized through your proxy server; but HTTPS support remains a requirement.