AAD Login via OAuth fails with Dockerhub image "gitea/gitea" #12668

Closed
opened 2025-11-02 10:17:41 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @dominikschroeck on GitHub (Mar 18, 2024).

Description

I updated this morning to the most recent Gitea Docker image. Now I cannot login via AAD anymore using the AAD Oauth login. I just get sent back to the Homepage and the screen still looks like I am not logged in.

Could it be that the cookie is not set correctly?

Screenshots

image

Gitea Version

1.21.8

Can you reproduce the bug on the Gitea demo site?

No

Operating System

MacOs 14.3.1

Browser Version

Safari

Originally created by @dominikschroeck on GitHub (Mar 18, 2024). ### Description I updated this morning to the most recent Gitea Docker image. Now I cannot login via AAD anymore using the AAD Oauth login. I just get sent back to the Homepage and the screen still looks like I am not logged in. Could it be that the cookie is not set correctly? ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/28702562/febc09e6-e3ae-40de-9b93-0c58e42dd323) ### Gitea Version 1.21.8 ### Can you reproduce the bug on the Gitea demo site? No ### Operating System MacOs 14.3.1 ### Browser Version Safari
GiteaMirror added the topic/uiissue/needs-feedbacktype/bug labels 2025-11-02 10:17:41 -06:00
Author
Owner

@dominikschroeck commented on GitHub (Mar 18, 2024):

Update: Downgrading the image to 1.21.7 helped solve this issue. So I suppose it is specific to 1.21.8

@dominikschroeck commented on GitHub (Mar 18, 2024): Update: Downgrading the image to 1.21.7 helped solve this issue. So I suppose it is specific to 1.21.8
Author
Owner

@wxiaoguang commented on GitHub (Mar 18, 2024):

Does browser's "Private Window" (without any existing cookie) help?

Are you using Gitea under a sub-path behind reverse-proxy?


Update: I see you are using /gitea/ as sub-path. I think it could be related to https://github.com/go-gitea/gitea/issues/29757#issuecomment-199494019

I guess this issue is caused by #29534 , the cookies are different on `/subpath` and `/subpath/`.

So I think it won't happen in the future because the cookie path should be correct now.
@wxiaoguang commented on GitHub (Mar 18, 2024): Does browser's "Private Window" (without any existing cookie) help? Are you using Gitea under a sub-path behind reverse-proxy? ---- Update: I see you are using `/gitea/` as sub-path. I think it could be related to https://github.com/go-gitea/gitea/issues/29757#issuecomment-199494019 ``` I guess this issue is caused by #29534 , the cookies are different on `/subpath` and `/subpath/`. So I think it won't happen in the future because the cookie path should be correct now. ```
Author
Owner

@dominikschroeck commented on GitHub (Mar 19, 2024):

Yep, seems similar.

@dominikschroeck commented on GitHub (Mar 19, 2024): Yep, seems similar.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12668