Hi,
Il 13/12/18 16:02, pcrowder ha scritto:
I'm currently using Syncope 2.1.2 and it looks like any time a group
membership attribute is changed, new rows for each attribute (not null) is
added to the uplainattr table with the owner id set the user and the
previous rows are left in the table
On 13-dec-18, at 16:02, pcrowder pcrowder_t...@hotmail.com wrote:
> I'm currently using Syncope 2.1.2 and it looks like any time a group
> membership attribute is changed, new rows for each attribute (not null) is
> added to the uplainattr table with the owner id set the user and the
> previous
I'm currently using Syncope 2.1.2 and it looks like any time a group
membership attribute is changed, new rows for each attribute (not null) is
added to the uplainattr table with the owner id set the user and the
previous rows are left in the table with the owner id set to NULL.
Is that intended?
Hi everyone,
I'm still looking at the Syncope inner data model, and currently am
reviewing the membership concept.
I see that I can extend the attributes schema for the membership object,
but I don't understand how this is then applyed to a user.
What I understand is that a membership = a link
.
What I understand is that a membership = a link between a user a role.
More or less: membership attributes (and derived, and virtual) are user
attributes, but assigned only to users that belong to a certain role,
and with different values for each assigned role.
Then, I would try to attach
