azuread provider does not support multiples tenants
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.6k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
I'm testing with my azure environment where we have multiples tenants. example
tenant A: holds all the users, mfa, etc.
tenant B: users synced from tenant A
Application created in tenant B fails to logging stating
```Application with id xxx-xxx-xxxxx does not exists on tenant A```
# Possible solution
add option to include tenant id. If present, then use the tenant ID as part of the urls as azureadv2 does.
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 azuread provider and compare its tenant URL handling with azureadv2, as suggested in the issue. Trace the login URL construction and determine where an optional tenant ID would be accepted. Done means an application in tenant B can authenticate against the intended tenant without the current tenant-mismatch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100