Originally created by @gvo on GitHub (Apr 14, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.5
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 22.04
### Browser (if applicable)
Chrome
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using 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 listed steps to reproduce the bug in detail.
### Expected Behavior
- Click "Sign Out"
- Continue with Microsoft
- User is logged back in
### Actual Behavior
When user signs back in they receive **{"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}**.
### Steps to Reproduce
1. Click 'Sign Out'.
2. Inspect cookies - **oui-session** cookie remains. Other OWUI cookies have been removed.
3. Continue with Microsoft.
4. Receive **{"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}** error.
5. Manually delete the **oui-session** cookie.
6. Can successfully log back in.
### Logs & Screenshots

### Additional Information
- I'm using OWUI with Microsoft OAuth authentication.
- I transitioned from v0.6.2 to 0.6.5 today for testing. Rolling back to v0.6.2 made the issue disappear.
- OPENID_PROVIDER_URL="https://login.microsoftonline.com/{REDACTED_TENANT_ID}/v2.0/.well-known/openid-configuration"
GiteaMirror
added the bug label 2025-11-11 16:04:31 -06:00
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 @gvo on GitHub (Apr 14, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.5
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
Actual Behavior
When user signs back in they receive {"detail":"The email or password provided is incorrect. Please check for typos and try logging in again."}.
Steps to Reproduce
Logs & Screenshots
Additional Information
@Anaphylaxis commented on GitHub (Apr 14, 2025):
Not an issue here with Authentik and OIDC.