github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 19:39:41 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[PR #6500] [PM-31954] Add server communication models to ConfigResponseJson #12768

New Issue
Closed
opened 2026-04-11 03:50:57 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-11 03:50:57 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/bitwarden/android/pull/6500

State: closed
Merged: Yes

🎟️ Tracking

PM-31954
Relates to https://github.com/bitwarden/server/pull/6892

📔 Objective

PM-27124 Add server communication models to ConfigResponseJson

Introduce new data models to the network module for handling server communication configuration received in the /config endpoint response.

Specifically, adds CommunicationJson and its nested BootstrapJson class to ConfigResponseJson to support server-driven cookie acquisition flows.

Specific Changes:

  • ConfigResponseJson.kt
    • Added a new nullable property communication: CommunicationJson? to ConfigResponseJson.
    • Defined the new serializable data class CommunicationJson, which contains a nullable bootstrap: BootstrapJson? property.
    • Defined the nested serializable data class BootstrapJson, which includes properties for SSO cookie vendor authentication:
      • type: String
      • idpLoginUrl: String?
      • cookieName: String?
      • cookieDomain: String?

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes
**Original Pull Request:** https://github.com/bitwarden/android/pull/6500 **State:** closed **Merged:** Yes --- ## 🎟️ Tracking PM-31954 Relates to https://github.com/bitwarden/server/pull/6892 ## 📔 Objective [PM-27124] Add server communication models to ConfigResponseJson Introduce new data models to the `network` module for handling server communication configuration received in the `/config` endpoint response. Specifically, adds `CommunicationJson` and its nested `BootstrapJson` class to `ConfigResponseJson` to support server-driven cookie acquisition flows. ### Specific Changes: - **`ConfigResponseJson.kt`** - Added a new nullable property `communication: CommunicationJson?` to `ConfigResponseJson`. - Defined the new serializable data class `CommunicationJson`, which contains a nullable `bootstrap: BootstrapJson?` property. - Defined the nested serializable data class `BootstrapJson`, which includes properties for SSO cookie vendor authentication: - `type: String` - `idpLoginUrl: String?` - `cookieName: String?` - `cookieDomain: String?` ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes [PM-27124]: https://bitwarden.atlassian.net/browse/PM-27124?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror added the pull-request label 2026-04-11 03:50:57 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#12768
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?