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.

Description of problem:
when trying to install a package via gpk-install-local-file, it always asks for a root password because it says the Package is untrusted. The gpg key for the repos that are used are installed, and it works under RHEL 7.1. (polkit rules are in place to allow users to install trusted Packages.

Version-Release number of selected component (if applicable):
gnome-packagekit-3.14.3-5.el7.x86_64

How reproducible:
Install a signed rpm via gpk-install-local-file $rpmname

Steps to Reproduce:
1. Install a signed rpm via gpk-install-local-file $rpmname
2. 
3. 

Actual results:
Package is seen as untrusted and thereofr a root password is needed

Expected results:
Package should be installed without any password

Additional info:
If i allow org.freedesktop.packagekit.package-install-untrusted in the polkit rule, the install works as expected. This worked well with the same config in RHEL 7.0 and 7.1

Still with RHEL 7.5? Are the packages being downloaded over http:// rather than https:// perhaps?

no longer needed in RHEL 7.6