SCIM server: updating attribute values causes NullReferenceExceptions on future reads about simpleidserver HOT 4 OPEN

I've switched to the very latest SimpleIdServer source to help diagnose this. I can see that the NullReference exception is actually coming from the first line of ComputeValueIndex: the value of SchemaAttribute is actually null in my case for the attribute with a full path of 'phoneNumbers'. Looking in the database, the SCIMRepresentationAttribute has a null SchemaAttributeId column value.

(Does it ever make sense for that to be null?)

from simpleidserver.

Hello,

The SchemaAttributeId is getting erased because the navigation properties are not considered in the BulkInsertAsync instruction :(. The issue has been resolved in the master branch. Could you please try again?

Kind Regards,

SID

from simpleidserver.

Yes, that looks much happier. The SchemaAttributeId is no longer getting into the database as null, and the ComputedValueIndex (whatever that is) is also being populated now, so reads work happily.

Thank you for the rapid fix!

If SchemaAttributeId is always a required value, would it be worth tweaking the definition of it so that nulls can't get into the database?
e.g.

public void Configure(EntityTypeBuilder<SCIMRepresentationAttribute> builder)
{
    ...
    builder.Property(a => a.SchemaAttributeId).IsRequired();
    ...
}

?

Btw, I'm currently attempting to add multi-tenant support for SCIM. I've seen the existing 'shadow property' example, but it requires copying quite a bit of CommandRepository/QueryRepository code. I've just about managed to make a set of code work that only:

1. subclasses the ScimDbContext (to filter on tenant and add tenant during writes)
2. subclasses RepresentationHelper so that I can make the attributes marked as SCIMSchemaAttributeUniqueness.SERVER and SCIMSchemaAttributeUniqueness.GLOBAL have slightly different behaviour (i.e. per-instance and global, respectively)

i.e. I've not had to make any changes to, or any copies of, any of the repositories, which is really nice.

Doing this would be a little easier if there was an extra protected constructor on ScimDbContext to allow easy subclassing, and if RepresentationHelper.CheckUniqueness were marked virtual. Would you be willing to accept small PRs along those lines?

from simpleidserver.

Hello,

Certainly, the SchemaAttributeId can be designated as a required property in the Entity Framework Configuration.

I would appreciate it if you could submit a pull request with your suggested modifications to simplify the ScimShadowProperty sample project :)

from simpleidserver.