Hi Jonas,
1) Is the entryUUID as 'Uid Attribute' by design not supposed to
work in syncope ?
entryUUID should work in Syncope very well. Probably, the trouble
that you have is in your mapping.
I mean, if you are using the default 'Uid Attribute' you have to map
it as remote key by speci
ave hooked up a connector to my openldap
>server.
>>>>>>
>>>>>> First sync, no problem all users are placed in the local storage.
>
>>>>>> Second sync however, even though the sync is marked as successful
>
>>>>>> I see f
all users are placed in the local storage.
Second sync however, even though the sync is marked as successful
I see from the logs syncope are trying to reinsert all entrys to
the local storage and fail due to key violation. I have set the
matching rule to update, and use the uid as remote key
sync however, even though the sync is marked as successful
I see from the logs syncope are trying to reinsert all entrys to
the local storage and fail due to key violation. I have set the
matching rule to update, and use the uid as remote key, mapped to
the local username field.
Can I create
successful I
see from the logs syncope are trying to reinsert all entrys to the
local storage and fail due to key violation. I have set the
matching rule to update, and use the uid as remote key, mapped to
the local username field.
Can I create this behaviour by misconfiguration, or do we have a
reinsert all entrys to the
local storage and fail due to key violation. I have set the matching
rule to update, and use the uid as remote key, mapped to the local
username field.
Can I create this behaviour by misconfiguration, or do we have a bug
here ?
It is quite common to fall into such
fail due to key violation. I have set the matching
rule to update, and use the uid as remote key, mapped to the local
username field.
Can I create this behaviour by misconfiguration, or do we have a bug
here ?
It is quite common to fall into such issues when configuring an LDAP
resource
oblem all users are placed in the local storage.
Second sync however, even though the sync is marked as successful I see
from the logs syncope are trying to reinsert all entrys to the local
storage and fail due to key violation. I have set the matching rule to
update, and use the uid as remot
nc is marked as successful I see from
the logs syncope are trying to reinsert all entrys to
the local storage and fail due to key violation. I have set the
matching rule to update, and use the uid as remote key, mapped to the
local username field.
Can I create this behaviour by misconfiguratio
