We need the deviceID and userID when calling auth endpoint in connection handler. The identity context has access to the most recent values - because it consumes the emitter on native.
Depends on D10777
Paths
| Differential D10786 Authored by tomek on Jan 22 2024, 5:54 AM.
Tags None Referenced Files
Subscribers
Details Summary We need the deviceID and userID when calling auth endpoint in connection handler. The identity context has access to the most recent values - because it consumes the emitter on native. Depends on D10777 Test Plan Console log the result of this function and check if it is correct on native and web.
Diff Detail
Event TimelineHerald added a subscriber: ashoat. · View Herald TranscriptJan 22 2024, 5:54 AM2024-01-22 05:54:55 (UTC-8) Harbormaster failed remote builds in B26028: Diff 35962!Jan 22 2024, 6:07 AM2024-01-22 06:07:56 (UTC-8) Harbormaster completed remote builds in B26030: Diff 35964.Jan 22 2024, 6:16 AM2024-01-22 06:16:26 (UTC-8) This revision is now accepted and ready to land.Jan 25 2024, 1:02 AM2024-01-25 01:02:17 (UTC-8) tomek added a child revision: D10813: [keyserver] Update auth request validator.Jan 25 2024, 6:39 AM2024-01-25 06:39:14 (UTC-8) tomek removed a child revision: D10814: [lib] Call keyserver auth.Jan 26 2024, 3:23 AM2024-01-26 03:23:26 (UTC-8) Closed by commit rCOMMe11d5b0539b8: [lib] Expose a function that allows reading deviceID, userID and accessToken (authored by tomek). · Explain WhyJan 29 2024, 3:44 AM2024-01-29 03:44:47 (UTC-8) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 36249 lib/components/keyserver-connection-handler.js
lib/shared/identity-client-context.js
native/identity-service/identity-service-context-provider.react.js
web/grpc/identity-service-context-provider.react.js
|