Hi Philip, see my replies embedded below. Regards.
On 06/12/2017 09:32, Philip wrote:
I tried to reproduce the problem. However i cant let your syncope connect to our ldap because of security issues.
Of course: how could you connect syncope-vm to your LDAP unless the latter is publicly exposed on the Internet?
All I did was 1. create a plain schema(role) added it to the minimal user. 2. created a group name USERGROUP. Used dynamic assignment where role = user 3. added external resource resource-ldap. clicked finish(end of creating the group) 4. added new user SampleUser added needed attributes added a role user click finish gets link with the resource-ldap 5. attempt to edit SampleUser (eg. change firstname to SampleUserrrrr) click finish then;
Ok, so you cannot reproduce it.
in my case after i click finish i get the workflow[nullpointerexception] error but in your case it seems working fine.
You need to look at your Syncope deployment's log files for NullPointerException and report here the full stacktrace.
I really dont know why maybe it is because it is automatically propagated in my LDAP if i have my resource assigned?
If the LDAP resource defines provisioning information for the USER AnyType, and the created user is member of the group (even via dynamic condition), then this is the expected behavior:
https://syncope.apache.org/docs/reference-guide.html#memberships-relationships
-- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
