Open Menu
AllLocalCommunitiesAbout
lotide
AllLocalCommunitiesAbout
Login

Here is the mockup pic for adding Oauth Scopes in Nextcloud, but how should it actually be implemented?

⁨48⁩ ⁨likes⁩

Submitted ⁨⁨4⁩ ⁨days⁩ ago⁩ by ⁨kiol@lemmy.world⁩ to ⁨selfhosted@lemmy.world⁩

https://lemmy.world/pictrs/image/202559ac-f942-4f80-baaf-758614632201.png

Specific suggestions appreciated! Here is admin doc related section and more info on scopes. Here is github issue.

source

Comments

Sort:hotnewtop
  • Slotos@feddit.nl ⁨4⁩ ⁨days⁩ ago

    oauth.net/articles/authentication/

    That aside, why is nextcloud asking for scopes from remote API in the diagram? What is drawn on the diagram has little to do with OAuth scopes, but rather looks like an attempt to wrap ACL repository access into a new vocabulary.

    Scopes issued by the OAuth authorization server can be hidden entirely. The issuer doesn’t hold any obligation to share them with authorized party since they are dedicated for internal use and can be propagated via invisible or opaque means.

    I really can’t figure out what’s going on with that diagram.

    source
    • kiol@lemmy.world ⁨1⁩ ⁨day⁩ ago

      Thanks, this helped me better understand what is going on. Tried to formulate a response: github.com/nextcloud/server/issues/26233#issuecom…

      source
      • Slotos@feddit.nl ⁨1⁩ ⁨day⁩ ago

        I’d probably add that for something like nextcloud granted scopes can be an „orthogonal”–for the lack of a better word–subset of requested scopes.

        The set of requestable scopes has to be defined by the system itself, not its specific configuration. E.g. „files:manage”, „talk:manage”, „mail:read” are all general capabilities the system offers.

        However, as a user I can have a local configuration that adds granularity to the grants I issue. E.g.: „files:manage in specific folders” or „mail:read for specific domains or groups only” are user trust statements that fit into the capability matrix but add an additional and preferably invisible layer of access control.

        It’s a fairly rare feature in the wild and is a potential UX pitfall, but it can be useful as an advanced option on the grant page, or as a separate access control for issued grants.

        source
    • poVoq@slrpnk.net ⁨4⁩ ⁨days⁩ ago

      The email address scope is usually used as a common identifyer for linking accounts.

      source
    • chonkyninja@lemmy.world ⁨4⁩ ⁨days⁩ ago

      Thank you for answering this person, it amazes me how little people know of oauth, and it’s not a new tech.

      source
  • jaark@infosec.pub ⁨4⁩ ⁨days⁩ ago

    I think you are getting confused there, the doc you are linking to are for linking an external application to your Nextcloud account, whereas your diagram seems to be connecting Nextcloud to an external IDP.

    You may be wanting : apps.nextcloud.com/apps/oidc_login or apps.nextcloud.com/apps/user_saml

    source
  • possiblylinux127@lemmy.zip ⁨4⁩ ⁨days⁩ ago

    OpenID via keycloak

    source