ARTIFACTORY: How to properly configure a proxy when using JFConnect

ARTIFACTORY: How to properly configure a proxy when using JFConnect

AuthorFullName__c
Benny Caspi
articleNumber
000005880
ft:sourceType
Salesforce
FirstPublishedDate
2023-09-28T08:54:34Z
lastModifiedDate
2023-09-28
VersionNumber
3

JFConnect is the microservice that fetches entitlements from the subscription into a JFrog Platform deployment (JPD).
It provides a secure and automated mechanism for synchronizing entitlements and ensuring that the JPD is up to date with the latest entitlements of the subscription.

In environments that go through a proxy - we can get a jfconnect - config error (“could not retrieve config for key jfconnect.entitlements.config”),

User-added image

  • Another subject that is affected by this is when the customer runs next API call: <INSTANCE URL>/ui/api/v1/jfconnect/entitlements, 

The "entitlements" variable is empty, meaning that no entitlement has been retrieved
  • In addition, even though that opening an ssh session to the Artifactory and running a curl command from there with the proxy configured (through cURL for example), works, jfconnect microservice is not capable of working through the proxy configuration

In this situation we need to validate that jfconnect has an environment configuration section in the system.yaml of Artifactory (jfconnect proxy configuration)
For RPM / Deb Deployment
jfconnect:
    enabled: true
    usage:
        enabled: true
    env:
         http_proxy: "http://test.tes.com "
         https_proxy: "http://test.tes.com "
         no_proxy: “localhost, 127.0.0.1”

For K8s deployment
jfconnect:
    enabled: true
    extraEnvironmentVariables:
    -  name: http_proxy
       value: http://test.test.com/ 
    - name: https_proxy
       value: http://test.test.com/ 
    - name: no_proxy
       value: localhost,127.0.0.1
  • Please validate that you don’t have identical syntax issues in system.yaml
  • After filling the system.yaml - A restart is required for it to take effect.

Enable the debug log for jfconnect
To enable jfconnect debug log please use this in system.yml:
jfconnect:
  logging:
    application:
      level: "debug"