Skip to content

OAuth readiness reports configured when client secret is missing #6056

@aaradhychinche-alt

Description

@aaradhychinche-alt

User Request

Type: bug
Target: Console Application
Submitted by: @aaradhychinche-alt
Console Request ID: cb8de748-c16c-469b-8b54-3cc137b4998f

Description

What happened:
The backend marks OAuth as configured when only the client ID is set, even if the client secret is missing. Login flow then fails during token exchange.

What I expected:
OAuth should only be marked configured when both client ID and client secret are present and valid.

Steps to reproduce:

  1. Set GITHUB_CLIENT_ID only
  2. Leave GITHUB_CLIENT_SECRET unset
  3. Start backend
  4. Attempt login
  5. Observe failure during OAuth callback

Additional context:
This creates a false-positive readiness state and leads to deterministic login failures.


This issue was automatically created from the KubeStellar Console.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ai-fix-requestedai-processingAI is currently processing this issuekind/bugCategorizes issue or PR as related to a bug.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions