Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-32981

Allow per-entity permissions for custom content types in the site search

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      It is possible for custom content types to appear in the dosearchsite.action results. Unfortunately it does not seem to be possible to control per-entity permissions in these results. This limits the usefulness of this feature.

      I have tried adding permissions via:

      contentEntity.addPermission(ContentPermission.createUserPermission(ContentPermission.VIEW_PERMISSION, user));

      but they seem to be ignores. Implementing the 

      public boolean canView(User user, Object target)

      method in the permission delegate also does not work.

            [CONFSERVER-32981] Allow per-entity permissions for custom content types in the site search

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3576585 ] New: JAC Suggestion Workflow 3 [ 4326987 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3169328 ] New: JAC Suggestion Workflow 4 [ 3576585 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3031073 ] New: JAC Suggestion Workflow 2 [ 3169328 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2533165 ] New: JAC Suggestion Workflow [ 3031073 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2276544 ] New: Confluence Workflow - Public Facing v4 [ 2533165 ]
            Adam Barnes (Inactive) made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Needs Verification [ 10004 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2173343 ] New: Confluence Workflow - Public Facing v3 [ 2276544 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1936328 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2173343 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1759128 ] New: Confluence Workflow - Public Facing v3 [ 1936328 ]
            jonah (Inactive) made changes -
            Description Original: It is possible for custom content types to appear in the dosearchsite.action results. Unfortunately it does not seem to be possible to control per-entity permissions in these results. This limits the usefulness of this feature.

            I have tried adding permissions via:
            {code}
            contentEntity.addPermission(ContentPermission.createUserPermission(ContentPermission.VIEW_PERMISSION, user));
            {code}
            but they seem to be ignores. Implementing the
            {code}
            public boolean canView(User user, Object target)
            {code}
            method in the permission delegate also does not work.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-32981].
              {panel}

            It is possible for custom content types to appear in the dosearchsite.action results. Unfortunately it does not seem to be possible to control per-entity permissions in these results. This limits the usefulness of this feature.

            I have tried adding permissions via:
            {code}
            contentEntity.addPermission(ContentPermission.createUserPermission(ContentPermission.VIEW_PERMISSION, user));
            {code}
            but they seem to be ignores. Implementing the
            {code}
            public boolean canView(User user, Object target)
            {code}
            method in the permission delegate also does not work.

              Unassigned Unassigned
              merickson Matthew Erickson
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: