GithubHelp home page GithubHelp logo

Comments (2)

fabacab avatar fabacab commented on June 10, 2024

Hmmm. I think this project's wiki makes sense as a place to start drafting possible implementation ideas.

What comes up for me immediately is that on WP Multisite, a "site" is an implicit "grouping of content (and maybe also users)" but on NextCloud there is no direct analogue to this. This is why NextCloud's Groups feature exists, of course. So, does that mean the most intuitive mapping is:

  • WP Site → NextCloud Group?

Can NextClous groups contain other NextCloud Groups (can NextCloud Groups be nested)? If not, is this a better mapping:

  • WP User with a certain role → NextClous Group with that role as its name

If so, maybe the better hierarchy mapping is:

  • WP Site → NextCloud Group (for that Site)
    • WP User (Author) → NextCloud Group of Authors

For example: a website at subsite1.example.com might have two users, Alice and Bob. Alice is a Site Admin in WordPress (her user account in WP has the Administrator role associated with it). Bob is an Author. What does this mean for how they share files (using NextCloud)? Do they need access to the same files regardless? If so, maybe groups matter less. Might Bob need more access to NextCloud capabilities than Alice? If so, maybe a strict permission mapping from WP to NextCloud isn't sensible. Or maybe it would make sense to map the structure directly, and so we would have four NextCloud Groups, two nested one-level deep:

  1. Main Site Group (for the implicit group at example.com)
  2. Subsite1 Group (for subsite1.example.com)
    1. Admins of Subsite1 Group (for Alice)
    2. Authors of Subsite1 Group (for Bob)

In any event, I think it's important to work out what we want to happen in WP and NextCloud before worrying about what the LDAP DIT structure will look like.

from wp-ldap.

danaskallman avatar danaskallman commented on June 10, 2024

Back looking at this. Maybe start "simpler" (let me know if I am off base) since it may not be simple at all.

The one thing that seem important to start are site_id. So could a user just be part of any group they are a user on a site? And not look at roles at all right now. So if I am a user on two sites, I am part of those two groups in nextcloud for example.

The reason I note this is that the share option in nextcloud displays all users, but it would be good to see only users in groups associated with the sites they are part of. And not all users in the network.

Maybe after we can explore of network_id too.

from wp-ldap.

Related Issues (6)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.