Device Dehydration v2 - Device fails to rehydrate. Extra Security Key popup that will not accept a valid key.

[mjw3428]

Steps to reproduce

1. After logging in with SSO an pop for Security Key appears.

2. Entering a valid key is considered invalid in the dialog box and the continue button is never activated.
   

3. Clicking the close button on this dialog box will result in the verify device dialog box appearing. Clicking verify with securtiy key here will show the same dialog box as before, but this time the same key will be accepted.
   

This is with device dehydration set on within the Element config.

It looks to me like it is trying to access the Security Key before the session has initialised and, since this fails, the dialog box doesn't know what your Secret Key is and so it will never match.

As a result it looks like it never rehydrates the device on subsequent logins.

Outcome

What did you expect?

Valid Security Keys should be accepted and device rehydration should work.

What happened instead?

The error 'Invalid Security Key is shown and the continue button is disabled.

Operating system

Docker Container (Alpine?)

Browser information

Chrome 125

URL for webapp

1.11.68

Application version

Riot version: 153d0c3-react-ab6a94aa8f76-js-131e81401a04 Crypto version: Rust SDK 0.7.0 (068a0af), Vodozemac 0.6.0

Homeserver

Synapse v1.108.0

Will you send logs?

Yes

[t3chguy]

Will you send logs?
Yes

Not seeing any logs.

[mjw3428]

This relates to msc2697 and not the newer 3814. Closing as no longer relevant.