You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per-account configuration of conference call initiation (details: /docs/reference/config-options.md#conference-calling-1) (#1811, #1818)
Bug fixes and other updates
An attempt to create a 3rd IdP with the same issuer was triggering an exception. (#1763)
When a user was auto-provisioned into two teams under the same pair of Issuer and NameID, they where directed into the wrong team, and not rejected. (#1763)
Documentation
Expand documentation of conversations/list-ids endpoint (#1779)
Add documentation of the multi-table paging abstraction (#1803)
Document how to use IdP issuers for multiple teams (#1763)
All named Swagger schemas are now displayed in the Swagger UI (#1802)
Internal changes
Abstract out multi-table-pagination used in list conversation-ids endpoint (#1788)
Testing: rewrite monadic to applicative style generators (#1782)
Add a test checking that creating conversations of exactly the size limit is allowed (#1820)
Rewrite the DELETE /self endpoint to Servant (#1771)
Fix conversation generator in mapping test (#1778)
Refactored a few functions dealing with conversation updates, in an attempt to
make the conversation update code paths more uniform, and also reduce special
cases for local and remote objects. (#1801)
Merged http2-client fixes as mentioned in the comments of #1703 (#1809)
Some executables now have a runtime dependency on ncurses (#1791)
Minor changes around SAML and multi-team Issuers.
Change query param to not contain -, but _. (This is considered an internal change because the feature has been release in the last release, but only been documented in this one.)
Make conversation ID of the on-conversation-created RPC unqualified (#1766)
4 endpoints for create/update/get/list connections designed for remote users in mind. So far, the implementation only works for local users (actual implementation will come as a follow-up) (#1773)
The returned connection object now has a qualified_to field with the domain of the (potentially remote) user. (#1773)