As a user of a company, I want to sync contacts changes of my company

Desc:

Given I get all the contacts of my company yesterday in my ToM client
Given today, contacts have some changes (someone left company, someone onboarding, ...)
I want my contacts list in my ToM client up-to-date

DoD:

• endpoint to sync the contact changes

added To do label

changed the description

Hi @dphamhoang,

could you describe the API you want here ?

yeah, I want to cache the whole list in client side (don't want to fetch the whole list all the time). So I want to sync the change when open the app.

But if this endpoint take you a huge effort, please ignore it for now. Come back to it later.

Maybe not a huge work, but I'd like to know which behavior you want

Scenario:

1. client gets the whole list at State A -> cache the list + State A
2. LDAP has some changes (new joiner, someone left, ...) -> Contact list will be in State B
3. client need to sync the alpha from State A to State B

Questions:

• Do we need this? Do you think it is good or not
• Can you suggest the alternative way?

Hi @dphamhoang, alternative to get a stateless API:

• at regular intervals, the app pushes his list of contacts: _(new API inspired from matrix/lookup):

{
  "algorithm": "sha256",
  "pepper": "aaaaaaa",
  "addresses": {
    "company1.com": ["aaa", "bbb", "ccc"],
    "company2.com": ["ddd", "eee", "fff"],
  }
}

• the (federation) identity server send responses only from the servers (domains) it knows:

{
  "company1": {
    "aaa": "@dwho:company1.com",
    "bbb": "@rtyler:company1.com",
    "ccc": null
  }
}

• the app then knows that:
  • this server doesn't know "company2.com", then no changes are possible here
  • the user corresponding to "ccc" hash has no more any account in "company1.com"

removed To do label

assigned to @xguimard

Hi @dphamhoang, do you agree with my proposition ?

no, it is not what I want to say. I only want to get the change of company's contacts.

Today (t), contacts list from lookup/match with 100,

Next day (t + 1), contact list (identity server) right now are 120.

I don't want to call lookup/match again, I only want to call sync to get new contacts (20)

So IMO, we can ignore it in M0

Part of your contact may come from unknown servers.

• We can detect inactive users in domain owned by a Twake server (and synchronized with Federation ID Server after M0)
• But what do you call new contacts ? New users in the same organization ? Automatically added to your contacts ?

But what do you call new contacts ? New users in the same organization ?

yes, new employers of Linagora, or someone resigns.

That can be an acceptable feature for little companies (not for bigs!), do you plan to prompt user with the list of all new employees ?

yes, plan to fetch all employee this sprint

New employee since when, 1 day ?

so that why I propose we need state :(

State by device or by user ? After a query, automatically reset state ?

Storing client state on server side is always a bad idea. Imagine that client queries the server but has a network connection problem during response receive, when it will query a new time the server, the response will be different. We can use here an API inspired from HTTP cache: "Give me new users since XX". Then API becomes stateless

mentioned in commit 96453f7c

mentioned in commit 6bc0714a

mentioned in merge request !36 (merged)

mentioned in commit f862f966

mentioned in commit df4454d7

closed with merge request !36 (merged)