Login Authentik OIDC CORS

[FlyingThaCat]

Current Behavior

When try to setup and login with authentik it just infinite loading, looking at console log it show cors error

Expected Behavior

Auth Succesfully

Steps to Reproduce

• Add authentik OIDC
• Link account
• Logout
• Login with authentik

Panel Version

1.0.0-beta32

Wings Version

1.0.0-beta23

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[FlyingThaCat]

changing the logic of this code fixed it

protected function getOAuthFormComponent(): Component
    {
        $actions = [];

        $oauthSchemas = $this->oauthService->getEnabled();

        foreach ($oauthSchemas as $schema) {

            $id = $schema->getId();

            $color = $schema->getHexColor();
            $color = is_string($color) ? Color::hex($color) : null;

            $actions[] = Action::make("oauth_$id")
                ->label($schema->getName())
                ->icon($schema->getIcon())
                ->color($color)
                ->action(fn () => redirect()->route('auth.oauth.redirect', ['driver' => $id])); //forced redirect
        }

        return Actions::make($actions);
    }

[Boy132]

This is likely caused by a proxy and/or webserver misconfiguration and not a bug.

[FlyingThaCat]

This is likely caused by a proxy and/or webserver misconfiguration and not a bug.

But the endpoint itself is working for other app, so that little odd

[CaptBlackbeard]

I can independently confirm this is a bug in Pelican, not a proxy/webserver misconfiguration. I hit the exact same issue with Authentik OAuth behind Traefik v3 on Docker Swarm.

Root cause: The OAuth button in app/Filament/Pages/Auth/Login.php uses Action::make()->url(), which in Filament 4 renders the tag with Livewire 3's wire:navigate attribute. When clicked, wire:navigate intercepts the navigation and uses fetch() to load the URL as an SPA transition. The server correctly returns a 302 redirect to the external OAuth provider (e.g., auth.example.com), but fetch() cannot follow cross-origin redirects — the browser blocks it, and the loading bar hangs.

This has nothing to do with proxy configuration. You can verify by:

1. Navigating directly to /auth/oauth/redirect/authentik in the browser address bar — works perfectly (standard browser redirect)
2. Clicking the button on the login page — hangs (Livewire fetch() intercept)

The fix proposed by @FlyingThaCat is correct. Replacing ->url(route(...)) with ->action(fn () => redirect()->route(...)) makes Livewire handle the redirect server-side, bypassing wire:navigate entirely. Alternatively, ->openUrlInNewTab() also works but opens a new tab which isn't ideal UX.

This affects any external OAuth provider (Authentik, Discord, Google, etc.) when Pelican is behind a reverse proxy on a different domain — which is the standard deployment pattern. It's a one-line fix in Login.php.

Would appreciate this being reopened and considered for a patch.

[Boy132]

This was fixed in #2224