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
Feature flag for exposing invite URLs to team admins [SQPIT-1368] (#2684)
This flag is generally locked and disabled. To be able to unlock/enable it, the team id must be added to the list of eligible teams.
The invitation URLs are meant to be used in automatized onboarding processes; e.g. rendering them as QR codes.
N.B. getting hold of the invitation URLs makes it possible to impersonate as someone else. That's why there's this two-configs solution: To make sure it's only activated when absolutely needed (and not accidentally.)
Co-authored-by: Sven Tennie <[email protected]>
Co-authored-by: Molly Miller <[email protected]>
Co-authored-by: Matthias Fischmann <[email protected]>
Optionally add invitation urls to the body of `/teams/{tid}/invitations`. This allows further processing; e.g. to send those links with custom emails or distribute them as QR codes. See [docs](https://docs.wire.com/developer/reference/config-options.html#expose-invitation-urls-to-team-admin) for details and privacy implications.
@@ -939,6 +943,24 @@ instance IsFeatureConfig MLSConfig where
939
943
Doc.property "allowedCipherSuites" (Doc.array Doc.int32') $Doc.description "cipher suite numbers, See https://messaginglayersecurity.rocks/mls-protocol/draft-ietf-mls-protocol.html#table-5"
940
944
Doc.property "defaultCipherSuite"Doc.int32' $Doc.description "cipher suite number. See https://messaginglayersecurity.rocks/mls-protocol/draft-ietf-mls-protocol.html#table-5"
0 commit comments