Skip to content

Conversation

@fisx
Copy link
Contributor

@fisx fisx commented Jan 27, 2022

Release notes

  • The nginz chart now configures nginx to only allow cross-origin requests from an explicit allow list of subdomains. By default these are:

    nginz:
      nginx_conf:
        allowlisted_origins:
        - webapp
        - teams
        - account

    If you changed the names of these services, you must adjust those names in the nginz config as well. (charts/nginz: Add restrictive CORS headers to all URLs and explicitly… #1630)

  • Backend now separates conversation access control for guests and services. The old access roles are still supported but it is encouraged to upgrade clients since mapping between the old access roles and the new access roles is not isomorphic. For more details refer to the API changes below or the Swagger docs.
    Old clients are fully supported; if new clients and old clients are mixed, to old clients, either guests of services may appear to be enable if they are not, which may lead to error messages (confusing but harmless). (SQSERVICES-1083 Separate Access Control For Guests And Services #2035)

API changes

  • Endpoints that recently have accepted access_role in their payload will now accept access_role_v2 as well which will take precedence over access_role. See Swagger docs for how values are mapped. Endpoints that recently have returned access_role in their payload will now additionally return the access_role_v2 field. (SQSERVICES-1083 Separate Access Control For Guests And Services #2035)

Features

Bug fixes and other updates

Internal changes

Federation changes

jschaul and others added 21 commits January 18, 2022 17:23
…in certificate. (#2054)

* generate cert with multiple domains in the SAN

also, the subject CN has yet another value than the ones inside Subject
alternative name fields.

* add unit test for multi-domain cert
* cabal wrapper: define CONFIG_SHELL

* add changelog
Merge release 2022-01-18 back into develop
* Tag a negative test case for X509v3 Extended Key Usage

* Tag a test for remote user removal when guests disallowed

- When the access is updated such that it disallows guests from
accessing, all guests, both local and remote, are kicked out of the
conversation. This just tags such a test case.

* Tag a negative test for getting remote conversation details
* Add licenses

* Changelog

* Refresh headroom.

* Changelog

Co-authored-by: Matthias Fischmann <[email protected]>
* Split up Spar.Data

* make format

* Fix test

* changelog
…upByTeam (#2068)

* Rename ScimTokenStore.GetByTeam -> ScimTokenStore.LookupByTeam

* changelog

* CI
Also, provide better swagger doc inspired by MultiVerb and add names to endpoints (including the public one).

Use PushNotificationStream to abstract from FromSourceIO: This makes the conversion to ConduitT a bit easier to find, because it's literately written in the code.

Use latest master of Servant.
There are a lot left, but these ones should be safe to not change the
application's behavior.
* charts/nginz: Add restrictive CORS headers to all origins and explicitly allowlist allowed origins

* charts/nginz:  Set some default allowlisted origins

* Update changelog

* Spelling and style fixes in changelog.

* charts/nginz: fix fail-open behaviour in CORS configuration.

* charts/nginz: use singular "account" for consistency with other resources.

Co-authored-by: Molly Miller <[email protected]>
* Fix: nginz template broken for allowlisted_origins

* changelog
Fix bug: Calls config crashes when SFTs are unreachable
@fisx fisx force-pushed the release_2022_01_27 branch from 5890932 to 0641f90 Compare January 28, 2022 07:58
@fisx fisx merged commit 13a6a83 into master Jan 28, 2022
@fisx fisx deleted the release_2022_01_27 branch January 28, 2022 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants