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:

TB 102.7.1 breaks OAuth2 authentication with MS365.  102.7.1 build 2 should fix it.  See https://bugzilla.mozilla.org/show_bug.cgi?id=1810760

Same for EL 7 and 9

This will be fixed in 102.7.1 build2, for which we have release tracking bugs at bug 2166591.

*** Bug 2184197 has been marked as a duplicate of this bug. ***

Please ship the fixed thunderbird in CentOS Stream 8.

(In reply to Orion Poplawski from comment #5)
> Please ship the fixed thunderbird in CentOS Stream 8.

We've build every Thunderbird update in y-stream, so it should got into CentOS Stream 8. If it didn't, then it's an infrastructure problem and we (package maintainers) can't do much about it. Let me actually add people from https://bugzilla.redhat.com/show_bug.cgi?id=2156787 here that were handling something similar few months ago. For the completeness with 102.9+ we're blocked on CentOS Stream with https://issues.redhat.com/browse/CS-1516, but previous updates should be part of CentOS Stream 8