[GH-ISSUE #45] Generic OIDC Provider Plugin can brick Pelican if no color is specified #34

Closed
opened 2026-05-07 00:17:18 +02:00 by BreizhHardware · 4 comments

Originally created by @dougmaitelli on GitHub (Dec 23, 2025).
Original GitHub issue: https://github.com/pelican-dev/plugins/issues/45

I installed and configured the Generic OIDC provider. One of the settings is the Provider Color, which is not mandatory and I left blank.
Now my installation is bricked and I can't open the panel at all:

[2025-12-23 07:18:38] production.ERROR: Filament\Support\Colors\Color::hex(): Argument #1 ($color) must be of type string, null given, called in /var/www/pelican/app/Filament/Pages/Auth/Login.php on line 82 {"exception":"[object] (TypeError(code: 0): Filament\Support\Colors\Color::hex(): Argument #1 ($color) must be of type string, null given, called in /var/www/pelican/app/Filament/Pages/Auth/Login.php on line 82 at /var/www/pelican/vendor/filament/support/src/Colors/Color.php:501)
[stacktrace]

Originally created by @dougmaitelli on GitHub (Dec 23, 2025). Original GitHub issue: https://github.com/pelican-dev/plugins/issues/45 I installed and configured the Generic OIDC provider. One of the settings is the Provider Color, which is not mandatory and I left blank. Now my installation is bricked and I can't open the panel at all: [2025-12-23 07:18:38] production.ERROR: Filament\Support\Colors\Color::hex(): Argument #1 ($color) must be of type string, null given, called in /var/www/pelican/app/Filament/Pages/Auth/Login.php on line 82 {"exception":"[object] (TypeError(code: 0): Filament\\Support\\Colors\\Color::hex(): Argument #1 ($color) must be of type string, null given, called in /var/www/pelican/app/Filament/Pages/Auth/Login.php on line 82 at /var/www/pelican/vendor/filament/support/src/Colors/Color.php:501) [stacktrace]
Author
Owner

@coderabbitai[bot] commented on GitHub (Dec 23, 2025):

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

  • Create Plan
Examples

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

<!-- gh-comment-id:3685511671 --> @coderabbitai[bot] commented on GitHub (Dec 23, 2025): <!-- This is an auto-generated issue plan by CodeRabbit --> ### 📝 CodeRabbit Plan Mode Generate an implementation plan and prompts that you can use with your favorite coding agent. - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan <details> <summary>Examples</summary> - [Example 1](https://github.com/coderabbitai/git-worktree-runner/issues/29#issuecomment-3589134556) - [Example 2](https://github.com/coderabbitai/git-worktree-runner/issues/12#issuecomment-3606665167) </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit) or [schedule a call](https://calendly.com/parth-coderabbit/issues-feedback)!
Author
Owner

@dougmaitelli commented on GitHub (Dec 23, 2025):

FYI @Boy132

<!-- gh-comment-id:3685512298 --> @dougmaitelli commented on GitHub (Dec 23, 2025): FYI @Boy132
Author
Owner

@dougmaitelli commented on GitHub (Dec 23, 2025):

I managed to fix my issue by changing the code to have a fallback color, then I fixed the settings in the settings. However this prob need to be addressed in the plugin to avoid other people having the same bug

<!-- gh-comment-id:3685553893 --> @dougmaitelli commented on GitHub (Dec 23, 2025): I managed to fix my issue by changing the code to have a fallback color, then I fixed the settings in the settings. However this prob need to be addressed in the plugin to avoid other people having the same bug
Author
Owner

@Boy132 commented on GitHub (Dec 23, 2025):

That's actually a bug on the panel, it should allow "no color" for oauth providers.
https://github.com/pelican-dev/panel/pull/2044 will fix that.

<!-- gh-comment-id:3686718417 --> @Boy132 commented on GitHub (Dec 23, 2025): That's actually a bug on the panel, it should allow "no color" for oauth providers. https://github.com/pelican-dev/panel/pull/2044 will fix that.
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#34
No description provided.