Need to provide well known abstract principals for general purpose application use

XMLWordPrintable

    • Type: Improvement
    • Resolution: Applied
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      These fields on repositoryInfo specify the principals (groups/roles) that map to these concepts.

      • cmis:anonymous - The repository may or may not support anonymous access. This may be determined by whether this capability is supported by the repository or by the system administrator of the repository instance. If the repository instance does support anonymous access, then an application can determine what rights the anonymous user has.
      • cmis:anyone - If there is a notion of an "everyone" or "all" group, then this principal can determine what rights anyone might have. The most common case is that everyone has read-only access to a new document.

      The following macro is provided to make it easy to set ACLs:

      • cmis:user - This is the current user of the application and used for specifying permissions for that user.
      Show
      These fields on repositoryInfo specify the principals (groups/roles) that map to these concepts. cmis:anonymous - The repository may or may not support anonymous access. This may be determined by whether this capability is supported by the repository or by the system administrator of the repository instance. If the repository instance does support anonymous access, then an application can determine what rights the anonymous user has. cmis:anyone - If there is a notion of an "everyone" or "all" group, then this principal can determine what rights anyone might have. The most common case is that everyone has read-only access to a new document. The following macro is provided to make it easy to set ACLs: cmis:user - This is the current user of the application and used for specifying permissions for that user.

      In order to build applications that have general applicability against multiple repositories, some applications may need to be able to control access to some content where it may not know the exact prinicipal, but the prinicipal may be inferred. For instance, in Unix applications, it is possible for applications to specify that content may be world readable. This is related to the abstract permissions that CMIS introduces for READ, WRITE, DELETE and ALL.

      A use case is a collaborative content applications, such as a wiki, where forcing users to go through a series of dialogs to specify permissions is counter to the objective of making it easy to contribute and share content.

            Assignee:
            Ryan McVeigh (Inactive)
            Reporter:
            John Newton (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: