Yes, I have set a group mapping. It's kinda simple:
Type
User
Object Class
__GROUP__
Mapping
name
Int: name
ext: cn
Remote key: yes
Object Link
'cn=' + name + ',ou=groups,dc=example,dc=com'
I had a look at the working example you provided. Using "cn" as the
uidAttribute and in the DN
I can confirm that something seems to go wrong when generating the token as it
contains Asian characters and is way longer than expected.
I submitted a "forgot password" request via the enduser UI. This is the link it
wants me to open to reset the password:
When I make a REST call to the User Self confirmPasswordReset API for a users
I am getting a JPA persistence error. It seems that it is not able to save
the User object because of the token value, see value below. I just
recently upgrade to 2.0.4, prior to the upgrade this was working. Anyone
Have you set a mapping for GROUP? Could you share it?
Pay attention to the object link for groups. It should be something like
this: 'cn=' + name + ',ou=groups,dc=sample,dc=com'
If it is correct (as I thisnk) try to use as uidAttribute an attribute
that both USER and GROUP have, and is mapped
Hi Andrea,
Thank you for the quick reply!
I changed the uidAttribute as you suggested and sync works for users. However,
now I have the very same problem with groups whose remote IDs happen to be
empty.
So, when I change the uidAttribute to "uid", will the same connector also work
for
HI,
I cannot get the configuration of my LDAP Identity Store right. What I want is
a synchronization of user, groups and group memberships, meaning that
everything change in Syncope is propagated to LDAP and vice-versa.
With my current configuration below, I am able to pull users from LDAP
Hi Francesco,
I finally had the chance to give Syncope 2.0.4 a try on a fresh machine as you
suggested. Good news: I do not have any issues with the notification page any
more.
However, notifications are not working due to the email configuration. I found
the documentation in the reference
