Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][IMP][auth_saml] Res.users autoprovisioning feature on login #655

Open
wants to merge 1 commit into
base: 16.0
Choose a base branch
from

Conversation

arnaudlayec
Copy link

This commit add the possibility for Odoo administrator to specify a list of trusted "domains*" per SAML providers.
When a user tries to authenticate to Odoo using SAML, coming from such domain* & providers, its Odoo res.users account is automatically created (copied from base.default_user) instead of showing him/her 'Permission denied' or 'No access granted to this database'.
*domain refers to the suffix or login used for SAML authentication, like : [email protected], like from Google, Microsoft, ...

Thus, it removes for Odoo administrators who choose SAML authentication the tasks to pre-create all users manually or through SCIM connectors.
However, it does not remove the need to tailor users access rights after the 1st login of the user.

@OCA-git-bot
Copy link
Contributor

Hi @vincent-hatakeyama,
some modules you are maintaining are being modified, check this out!

Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants