[GH-ISSUE #100] [Generic OIDC Providers] Latest version of generic-oidc does not work with latest version of panel beta32 #59

Closed
opened 2026-05-07 00:17:37 +02:00 by BreizhHardware · 5 comments

Originally created by @dougmaitelli on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/pelican-dev/plugins/issues/100

I had panel beta31 with the version of the generic-oidc plugin from the time beta31 was released and everything worked perfectly fine.
Today I upgraded the panel to beta32 and I had to update the plugin as well because it would fail to update.
As it stands, the OIDC does not work at all anymore, when I click on the OIDC provider button in the login screen is calls the https://pelican.mydomain.com/auth/oauth/redirect/pockert_id but it hangs there, nothing happens.

Originally created by @dougmaitelli on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/pelican-dev/plugins/issues/100 I had panel beta31 with the version of the generic-oidc plugin from the time beta31 was released and everything worked perfectly fine. Today I upgraded the panel to beta32 and I had to update the plugin as well because it would fail to update. As it stands, the OIDC does not work at all anymore, when I click on the OIDC provider button in the login screen is calls the `https://pelican.mydomain.com/auth/oauth/redirect/pockert_id` but it hangs there, nothing happens.
Author
Owner

@dougmaitelli commented on GitHub (Feb 10, 2026):

I found this in the logs:

[2026-02-10 10:20:57] production.ERROR: Unable to get the OIDC configuration from https://id.mydomain.com/authorize/.well-known/openid-configuration: Syntax error {"exception":"[object] (SocialiteProviders\\OIDC\\ConfigurationFetchingException(code: 0): Unable to get the OIDC configuration from https://id.mydomain.com/authorize/.well-known/openid-configuration: Syntax error at /var/www/pelican/vendor/kovah/laravel-socialite-oidc/src/Provider.php:245)
<!-- gh-comment-id:3876739173 --> @dougmaitelli commented on GitHub (Feb 10, 2026): I found this in the logs: ``` [2026-02-10 10:20:57] production.ERROR: Unable to get the OIDC configuration from https://id.mydomain.com/authorize/.well-known/openid-configuration: Syntax error {"exception":"[object] (SocialiteProviders\\OIDC\\ConfigurationFetchingException(code: 0): Unable to get the OIDC configuration from https://id.mydomain.com/authorize/.well-known/openid-configuration: Syntax error at /var/www/pelican/vendor/kovah/laravel-socialite-oidc/src/Provider.php:245) ```
Author
Owner

@dougmaitelli commented on GitHub (Feb 10, 2026):

The error above might be unrelated, I was testing other things at the time. I suspect the problem is actually caused by the livewire (4.5 -> 5.0) upgrade that happened in the panel.

When I click the OIDC button I can confirm it calls the panel, gets a response then uses livewire to fetch the authorize url which then fails aparently due to CORS.

If I open the URL manually on a new tab authentication works. All the other applications using the same OIDC work. Panel worked on previous version too.

<!-- gh-comment-id:3876817488 --> @dougmaitelli commented on GitHub (Feb 10, 2026): The error above might be unrelated, I was testing other things at the time. I suspect the problem is actually caused by the livewire (4.5 -> 5.0) upgrade that happened in the panel. When I click the OIDC button I can confirm it calls the panel, gets a response then uses livewire to fetch the authorize url which then fails aparently due to CORS. If I open the URL manually on a new tab authentication works. All the other applications using the same OIDC work. Panel worked on previous version too.
Author
Owner

@dougmaitelli commented on GitHub (Feb 11, 2026):

FYI @Boy132, sorry for tagging you, but just wanted to know if you are aware of this

<!-- gh-comment-id:3881723657 --> @dougmaitelli commented on GitHub (Feb 11, 2026): FYI @Boy132, sorry for tagging you, but just wanted to know if you are aware of this
Author
Owner

@KyleDerZweite commented on GitHub (Feb 12, 2026):

I had a similar issue, with the redirect and fixed it that, i changed:

Image

My problem was that:
->spa(fn () => !request()->routeIs('filament.server.pages.console'))

Livewire intercepted all link clicks via fetch/AJAX, including the OAuth redirect.
When Livewire fetches /auth/oauth/redirect/zitadel, it gets a 302 to Zitadel but can't follow a cross-origin redirect via fetch.
I exlcluded auth/oauth/redirect urls from the "FilamentView" and now my entire oidc flow works.

Kinda messed up my personal fork branching, so need to sort that out / re-fork it, before i commit anything, but maybe can be checked by someone else aswell

<!-- gh-comment-id:3893556741 --> @KyleDerZweite commented on GitHub (Feb 12, 2026): I had a similar issue, with the redirect and fixed it that, i changed: <img width="902" height="532" alt="Image" src="https://github.com/user-attachments/assets/e62feada-2c8f-448d-9478-3b894ef42e18" /> My problem was that: `->spa(fn () => !request()->routeIs('filament.server.pages.console'))` Livewire intercepted all link clicks via fetch/AJAX, including the OAuth redirect. When Livewire fetches /auth/oauth/redirect/zitadel, it gets a 302 to Zitadel but can't follow a cross-origin redirect via fetch. I exlcluded auth/oauth/redirect urls from the "FilamentView" and now my entire oidc flow works. Kinda messed up my personal fork branching, so need to sort that out / re-fork it, before i commit anything, but maybe can be checked by someone else aswell
Author
Owner

@Boy132 commented on GitHub (Feb 12, 2026):

This was fixed on the panel side with https://github.com/pelican-dev/panel/pull/2224

<!-- gh-comment-id:3893570469 --> @Boy132 commented on GitHub (Feb 12, 2026): This was fixed on the panel side with https://github.com/pelican-dev/panel/pull/2224
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/plugins#59
No description provided.