Device Authorization Flow broken with etcd storage

[MM53]

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.
• I am not looking for support or already pursued the available support channels without success.

Version

2.37.0

Storage Type

etcd

Installation Type

Official container image

Expected Behavior

Being able to use the oidc Device Authorization Flow with any type of storage.

Actual Behavior

When using the Device Authorization Flow with etcd as storage all login attempts resulted in an error page complaining about missing data like clientId, clientSecret, ... although those information were provided while generating the login url.

Steps To Reproduce

No response

Additional Information

No response

Configuration

No response

Logs

No response