[Bug]: passkey / security key create --> randomly discoverable or non-discoverable passkey

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Open web browser, login to your Nextcloud (I tested in Hetzner)

From UI - Administration Settings - Personal - Security:

• Security key - Add Security key
• Passwordless Authentication - Add WebAuthn device

Behaviour of both buttons are unpredictable. Sometimes they (both!) seem to create non-discoverable FIDO2 credential and sometimes discoverable.

I was able first to create both into Bitwarden with some of my smartphones (android I think).

Now weeks later when I am trying again both seem to create device bound non-discoverable credential. I've done tests both when Bitwarden and Google are as autofill/passkey managers.

These both should be really tested thoroughly.

When creating FIDO2 security key in Nextcloud, what is the intention? Typically they are non-discovered credentials. Should it be as default like this or user have a choice as I WAS ABLE to save from this button to Bitwarden as discoverable credential.

In passwordless authentication typically peeps would want to save to password manager. But maybe not always?
When pressing Add security key or Add webauthn device buttons should there perhaps come a dialog where user can choose if he wants discoverable or non-discoverable credential to be saved...?

Also there is a bit related issue in windows Hello. It seems to be able to save only either one of them to TPM. It is version 25h2, not the latest one.

Steps to reproduce

1..
2.
3.

Expected behavior

.

Nextcloud Server version

32

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

I don't know details of the server versions except I got from hetzner update that it should be 32.0.9

List of activated Apps

All defaults + Two-Factor TOTP Provider, Two-Factor WebAuthn

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

Additional info

No response

Begin with the two registration entry points under Administration Settings > Personal > Security: Add Security key and Add WebAuthn device. Reproduce their discoverable versus non-discoverable behavior with the reported passkey managers and devices, then establish the intended behavior; done means the result is consistent and covered for the relevant WebAuthn flows.