Introduction This article explores the possible causes of license expiry date discrepancies in Artifactory, often linked to JFConnect connectivity. JFConnect fetches entitlements from a central JFrog server, dynamically updating entitlements within Artifactory. As a result, license expiry dates in the UI update automatically, even if no new license is manually applied. This is expected behavior. When a new license is provided, JFConnect should automatically fetch and apply the updated expiry date. However, if this does not happen, it may indicate a connectivity issue with JFConnect when trying to reach the jes.jfrog.io endpoint. Issue When updating the licenses In Artifactory, the expiry date does not update and continues to show the old expiry. This occurs if the JFConnect service has previously fetched entitlement data (which includes expiry), but no longer has a connection to the entitlements server. This leads to Artifactory continuing to display the old expiry even with new licenses in place. Resolution Option A: Enable Connectivity to jes.jfrog.io Ensure that the JFConnect service is functional and able to connect to the https://jes.jfrog.io endpoint. To verify connectivity, check for errors like the following in the jfconnect-service.log:
[jfcon] [ERROR] [0a5160597f97c705] [jes_authenticating_round_tripp] [main]- Failed refreshing JES authentication token: Post "https://jes.jfrog.io/api/v1/token/refresh": dial tcp: lookup jes.jfrog.io on xx.xxx.xxx.xxx: no such host [jes_auth_round_tripper]
If you find this error or similar ones, it means Artifactory can not reach the server to verify entitlements. Check your network configurations to ensure that there are no firewalls, proxies or other network issues preventing this connectivity. If you can not allow this access then proceed with option B below. Option B: Load new Entitlements in Airgapped Mode. Artifactory allows the loading of entitlements even with an airgapped server. Follow the instructions in the official documentation to load the new entitlements: https://jfrog.com/help/r/jfrog-installation-setup-documentation/configure-jfrog-platform-in-an-air-gapped-environment Conclusion If license expiry dates do not update even after new licenses are in place, begin by checking whether JFConnect can connect to jes.jfrog.io. If it cannot, either restore connectivity or manually load the new entitlements in air-gapped mode to ensure the license expiry is correctly reflected in the UI. For additional support, contact JFrog Support.