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:
- Set GITHUB_CLIENT_ID only
- Leave GITHUB_CLIENT_SECRET unset
- Start backend
- Attempt login
- 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.
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:
Additional context:
This creates a false-positive readiness state and leads to deterministic login failures.
This issue was automatically created from the KubeStellar Console.