Page MenuHomePhabricator

[native] use identity wallet registration from final step of new registration workflow
ClosedPublic

Authored by varun on Feb 9 2024, 10:41 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 24, 4:02 AM
Unknown Object (File)
Tue, Dec 24, 4:02 AM
Unknown Object (File)
Tue, Dec 24, 4:02 AM
Unknown Object (File)
Tue, Dec 24, 4:02 AM
Unknown Object (File)
Tue, Dec 24, 4:02 AM
Unknown Object (File)
Wed, Dec 11, 10:53 PM
Unknown Object (File)
Fri, Dec 6, 7:41 PM
Unknown Object (File)
Nov 21 2024, 9:02 AM
Subscribers
None

Details

Summary

if usingCommServicesAccessToken, use identity wallet registration RPC for auth

Test Plan

confirmed that the action was dispatched successfully, verified that payload contents in redux matched local ddb

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

varun requested review of this revision.Feb 9 2024, 10:56 AM
This revision is now accepted and ready to land.Feb 9 2024, 11:22 AM
varun retitled this revision from [native] use identity wallet login from final step of new registration workflow to [native] use identity wallet registration from final step of new registration workflow.
varun edited the summary of this revision. (Show Details)
varun retitled this revision from [native] use identity wallet registration from final step of new registration workflow to [native] use identity wallet login from final step of new registration workflow.
varun edited the summary of this revision. (Show Details)

use identity wallet registration RPC

varun retitled this revision from [native] use identity wallet login from final step of new registration workflow to [native] use identity wallet registration from final step of new registration workflow.Feb 15 2024, 8:44 PM
varun edited the summary of this revision. (Show Details)

We had talked previously about falling back to the legacy APIs if the new ones were broken or failing for whatever reason. Is that still the plan? It looks like this code doesn't have a fallback mechanism like that

We had talked previously about falling back to the legacy APIs if the new ones were broken or failing for whatever reason. Is that still the plan? It looks like this code doesn't have a fallback mechanism like that

new plan is described in this comment: https://linear.app/comm/issue/ENG-6881/fallback-mechanism-for-login-and-registration#comment-9445e916