Bug 2130655

Summary:	[RFE] Ability to restrict which services can be enabled / disabled for GNOME Online Accounts
Product:	Red Hat Enterprise Linux 9	Reporter:	Mitko Bogdanoski <mbogdano>
Component:	gnome-online-accounts	Assignee:	Milan Crha <mcrha>
Status:	CLOSED MIGRATED	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	mcatanza, tpopela
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Reopened
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-12 07:22:50 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mitko Bogdanoski 2022-09-28 18:53:34 UTC

Description of problem:

Currently it's not possible for an administrator to restrict which services can be enabled / disabled with GNOME Online Accounts.

On the other hand, it is possible to safelist online providers, but it's not possible to configure which services to be available per specific online provider.

Ideally, having a similar ability to safelist which of the available services are displayed in the Gnome Settings such as mail, calendar, printers, files, etc would be very convenient for the end users that will allow them to disable / enable specific services as needed.

Comment 3 Milan Crha 2022-09-29 06:26:18 UTC

Thanks for a bug report. This is a huge change. Such things should be done upstream and only then backported to RHEL. It would not make any sense to carry a custom patch only in RHEL, not only due to maintenance burden. You already have an upstream bug, thus I'd simply close this and wait for the upstream (which can take quite a long, because the GOA is more or less unmaintained these days).

Comment 4 RHEL Program Management 2022-09-29 06:26:25 UTC

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.

Comment 6 Milan Crha 2022-09-29 20:28:46 UTC

For what it's worth, I opened a merge request upstream with an implementation of this (see the linked upstream bug). It's currently awaiting review and some deeper testing. If approved, I can backport it to the RHEL 9. I'll keep this bug as is (aka closed) for now.

Comment 7 Tomas Popela 2024-06-12 07:15:23 UTC

Reopening and migrating to JIRA as the upstream change was merged and the customer would like to see this in 9.5.

Comment 9 RHEL Program Management 2024-06-12 07:17:49 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 10 RHEL Program Management 2024-06-12 07:22:50 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.