mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #1173] [Bug]: SSO/OIDC Account creation behavior #848
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#848
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @G4mm3l on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1173
Originally assigned to: @netscout2001 on GitHub.
Component
Bambuddy
Bug Description
I was able to successfully integrate the OIDC connection via Authentik. However, I noticed that when Bambuddy creates an account for a user who does not yet exist, it assigns an ID as the name rather than username which comes from the IdP. The new user is automatically assigned to the “Viewers” group. Changing the permissions is only possible once an email address has also been added.
It might make sense to use the attributes from the IdP, such as preferred_username and email, and store the OIDC ID separately.
Expected Behavior
New Account creation listed with username and email with groups synced to their group-permissions
Steps to Reproduce
Printer Model
None
Bambuddy Version
v0.2.3.2
SpoolBuddy Version
No response
Printer Firmware Version
No response
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
No response
Screenshots
No response
Additional Context
No response
Checklist
@cadtoolbox commented on GitHub (Apr 30, 2026):
This bug is applicable for the Azure Entra ID method as well, but we also don't have auto-create accounts enabled so it was a non-issue.
@netscout2001 commented on GitHub (Apr 30, 2026):
Thanks for the heads-up! The fix covers Azure Entra ID through the same code path.
@netscout2001 commented on GitHub (May 1, 2026):
@G4mm3l
Can you provide more information as requested in the pull request #1176?
@G4mm3l commented on GitHub (May 1, 2026):
Hey there @netscout2001, big thanks for enhancing this topic!
Regarding question 3 saving changes in the UI on OIDC created accounts i've had these behaviour:
the account gets created with ID:
Now it is impossible to save group-settings, because the email form is empty.
If i do any changes to the checkboxes, the save-button stays disabled.
I thought it should be a good way also to set the email address that comes from the IdP as well because of possible email-notifications through bambuddy.
It also would be a nice feature to sync users to their groups automatically if the groupname is also present in bambuddy, when the group claim is used.
I also discovered, that if i manually delete an existing oidc account in bambuddy, it is also possible to log in again via IdP but the user isnt created again on userlist. But i'm still testing this behaviour and would report a new issue regarding this.
@netscout2001 commented on GitHub (May 2, 2026):
Thread 1 & 2 is adressed here: https://github.com/maziggy/bambuddy/pull/1176
Thread 3 is out of scope for this PR: Neither the maintainer nor the contributor can reproduce this on current dev. The UsersPage edit modal disables password-reset/email controls but not groups or permissions, and email is optional in the schema. Dropped from this PR's scope — reduced to "needs reporter repro" in https://github.com/maziggy/bambuddy/issues/1173 for a separate follow-up if concrete steps surface.