🐛 Bug: JFrog Artifactory Plugin Not Displaying Image Data in Catalog Tab

[BanerjeeAgniva]

Workspace

jfrog-artifactory

📜 Description

The Container Image Registry for JFrog Artifactory plugin is not displaying container image metadata in the entity dashboard, even though the annotation and proxy configuration are correct. This is happening for the repository:

docker-trial/exposures:latest

---

✅ Environment Details

• JFrog URL: https://trialbby5u2.jfrog.io
• Artifactory Repository Path: docker-trial/exposures/_uploads and docker-trial/exposures/latest
• Annotation in catalog-info.yaml:

metadata:
  annotations:
    jfrog-artifactory/image-name: "docker-trial/exposures:latest"

• JFrog Plugin Configuration in app-config.yaml:

proxy:
  endpoints:
    /jfrog-artifactory/api:
      target: https://trialbby5u2.jfrog.io
      pathRewrite:
        api/proxy/jfrog-artifactory/api/?: /
      headers:
        Authorization: Bearer ${JFROG_TOKEN}
      secure: true

👍 Expected behavior

The plugin should resolve the image and show:

• Manifest metadata
• Image layers
• Image tags

👎 Actual Behavior with Screenshots

👟 Reproduction steps

1. Annotate your service entity YAML with jfrog-artifactory/image-name.
2. Navigate to the JFrog tab on the catalog entity page.
3. Observe: No data is shown in the UI.

📃 Provide the context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• [x] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [x] I have read the Code of Conduct

Are you willing to submit PR?

None

[benoneal396]

@BanerjeeAgniva If you inspect the page and go to Network when you navigate to that page do you see an error for the "query" call and it's saying "no authorization header"? That's the error I'm currently getting with this same plugin.

[christoph-jerolimov]

@its-mitesh-kumar can you also take a look into this issue?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[christoph-jerolimov]

Sorry we missed this. I will take a look and will follow up this week.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[its-mitesh-kumar]

I am checking this @christoph-jerolimov , Sorry it got missed.