#12653 Some of HyperKitty's OAuth2 integrations are (sometimes) unconnectable.
Closed: Fixed with Explanation by zlopez. Opened by rokejulianlockhart.

What you would like us to do

Per issue/12582#comment-978214, remediate or remove unusable OAuth2 integrations in HyperKitty. Currently, this is sometimes FAS:

  1. 7b84f131b5a916d086e557ba9ce559cb6037d14e3b39c3a6558f23d1333ee045-1000031913.png

  2. 20250710T131016.png

However, it always applies to Facebook, SE, and X:

20250710T131040.png 20250710T131050.png

For Facebook, see youtu.be/b1NZ5C8Oo6Y.

When you need this to be done by

⪅ 2026


For FAS kerberos ticket works, but username and password ends up with 400 - Bad request.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: lists, low-gain, medium-trouble, ops

We can either disable the others or try to get them working again.

Metadata Update from @zlopez:
- Issue assigned to zlopez

I tried to reproduce it now and it works, I think we are hitting https://pagure.io/fedora-infrastructure/issue/12534

@rokejulianlockhart Could you try the login with FAS account few more times to confirm that? If you will log in after few retries it is probably the above issue.

rokejulianlockhart commented

@zlopez, FAS SSO consistently succeeds. I've tried 4 times, 3 on firefox-140.0-1.fc42.x86_64.rpm, and 1 on fenix-142.0a1.multi.android-arm64-v8a.apk, yet I've yet to see any failure (much less a 400).

So the FAS endpoint is working, just failing sometime.

I will probably disable the ones that are not working anymore, I don't think we need that many options for login to mailing lists anyway.

Non working options are now removed from both staging and production instance of mailman.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Metadata