mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 14:39:31 -05:00
[GH-ISSUE #9079] User creation with Microsoft SSO won't work properly #15378
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#15378
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vincentk222 on GitHub (Jan 29, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9079
Bug Report
Installation Method
running openwebui in docker with latest image
Environment
Open WebUI Version: v0.5.7
Operating System: ubuntu 22.04
Confirmation:
Expected Behavior:
Create a new user wit Microsoft SSO
Actual Behavior:
User is created without default avatar picture
Description
Bug Summary:
User is created without default avatar picture
Reproduction Details
Steps to Reproduce:
Docker compose relevant information:
image: ghcr.io/open-webui/open-webui:latest
environment:
- ENV=prod
- DEFAULT_USER_ROLE=user
- ENABLE_ADMIN_CHAT_ACCESS=false
- OAUTH_MERGE_ACCOUNTS_BY_EMAIL=true
- 'ENABLE_OAUTH_SIGNUP=true'
- 'MICROSOFT_CLIENT_ID=xxxxxx'
- 'MICROSOFT_CLIENT_SECRET=xxxxxx'
- 'MICROSOFT_CLIENT_TENANT_ID=xxxxxx'
- DATABASE_URL=sqlite:///data/webui.db
Start docker compose
Login with new user with SSO will create a new user in Open-Webui without avatar picture
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!