-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
-
False
-
None
Right now we are using ebsAccountNumber in notifications-backend to fetch the users belonging to a respective ebsAccountNumber.
The ebsAccountNumber will be replaced somewhere in the future and will return null. So our request will probably not work anymore. But only after all applications have migrated to orgId instead of ebsAccountNumber.
For us this means:
the accountId we are passing in the ITUserRequest object needs to be changed to orgId (we have to use identityheader.org_id instead of identityheader.account)
This orgId comes from the identityHeader (we have to use identityheader.org_id instead of identityheader.account) and pass this to the ITUserRequest instead of accountId as we are doing it right now
Then we will have to change the property ebsAccountNumber in the ITUserRequest object to accountId.
We also need to migrate the existing ebsAccountNumbers. This can either be done on the fly (we are getting the orgId as well as the ebsAccountNumber with the identify header) or we migrate it once.
HINT: the accountId we are using right now is a different accountId than the it user service wants to get from us.