-
Bug
-
Resolution: Unresolved
-
Major
-
3.23.0.GA, 3.24.1.GA
-
None
-
False
-
-
False
-
-
###Issue :
Customer is unable to authenticate using the GitHubAuthProvider and following error message when trying.
2025-10-14 13:28:44.896 [info] Device Authentication is triggered for scopes: user:email 2025-10-14 13:28:44.896 [info] GitHubAuthProvider: GET SESSIONS for scopes: user:email 2025-10-14 13:28:44.896 [info] GitHubAuthProvider: GET sessions - found 0 sessions for scopes: user:email 2025-10-14 13:28:44.897 [info] Device Authentication: found 0 existing sessions with scopes: user:email 2025-10-14 13:29:00.303 [info] Device Authentication: token for scopes: user:email has been generated successfully 2025-10-14 13:29:00.395 [info] GitHubAuthProvider: CREATE SESSION for scopes: ["user:email"] 2025-10-14 13:29:00.444 [error] GitHubAuthProvider: an error happened at session creation (get user step): Request failed with status code 500 2025-10-14 13:29:00.444 [error] An error has occurred at the Device Authentication flow: Request failed with status code 500
They trying to authenticate to "github.com", using `Device Authentication Flow` and running the command "GitHub : Device authentication".
They are in Disconnected environment and confirmed that they have not configured a cluster global proxy, but the devspace container is using proxy settings to be able to reach "github.com".
###Env:
Red Hat Openshift Dev Spaces 3.23
