rustdesk / rustdesk/rustdesk-server-pro
OIDC to ADFS IdP won't get user personnal parameters
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 317
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
We've configured OIDC to a Microsoft ADFS IdP (not Entra, real On-Premise ADFS) and connection of users is ok but they get generated (?) username and no personnal information populated :
See screenshot section
How to Reproduce
1/ Generate new Applications Group on ADFS Server console with :
- Application Server
- URI redirection as https:///api/oidc/callback
- ID client
- ID secret
- Web API
2/ in Rustdesk server :
Settings --> OIDC
Add "New Auth Provider" with "Auth Type" as "Custom
Configure "Name", "Client id" and "Client Secret" from ADFS.
Specify "https:///adfs" as Issuer
Click Submit
3/ Login screen get a new button "Continue with , click on it
Login on your ADFS portal
Get redirected to Rustdesk, authentication ok but username appears as some generated value (always the same for a user if we delete him and connect again)
Expected Behavior
3/ Get redirected to rustdesk, authentication ok and username as ADFS username and email configured
Operating system(s) on local (controlling) side and remote (controlled) side
Server on Debian 13 / Docker
RustDesk Version(s) on local (controlling) side and remote (controlled) side
server : 1.7.2 / Webui
Screenshots
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the RustDesk server OIDC settings and the /api/oidc/callback flow, reproducing the configuration against an on-premises ADFS application group. Check how the callback result is turned into the RustDesk username and personal information; done means an ADFS-authenticated user receives the configured username and email instead of a generated value.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100