Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OAuth2 with MS Azure not working #6866

Closed
2 of 7 tasks
Mr-Reca opened this issue May 6, 2019 · 3 comments · Fixed by #16544
Closed
2 of 7 tasks

OAuth2 with MS Azure not working #6866

Mr-Reca opened this issue May 6, 2019 · 3 comments · Fixed by #16544
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented

Comments

@Mr-Reca
Copy link

Mr-Reca commented May 6, 2019

  • Gitea version (or commit ref): 73ce024 with Go 1.12.1
  • Git version: 2.13.7
  • Operating system: openSUSE Leap 42.1
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I configured an Authentication Source using this guide https://blog.anoff.io/2019-03-23-configure-azure-ad-for-gitea/ so I can use Azure Active Directory for authenticate the users.

After the 2FA, the browser shows the error AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application. I checked the redirect_uri and it has this format: https://<host>:3000/user/oauth2/gitea/callback

gitea.log has this error when I go to that page (with error 500):
routers/user/auth.go:560 handleOAuth2SignIn()] [E] UserSignIn: could not find a matching session for this request

I'm using MariaDB Ver 15.1 Distrib 10.0.30-MariaDB

Screenshots

@lunny
Copy link
Member

lunny commented May 7, 2019

Have #6345 fixed your problem?

@Mr-Reca
Copy link
Author

Mr-Reca commented May 7, 2019

I tried #6345 before opening the issue

@stale
Copy link

stale bot commented Jul 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jul 6, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Jul 6, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants