question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

failed to discover OIDC configuration: unexpected status "400" - che-gateway

See original GitHub issue

Summary

i used below command to deploy eclipse-che

chectl server:deploy --che-operator-cr-patch-yaml=/Users/divine/Documents/office_tasks/TAP-4540/terraformCheJun14/eclipsecheFiles/che-operator-cr-patch.yaml --platform=k8s --installer=operator --debug --k8spoderrorrechecktimeout=1000000 --domain=eclipseche-dchelladurai-chejune15.abc.def.com --k8spodreadytimeout=1000000

i use below chectl version image

apiVersion: org.eclipse.che/v2
kind: CheCluster
metadata:
  name: eclipse-che
spec:
  components:
    database:
      externalDb: true
      postgresHostName: hostname.com
      postgresPort: "5432"
  networking:
    auth:
      identityProviderURL: https://dex-dchelladurai-chejune15.abc.def.com
      oAuthClientName: eclipse-che
      oAuthSecret: ZXhhbXsdfc2VjcmV0

i received below error in oauth-proxy container in che-gateway pod . please help me to fix this error. i’m not sure what details i have missed here

kubectl logs che-gateway-5f644cfdd8-qjj2b -c oauth-proxy -n eclipse-che

image

che-gateway-config-oauth-proxy configmap detail is below kubectl get cm che-gateway-config-oauth-proxy -n eclipse-che -o yaml image

below are the components running in my eclipse-che namespace image

Relevant information

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:14 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
tolushacommented, Jun 16, 2022

Could you check if all Eclipse Che pods are up and running?

1reaction
tolushacommented, Jun 16, 2022

Could you try https://eclipseche-dchelladurai-chejune15.calatrava.vmware.com/dashboard/ ?

Read more comments on GitHub >

github_iconTop Results From Across the Web

failed to discover OIDC configuration: unexpected status "403"
Hello, I have 4 EKS K8s clusters, all v1.22 I don't have any problems with 3 of them. I faced with the problem...
Read more >
Troubleshoot an OIDC provider and IRSA in EKS - Amazon AWS
Resolution. Check if you have an existing IAM OIDC provider for your cluster. If a provider already exists, then you receive an error....
Read more >
Test Connection to OIDC Provider REST Service - IBM
Use the Test Connection to OIDC Provider REST Service to test whether connection to the configured endpoint URLs of OpenID Connect (OIDC) provider...
Read more >
Error trying to connect from quarkus to keycloak - Stack Overflow
Which gave me this error: Caused by: org.keycloak.authorization.client.util.HttpResponseException: Unexpected response from server: 400 ...
Read more >
OpenID Connect (OIDC) on the Microsoft identity platform
This error can occur when the client application isn't registered in Azure AD or isn't added to the user's Azure AD tenant.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found