RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Now that we have the Flatpak runtime/SDK on registry.redhat.io, we are hitting a couple of problems:

 * GNOME Software doesn't honor the Authenticator key in the https://flatpaks.redhat.io/rhel.flatpakrepo. This is a GNOME Software bug, but is worked around by a change already in the master branch of Flatpak - to use the OCI authenticator by default for OCI remotes.

(The symptom is that attempts to use the created remote give "error: No authenticator configured for remote `rhel`")

 * Flatpak doesn't correctly handle OCI authentication for system remotes (apparently we only tested authenticator to registry.redhat.io for user remotes.) There were two bugs here, one already fixed in master and one now fixed in master ( https://github.com/flatpak/flatpak/pull/3677)

https://github.com/flatpak/flatpak/pull/3686/ is a backport to the 1.6.x branch of the relevant changes. I've tested that with these changes, we can correctly install rhel.flatpakrepo through GNOME Sofwtare and then install com.redhat.Platform and com.redhat.SDK through the command line.

Upstream changes build fine locally.

I can install com.redhat.Platform from oci+https://flatpaks.redhat.io/rhel/ with the remote configured as system or user remote.

The GNOME software auth will be verified as soon as we have the appstream data available.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (flatpak bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4814