<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Custom role visible in Alfresco Explorer in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273061#M226191</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;first of all, which Alfresco version are you using for your development?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Starting with Alfresco 4.0 and the introduction of SOLR, some permission checks (especially those performed on SOLR using indexed ACLs) are based on the "getReaders" method of the permission service, which uses a modified "Read" permission check (as far as I know without using implied permissions as would required in your case) to determine who can access the specific node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To my knowledge, this way of permission checking is mostly limited to filtering of result sets retrieved by SearchService.query and mostly in the SOLR use-case. Since I do not know the usage pattern that you used to determine that your permission group was not working, it is hard to say if this is what does affect you.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Generally, I do not yet understand your reason(s) for replacing the "Read" with the granular permissions in your custom role. As long as you don't plan to provide only a subset of these permissions, I'd advise to use "Read" instead.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 03 Feb 2013 14:47:46 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2013-02-03T14:47:46Z</dc:date>
    <item>
      <title>Custom role visible in Alfresco Explorer</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273060#M226190</link>
      <description>Hi all,I'm trying to add a custom role.Now, what one needs to do to get this to work is to edit the permissionDefinitions.xml file with your own custom role, and to edit the webclient.properties file for that new custom role (this part makes the role visible in Alfresco Explorer). That's all fine to</description>
      <pubDate>Thu, 31 Jan 2013 20:28:37 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273060#M226190</guid>
      <dc:creator>lista</dc:creator>
      <dc:date>2013-01-31T20:28:37Z</dc:date>
    </item>
    <item>
      <title>Re: Custom role visible in Alfresco Explorer</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273061#M226191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;first of all, which Alfresco version are you using for your development?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Starting with Alfresco 4.0 and the introduction of SOLR, some permission checks (especially those performed on SOLR using indexed ACLs) are based on the "getReaders" method of the permission service, which uses a modified "Read" permission check (as far as I know without using implied permissions as would required in your case) to determine who can access the specific node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To my knowledge, this way of permission checking is mostly limited to filtering of result sets retrieved by SearchService.query and mostly in the SOLR use-case. Since I do not know the usage pattern that you used to determine that your permission group was not working, it is hard to say if this is what does affect you.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Generally, I do not yet understand your reason(s) for replacing the "Read" with the granular permissions in your custom role. As long as you don't plan to provide only a subset of these permissions, I'd advise to use "Read" instead.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Feb 2013 14:47:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273061#M226191</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2013-02-03T14:47:46Z</dc:date>
    </item>
    <item>
      <title>Re: Custom role visible in Alfresco Explorer</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273062#M226192</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thank you for your answer.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's 3.4, Lucene. Replacing the "Read" with granular permissions was just a method to see where things stop working, since my custom role with granular permissions did not function. So I replaced granular permissions with "Consumer" role - it worked, I replaced "Consumer" role with "Read" permissions - it worked, I replaced "Read" permission with granular ones - it stopped working.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I just tried to see whether I was missing a piece, somewhere.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll be sure to post solution as soon as I find it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2013 10:26:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/custom-role-visible-in-alfresco-explorer/m-p/273062#M226192</guid>
      <dc:creator>lista</dc:creator>
      <dc:date>2013-02-04T10:26:14Z</dc:date>
    </item>
  </channel>
</rss>

