Introduction
1.Overview
This article explains an issue where access fails due to JFConnect entitlement errors. This typically happens when licenses or entitlements are not applied correctly or are no longer recognized by the system.
If you notice authentication or authorization errors in the logs, this guide will help you identify and resolve the issue.
2. Briefly explain the issue
When this issue occurs, you may see the following error in the JFConnect logs:
2025-12-11T17:17:31.433Z [jfcon] [ERROR] [3a18c5988027ff5e] [jes_authenticating_round_tripp] [main ] [ ] - Failed reading JES authentication token from storage: authentication was not setup yet [jes_auth_round_tripper]
Additional errors in the jfconnect-service.log may indicate that the entitlement service is unable to validate licenses,
2025-12-11T17:04:19.779Z [jfcon] [ERROR] [3a18c5988027ff5e] [entitlements_service.go:382 ] [main ] [ ] - [JFrog Entitlement Server]: couldn't validate licenses for licenses hash: [xxx] [entitlement_service]
2025-12-11T17:04:19.779Z [jfcon] [ERROR] [3a18c5988027ff5e] [entitlements_service.go:357 ] [main ] [ ] - Synced action 'register' - encountered unrecoverable error, entitlement service stopped until restart or license update. cause: status code 400 [entitlement_service]
These messages usually indicate that entitlements are out of sync or that the license information has not been registered correctly.
3. Outline the goal of the article
This article will help you resolve JFConnect access issues by,
- Verifying required JFrog service connectivity
- Confirming that JFConnect is enabled and functioning properly
- Resetting and reapplying entitlements so updated licenses are recognized
Troubleshooting and Resolution
Step 1: Verify JFConnect Connectivity
Confirm that JFConnect is enabled and that your Artifactory instance can reach the following endpoints:
* https://jcs.jfrog.io
* https://jes.jfrog.io
These services are required for authentication and entitlement validation.
For additional configuration details, refer to the official documentation:
https://jfrog.com/help/r/jfrog-installation-setup-documentation/jfconnect-microservice
Step 2: Review Current Entitlements
Retrieve the current entitlement details by sending a request to the following API:
http://<Artifactory_URL>/ui/api/v1/jfconnect/entitlements
This output is useful for validation and may be required if further troubleshooting is needed.
Step 3: Reset Entitlements in the Database
Based on the log entries, the issue is commonly related to license data not being applied or recognized correctly.
Important:
Always take a full database snapshot before making any changes, especially in Production environments.
After backing up the database, execute the following SQL queries against the Artifactory database:
delete from access_platform_config where config_key like '%.license.key';
delete from access_platform_config where config_key = 'jfconnect.entitlements.config';
delete from access_platform_config where config_key = 'jfconnect.entitlements.register';
delete from access_platform_config where config_key = 'jfconnect.entitlements';
These queries clear existing entitlement and license entries, allowing the system to re-register and apply the most recent entitlements.
Step 4: Restart Services
Once the database changes are complete:
1. Restart Artifactory
2. Restart Xray (if applicable)
This ensures the updated entitlements are loaded correctly.
Conclusion
Access issues related to JFConnect are usually caused by license or entitlement data being out of sync. Verifying connectivity, reviewing entitlements, and resetting the entitlement configuration allows the system to apply updated license information correctly.
Following the steps in this article should resolve the related authentication and authorization errors.
If the above documentation did not resolve your issue, please contact Jfrog Support for further assistance.