Unable to add multiple Webauthn keys in the same settings flow

[roboptics]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

In the SelfServiceSettingsFlow, it is only possible to add a webauthn key once in the same settings flow. If after submitting the first key, the same settings flow is used add a new webauthn key, the error below is shown:

Error Status: Internal Server Error (500)
Reason: Expected WebAuthN in internal context to be an object.
Message: An internal server error occurred, please contact the system administrator
Request: 71cf8e4c-ecf1-9332-b598-5207ab28c5aa

While browsing for a solution on the online ory custom ui implementation and the ory console, it was possible to see that the later actually creates a new settings flow after adding each webauthn key. This is the workaround we are currently using.

Furthermore, while trying to replace the problem in the online ory custom ui implementation, the following error is shown:

Could not find any login identifiers. Did you forget to set them? This could also be caused by a server misconfiguration.

But it is probably due to a missing configuration in the identity schema (although in our custom implementation it works).

Please advise.

Reproducing the bug

Simple try to use the same SelfServiceSettingsFlow to add more than one webauthn keys. Only the first submit works.

Relevant log output

No response

Relevant configuration

No response

Version

0.0.1-alpha.169

On which operating system are you observing this issue?

Windows

In which environment are you deploying?

Docker Compose

Additional Context

No response

[aeneasr]

I think this has since been resolved :)

[roboptics]

Tested today with Ory.Client version 0.2.0-alpha.60 and the issue seems to remain. Additionally it was also detected for the totp method in the registration flow.