Re: Memberships

2015-03-25 Thread Manfredo Hopp
Should users with same id have same usersTO object in different SyncActions methods? If answer is yes I have a SyncAction where this is not happening. UserTo object with userid(153) in beforeUpdate() method : org.apache.syncope.common.to.UserTO@3af4d81a[ memberships=[] status=active

Re: Memberships

2015-03-20 Thread Marco Di Sabatino Di Diodoro
Il 19/03/2015 22:44, Manfredo Hopp ha scritto: Thank you Marco I tested it with no errors but no memberships where created, maybe there is some configuration missing. I verified action class containing your code is active. Please debug your syncAction and show syncope core logs. In my

Re: Memberships

2015-03-19 Thread Marco Di Sabatino Di Diodoro
Hi Manfredo, Il 18/03/2015 21:23, Manfredo Hopp ha scritto: Hi, from doc. The primary purpose of identity management systems is to manage data belonging to/users/; it is common practice in such systems to define as well entities called/roles/that helps in defining and enforcing security

Re: Memberships

2015-03-19 Thread Manfredo Hopp
Thank you Marco is it possible to do the same through SyncAction? I tried with: Membership mem = new Membership(); mem.setSyncopeRole(r); mem.setSyncopeUser(u); Regards 2015-03-19 5:38 GMT-03:00 Marco Di Sabatino Di Diodoro marco.disabat...@tirasa.net: Hi Manfredo, Il 18/03/2015

Re: Memberships

2015-03-19 Thread Marco Di Sabatino Di Diodoro
Hi Manfredo, Il 19/03/2015 16:09, Manfredo Hopp ha scritto: Thank you Marco is it possible to do the same through SyncAction? I tried with: Membership mem = new Membership(); mem.setSyncopeRole(r); mem.setSyncopeUser(u); UserTO userTO = (UserTO) subject; MembershipTO membershipTO = new