<?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 IdentityService vs. UserService in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/identityservice-vs-userservice/m-p/215923#M169053</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;SPAN&gt;I'm using activiti-app v1.4.1 and LDAP sync to fill 'user' and 'group' (and also add some users/groups manually from the activiti-app-gui (IdentityManagement))&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then I'm using activiti-engine 5.19 API (RuntimeService, TaskService, etc) in another module of our system.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;But, the IdentityService is using the tables 'act_id_user' and 'act_id_group' which make it a bit… hard to find the users I want (the tables are empty)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have found some forum threads of how to write my own UserService (and connect them to the 'user' and 'group' tables)…&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Another solution would be to not only depend on the activiti-engine in our seperate module, but the 'UserService' in activiti-app-logic.jar…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've been informed that the 'act_id_user' and 'act_id_group' will be removed in a later release, correct?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;What would be the proper way?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Just wait on the next release, where IdentityService using the same tables as UserService? Write my own service? Make our seperate module depend on activit-app-logic.jar?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Feb 2016 12:42:18 GMT</pubDate>
    <dc:creator>johlyn</dc:creator>
    <dc:date>2016-02-19T12:42:18Z</dc:date>
    <item>
      <title>IdentityService vs. UserService</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/identityservice-vs-userservice/m-p/215923#M169053</link>
      <description>Hi,I'm using activiti-app v1.4.1 and LDAP sync to fill 'user' and 'group' (and also add some users/groups manually from the activiti-app-gui (IdentityManagement))Then I'm using activiti-engine 5.19 API (RuntimeService, TaskService, etc) in another module of our system.But, the IdentityService is usi</description>
      <pubDate>Fri, 19 Feb 2016 12:42:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/identityservice-vs-userservice/m-p/215923#M169053</guid>
      <dc:creator>johlyn</dc:creator>
      <dc:date>2016-02-19T12:42:18Z</dc:date>
    </item>
    <item>
      <title>Re: IdentityService vs. UserService</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/identityservice-vs-userservice/m-p/215924#M169054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Indeed, the identityService (and its tables) are not used in the enterprise version.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The reason is because the identityService and its implementation is pretty soft when it comes to security.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;They might indeed be removed in a future release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In the Activiti BPM Suite, there is a UserService, GroupService, … which you can use (as a Spring bean) to get that data.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In your db, you can see they live under USERS, GROUPS, etc. tables.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Feb 2016 09:23:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/identityservice-vs-userservice/m-p/215924#M169054</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-02-24T09:23:48Z</dc:date>
    </item>
  </channel>
</rss>

