I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
login should work
Actual Behavior:
After successful auth in Microsoft I get this error in browser: {"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}
Description
We use Microsoft OAuth and configured it as per documentation:
After successful auth in Microsoft I get this error in browser: {"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}
In the openwebui logs:
[open_webui.main] OAuth callback error: mismatching_state: CSRF Warning! State not equal in request and response.
INFO: 172.70.210.42:0 - "
GET /oauth/microsoft/callback?code=[REMOVED]&session_state=30a04c3a-7925-4878-a11a-ac161478462a HTTP/1.1
" 400 Bad Request
In Microsoft settings we have this: OIDC-based Sign-on > OIDC-based Sign-on › Attributes & Claims ›
we tried with different values combinations for OAUTH_EMAIL_CLAIM: email, username, preferred_username but error is the same
Originally created by @dmitryzykov on GitHub (Sep 19, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5535
# Bug Report
## Installation Method
helm open-webui-3.1.16
## Environment
- **Open WebUI Version:** 0.3.21
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
login should work
## Actual Behavior:
After successful auth in Microsoft I get this error in browser:
`{"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}`
## Description
We use Microsoft OAuth and configured it as per documentation:
```
MICROSOFT_CLIENT_ID: [REMOVED]
MICROSOFT_CLIENT_SECRET: [REMOVED]
MICROSOFT_CLIENT_TENANT_ID: [REMOVED]
ENABLE_OAUTH_SIGNUP: True
```
After successful auth in Microsoft I get this error in browser:
`{"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}`
In the openwebui logs:
```
[open_webui.main] OAuth callback error: mismatching_state: CSRF Warning! State not equal in request and response.
INFO: 172.70.210.42:0 - "
GET /oauth/microsoft/callback?code=[REMOVED]&session_state=30a04c3a-7925-4878-a11a-ac161478462a HTTP/1.1
" 400 Bad Request
```
In Microsoft settings we have this: OIDC-based Sign-on > OIDC-based Sign-on › Attributes & Claims ›
<img width="796" alt="image" src="https://github.com/user-attachments/assets/e80051bc-0af9-4fb1-a1e6-af59bafdfb64">
we tried with different values combinations for `OAUTH_EMAIL_CLAIM`: `email`, `username`, `preferred_username` but error is the same
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dmitryzykov on GitHub (Sep 19, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5535
Bug Report
Installation Method
helm open-webui-3.1.16
Environment
Confirmation:
Expected Behavior:
login should work
Actual Behavior:
After successful auth in Microsoft I get this error in browser:
{"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}Description
We use Microsoft OAuth and configured it as per documentation:
After successful auth in Microsoft I get this error in browser:
{"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}In the openwebui logs:
In Microsoft settings we have this: OIDC-based Sign-on > OIDC-based Sign-on › Attributes & Claims ›
we tried with different values combinations for
OAUTH_EMAIL_CLAIM:email,username,preferred_usernamebut error is the same