mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 23:15:57 +03:00
[GH-ISSUE #2131] [Feature Request] SSO username remap to different OIDC attributes #3268
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#3268
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 @tbfpartner on GitHub (Jan 30, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2131
Is your feature request related to a problem? Please describe.
When using the SSO feature, newly registered users currently get the first name (from/through the OIDC Provider) as a username in TRMM. In larger organizations, this quickly can become a problem.
Current workaround: renaming them manually.
Describe the solution you'd like
Make it possible to define, which OIDC-Provider-Field (attribute) is mapped to the username.
This feature request could also be extended to other fields or ultimatively, to the role assignment being mapped to "oidc provided groups". But this isnt actually part of this feature request - more an idea for the far future.