*[Related components and artefacts](#related-components-and-artefacts)
*[Development](#development)
<!-- TOC -->
# Disclaimer
@@ -28,8 +32,9 @@ We do not offer support for upgrades before we reach openDesk 1.0.
Though we try to ease the pain when it comes to 0.x upgrades. That is what this document is for.
Limitations:
- We assume that the PV reclaim policy is set to `delete`, so expect that PVs get deleted as soon as the related PVC was deleted and will cover an explicit delete for PVs.
**Limitations:**
- We assume that the PV reclaim policy is set to `delete`, so expect that PVs get deleted as soon as the related PVC was
deleted and will cover an explicit delete for PVs.
# Releases upgrades
@@ -40,16 +45,16 @@ Limitations:
#### MatrixID localpart update
Until 0.9.0 openDesk used the LDAP entryUUID of a user to generate the user's MatrixID. Due to restrictions of the
Matrix protocol an update of a MatrixID is not possible, therefore it was technically convenient to use the UUID
Matrix protocol, an update of a MatrixID is not possible, therefore, it was technically convenient to use the UUID
as it is immutable (see https://de.wikipedia.org/wiki/Universally_Unique_Identifier for more details on UUIDs.)
From the user experience perspective that was a bad approach, so from now on by default the username, that
is also used for logging into openDesk, is used to define the localpart of the MatrixID.
From the user experience perspective, that was a bad approach, so from now on, by default, the username which
is also used for logging into openDesk is used to define the localpart of the MatrixID.
For existing installations: The changed setting only affects users that login to Element the first time. Existing
user accounts will not be harmed. If you want existing users to get new MatrixIDs based on the new setting, you
need to update their external ID in Synapse and deactivate the old user afterwards. The user will get a new
Matrix account from the scratch, losing the existing contacts, chats and rooms.
need to update their external ID in Synapse and deactivate the old user afterward. The user will get a new
Matrix account from scratch, losing the existing contacts, chats and rooms.
The following Admin API calls are helpful:
- GET /_synapse/admin/v2/users/@<entryuuid>:<matrixdomain> get the user's existing external_id (auth_provider: "oidc")
@@ -58,7 +63,7 @@ The following Admin API calls are helpful:
- POST /_synapse/admin/v1/deactivate/@<entryuuid>:<matrixdomain> deactivate old user with JSON payload:
`{ "erase": true }`
For more details check the Admin API documentation:
For more details, check the Admin API documentation:
You can enforce the old standard with the following setting:
@@ -70,11 +75,12 @@ functional:
useImmutableIdentifierForLocalpart: true
```
#### Fileshare configurability
#### File-share configurability
We provide now some configurability regarding the sharing capabilities of the Nextcloud component.
Now we provide some configurability regarding the sharing capabilities of the Nextcloud component.
The new default is different from the standard until now. To keep the current state after the upgrade from 0.9.0 you have to provide the following settings:
The new default is different from the standard until now.
To keep the current state after the upgrade from 0.9.0, you have to provide the following settings:
```
functional:
@@ -86,6 +92,64 @@ functional:
enforceSharingPasswords: false
```
#### Updated default subdomains in `global.hosts`
We have streamlined the subdomain names used by openDesk to be more user-friendly and to avoid the use of specific
product names.
This results in following change of default subdomain naming: