if usingCommServicesAccessToken, SIWE auth will now be done by the identity service
Details
tested the following cases:
- fresh eth wallet with enableNewRegistrationMode
- was navigated to the new registration wizard
- existing account with enableNewRegistrationMode
- was logged in
- fresh eth wallet with !enableNewRegistrationMode
- was registered with identity service
- existing account with !enableNewRegistrationMode
- was logged in
- invalid siwe signature
- alert displayed
handling reserved users will be tackled in https://linear.app/comm/issue/ENG-4033/update-clients-to-try-new-registration-after-failed-login-due-to
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
native/account/fullscreen-siwe-panel.react.js | ||
---|---|---|
79 ↗ | (On Diff #36897) | my understanding was that we only want to set dataLoaded once we manage to connect to @ashoat 's keyserver |
native/account/siwe-hooks.js | ||
104–110 ↗ | (On Diff #36897) | i think we have to await it on line 109 too otherwise the error gets swallowed and we can't alert from the fullscreen panel |
enableNewRegistrationMode and onAccountDoesNotExist need to be handled here
native/account/fullscreen-siwe-panel.react.js | ||
---|---|---|
77–89 ↗ | (On Diff #36897) |
|
native/account/siwe-hooks.js | ||
104–110 ↗ | (On Diff #36897) | @tomek's code is implicitly awaiting because dispatchActionPromise returns a Promise. He's suggesting it needs testing because that await might resolve at a slightly different time than the await siwePromise line |
native/account/siwe-hooks.js | ||
---|---|---|
101 ↗ | (On Diff #36897) | This probably will need to handle doNotRegister |
we have a new plan instead of a fallback mechanism including automated alerts, daily manual testing, and an opt-in mechanism for clients to inform us when there are issues