Bug 1814045

Summary:	Fixes for Flatpak OCI authenticator
Product:	Red Hat Enterprise Linux 8	Reporter:	Owen Taylor <otaylor>
Component:	flatpak	Assignee:	David King <dking>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	dking, jkoten, lmiksik, mkrajnak, tpelka
Target Milestone:	rc
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	flatpak-1.6.2-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:10:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Owen Taylor 2020-03-16 20:56:52 UTC

Testing of Flatpak-1.6 against the internal container registry, registry.redhat.io, and registry.redhat.com revealed some defects that it would be good to fix for 8.2.

 * flatpak cannot authenticate to the internal container registry, blocking testing of whether installing the Flatpaks we will ship in 8.2 from a registry works correctly:

 https://github.com/flatpak/flatpak/pull/3460
 https://github.com/flatpak/flatpak/pull/3461
 https://github.com/flatpak/flatpak/pull/3471

 * downloading registry.redhat.io after prompting the user for username/password is twice as slow as it needs to be:

 https://github.com/flatpak/flatpak/pull/3472

Comment 2 Owen Taylor 2020-03-16 21:03:10 UTC

Switched from blocker to exception, since harm is is fairly modest:
 - installing Flatpaks from container registries would be less responsive and possibly look buggy
 - pre-release testing would be harder.

Risks of these fixes should, however, also be small - they are small self-contained patches that only affect the installing-from-OCI registries code paths.

Comment 8 errata-xmlrpc 2020-04-28 16:10:45 UTC

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, 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/RHEA-2020:1767