Usage of multitenant app for ODOO in Entra ID (azure_oauth.rst)
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 1.3k
- Forks
- 12.1k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Can you clarify why a multitenant application is required?
As a customer we are investigating the integration of Odoo with entra id and have the created the application with client from our tenant only which needs to use the tenanted endpoint for authentication (as oposed to the common endpoint for multitenanted apps)
For clarification:
- We don't want users from other tenant to sign-in to odoo for our company
- The multitenanted application are typically created to offer a service broadly as a service provider, in that sense i don't get why odoo requires us to create an application when odoo can do it for everyone (aka: letting odoo handle the app registration is one of the goal of multitenanted apps)
- (Microsoft will put more importance on tenant validation to help customers detect trusted apps)
Cédric
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 content/applications/general/email_communication/azure_oauth.rst and review the current multitenant application guidance. Investigate the Entra ID tenant-specific versus common authentication endpoints, then update the documentation to explain why the recommended setup is required and address the stated customer concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100