litmuschaos/litmus

OIDC naming is Dex-specific but works with any OIDC provider

Open

#5391 opened on Jan 13, 2026

View on GitHub
 (7 comments) (0 reactions) (0 assignees)HTML (3,702 stars) (574 forks)batch import
good first issuekind/enhancement

Description

Summary

The authentication system works great with any OIDC provider (we're using Keycloak), but the naming throughout the codebase is Dex-specific which is confusing.

Current Issues

  1. Callback endpoint: /auth/dex/callback - hardcoded with "dex" in the path
  2. Environment variables: DEX_OAUTH_CALLBACK_URL, DEX_OAUTH_CLIENT_ID, DEX_OAUTH_CLIENT_SECRET, DEX_ENABLED
  3. Documentation: Focuses heavily on Dex setup rather than generic OIDC configuration

Suggested Changes

  • Rename callback/login endpoint: /auth/dex/callback → /auth/oauth2/callback
  • Rename env variables:
    • DEX_ENABLED → OIDC_ENABLED
    • DEX_OAUTH_CALLBACK_URL → OAUTH_CALLBACK_URL or OIDC_CALLBACK_URL
    • DEX_OAUTH_CLIENT_ID → OAUTH_CLIENT_ID or OIDC_CLIENT_ID
    • DEX_OAUTH_CLIENT_SECRET → OAUTH_CLIENT_SECRET or OIDC_CLIENT_SECRET
  • Update docs to explain generic OIDC setup with Dex as one example

Why

Since ChaosCenter supports standard OIDC (works with Keycloak, Okta, Auth0, etc.), the naming should reflect that it's a generic OIDC integration, not Dex-specific. This would make it clearer for users that they can use any OIDC provider.

Additional Context

We successfully integrated ChaosCenter with Keycloak using the existing endpoints, but it was initially confusing whether Dex was required or just an example OIDC provider.

Contributor guide

Tech stack
go
Domain
authentication
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Go knowledgefamiliarity with OIDC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Rename all Dex specific references to generic OIDC across the codebase. Start by examining the callback route in dex router.go (linked in issue) and environment variable usage. Search for 'DEX' or 'dex ' in all files, then update routes, environment variables, and documentation accordingly. Ensure no breaking changes; consider deprecation warnings if needed.