You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(disclaimer: I wrote the original code that populated those values in UserService)
I think we should remove any code from inside Owin.Scim that populates these two fields, they should be the responsibility of the application server. In my particular case, the application server does not even persist creation/modify date for users, thus I want to return null - I do not see anything in the spec saying they are required.
Just wanted to put it out there for discussion before I go remove that code.
The text was updated successfully, but these errors were encountered:
I think most implementors would rather this metadata be filled via business logic. It's their choice whether to persist it. Since no part of Resource.Meta is used during calculation of resource versioning, I wouldn't consider this an issue or design flaw.
We need to modify Meta.Created and Meta.LastModified to nullable DateTime.
We need to modify UserService and GroupService (in Owin.Scim) to not automatically populate these properties (since I don't persist them in the application server, I don't want to give any impression they exist at all)
(disclaimer: I wrote the original code that populated those values in UserService)
I think we should remove any code from inside Owin.Scim that populates these two fields, they should be the responsibility of the application server. In my particular case, the application server does not even persist creation/modify date for users, thus I want to return null - I do not see anything in the spec saying they are required.
Just wanted to put it out there for discussion before I go remove that code.
The text was updated successfully, but these errors were encountered: