nextcloud / nextcloud/user_saml
Azure AD-Nextcloud integration does not really integrate groups
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Dear All,
I have succesfully integrated my NextCloud space with Azure Active Directory for a SSO. And it works.
In the claims, I have also set to return the groups of the user (which for a AD limitation can only be as ObjectID - but it's okay, they are imported and updated in NextCloud.
PROBLEMS:
- If I assign the AD user to a group, whenever he logs back in his groups are refreshed considering only the AD ones
- I thought to do the opposite, to use AD groups to set shares, etc... but I cannot share folders to AD groups
- and I cannot even share folders to AD users
- and in addition, groups can only be imported as ObjectID - which is already a limitation.
Is there anything that can be done to fix this?
Thanks in advance,
NC
Contributor guide
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 by reproducing the Azure Active Directory group-claim login flow described in the issue, then check how imported groups and users behave when sharing folders. Done means AD group memberships refresh correctly and folders can be shared with both AD groups and AD users, with the ObjectID limitation addressed if possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100