Fix Duo Field Names for Web Client #228

Closed
opened 2025-07-08 08:43:35 -04:00 by AtHeartEngineer · 0 comments

Originally created by @ratiner on 1/28/2025

Looks like the web client expects different fields for duo integration.
The changes were introduced in the following commit:
41e1d91558 (diff-2be3b52c1ad01eac329688bca2644e0aa1f819167ed8a9d52ed57f72e18b8aa8L4)
41e1d91558 (diff-8813d04cfcaad734e34e034e8a85eeb4a528d55aeb52b5c88e6bcbfced9fc260L13)

Web client sends different fields to the API (and also receives wrong ones):
clientSecret instead of secretKey and clientId instead of integrationKey

I believe, this PR can address this.

When saving:
image

When loading (Client Id and Client Secret is empty):
image

*Originally created by @ratiner on 1/28/2025* Looks like the web client expects different fields for duo integration. The changes were introduced in the following commit: https://github.com/bitwarden/clients/commit/41e1d9155850581be85d11e4b74088aa022f8381#diff-2be3b52c1ad01eac329688bca2644e0aa1f819167ed8a9d52ed57f72e18b8aa8L4 https://github.com/bitwarden/clients/commit/41e1d9155850581be85d11e4b74088aa022f8381#diff-8813d04cfcaad734e34e034e8a85eeb4a528d55aeb52b5c88e6bcbfced9fc260L13 Web client sends different fields to the API (and also receives wrong ones): `clientSecret` instead of `secretKey` and `clientId` instead of `integrationKey` I believe, this PR can address this. When saving: ![image](https://github.com/user-attachments/assets/21f13310-fce4-442f-baaa-df62d7bfc691) When loading (Client Id and Client Secret is empty): ![image](https://github.com/user-attachments/assets/dd70d557-4eaf-467e-b2ba-e2a03154be08)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#228