You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the issue report properly structured and detailed with version numbers?
Is this for Kubeflow development ?
Would you like to work on this issue?
You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.
Version
1.9
Describe your issue
I'm team i have installed latest version 1.9 in my EKS cluster and also i have my okta meta details client ID and secret followed by callback url and so on. all the pods are up and running inside Kubeflow components.
Post updating above configmap i have restarted the oauth2-proxy deployment and verified the oauth2-proxy pod logs
i can see auth success but followed by with message "No valid authentication in request. Initiating login"
[2024/09/13 16:40:34] 1.2.3.4:8080 GET - "/" HTTP/1.1 "" 302 462 0.001
[2024/09/13 16:40:34] [oauthproxy.go:1017] No valid authentication in request. Initiating login.
[2024/09/13 16:40:34] 1.2.3.4:8080 GET - "/" HTTP/1.1 "" 302 462 0.001
[2024/09/13 16:40:41] 2.3.4.5:4180 GET - "/ping" HTTP/1.1 "kube-probe/1.27+" 200 2 0.000
[2024/09/13 16:40:41] 2.3.4.5:4180 GET - "/ping" HTTP/1.1 "kube-probe/1.27+" 200 2 0.000
[2024/09/13 16:40:49] [oauthproxy.go:1017] No valid authentication in request. Initiating login.
[2024/09/13 16:40:49] 1.2.3.4:8080 GET - "/" HTTP/1.1 "" 302 462 0.001
[2024/09/13 16:40:51] 2.3.4.5:4180 GET - "/ping" HTTP/1.1 "kube-probe/1.27+" 200 2 0.000
[2024/09/13 16:40:51] 2.3.4.5:4180 GET - "/ping" HTTP/1.1 "kube-probe/1.27+" 200 2 0.000
viswa@company.com [2024/09/13 16:40:57] [AuthSuccess] Authenticated via OAuth2: Session{email:viswa@company.com user:abdefghiklmon PreferredUsername:viswa@company.com token:true id_token:true created:2024-09-13 16:40:57.315224546 +0000 UTC m=+4055.816491254 expires:2024-09-13 17:40:56.815439276 +0000 UTC m=+7655.316705964 groups:[KF-ADMIN]}
[2024/09/13 16:40:56] https://eks-sbx-aws.com GET - "/oauth2/callback?code=Q9pC8_ertuijslkalopqrs_tg9Q8sCrnwahAObTylQgjg&state=x9IF5isbdefghiklaopquytrewqahjdeJ-kmlmnhoaqsE%3A%2F" HTTP/1.1 "" 302 24 1.137
[2024/09/13 16:41:01] 2.3.4.5:4180 GET - "/ping" HTTP/1.1 "kube-probe/1.27+" 200 2 0.000
[2024/09/13 16:41:01] 2.3.4.5:4180 GET - "/ping" HTTP/1.1 "kube-probe/1.27+" 200 2 0.000
[2024/09/13 16:41:04] [oauthproxy.go:1017] No valid authentication in request. Initiating login.
[2024/09/13 16:41:04] 1.2.3.4:8080 GET - "/" HTTP/1.1 "" 302 462 0.001
[2024/09/13 16:41:04] [oauthproxy.go:1017] No valid authentication in request. Initiating login.
[2024/09/13 16:41:04] 1.2.3.4:8080 GET - "/" HTTP/1.1 "" 302 462 0.001
When accessing my dns name from browser https://eks-sbx-aws.com kubeflow dashboard waiting for username and pasword after passing the login details i'm getting page error like acces denied to access the webpage.
Validation Checklist
Version
1.9
Describe your issue
I'm team i have installed latest version 1.9 in my EKS cluster and also i have my okta meta details client ID and secret followed by callback url and so on. all the pods are up and running inside Kubeflow components.
Below the are files i have modified
Config map oauth2-proxy
Post updating above configmap i have restarted the oauth2-proxy deployment and verified the oauth2-proxy pod logs
i can see auth success but followed by with message "No valid authentication in request. Initiating login"
Here auth pods logs
Here is the dex config map value.yaml
When accessing my dns name from browser https://eks-sbx-aws.com kubeflow dashboard waiting for username and pasword after passing the login details i'm getting page error like acces denied to access the webpage.
Here is my k8s ingress.yaml file
Here is istio-ingressgateway
Steps to reproduce the issue
yaml and logs has been added
Put here any screenshots or videos (optional)
yaml and logs has been added
The text was updated successfully, but these errors were encountered: