mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-02 17:59:36 +07:00
Merge pull request #2129 from nextcloud/wiswedel/purgeOldVersions
This commit is contained in:
@@ -2,12 +2,10 @@
|
||||
BigInt (64bit) identifiers
|
||||
==========================
|
||||
|
||||
Since Nextcloud 13 big integers are used to store identifiers and auto-increment keys in the database.
|
||||
Because changing columns on huge tables can take quite a while (up to hours or days), the update from
|
||||
Nextcloud 12 or earlier did not perform this migration on the filecache and activity table.
|
||||
|
||||
To make it easy to force the update on those tables too, we've added a console command, which can be used
|
||||
to migrate the remaining columns to bigints.
|
||||
Nextcloud uses big integers to store identifiers and auto-increment keys in the database.
|
||||
Because changing columns on huge tables can take quite a while (up to hours or days)
|
||||
depending on the number of files in the Nextcloud instance, this migration on the filecache-
|
||||
and activity tablehas to be triggered manually by a console command.
|
||||
|
||||
The command can safely be executed. It will show a success message when there is nothing to do::
|
||||
|
||||
@@ -25,5 +23,5 @@ to suppress the confirmation message append ``--no-interaction`` to the argument
|
||||
sudo -u www-data php occ db:convert-filecache-bigint --no-interaction
|
||||
|
||||
|
||||
.. note:: Similar to a normal update, you should shutdown your apache or nginx server or enable maintenance
|
||||
.. note:: Similar to a normal update, you should shutdown your Apache or nginx server or enable maintenance
|
||||
mode before running the command to avoid issues with your sync clients.
|
||||
|
||||
@@ -6,12 +6,12 @@ The primary purpose of the Nextcloud server-side encryption is to protect users'
|
||||
files on remote storage, such as Dropbox and Google Drive, and to do it easily
|
||||
and seamlessly from within Nextcloud.
|
||||
|
||||
In Nextcloud 9.0 the server-side encryption separates encryption of local and
|
||||
remote storage. This allows you to encrypt remote storage, such as Dropbox and
|
||||
Server-side encryption separates encryption of local and remote storage.
|
||||
This allows you to encrypt remote storage, such as Dropbox and
|
||||
Google, without having to also encrypt your home storage on your Nextcloud
|
||||
server.
|
||||
|
||||
.. note:: Starting with Nextcloud 9.0 we support Authenticated Encryption for all
|
||||
.. note:: Nextcloud supports Authenticated Encryption for all
|
||||
newly encrypted files. See https://hackerone.com/reports/108082 for more
|
||||
technical information about the impact.
|
||||
|
||||
|
||||
@@ -16,12 +16,12 @@ These conventions apply throughout this document:
|
||||
- Static strings are denoted as ``"some string"``.
|
||||
- The concatenation of strings is denoted as ``$variable."some string"``.
|
||||
|
||||
.. note:: This document describes the server-side encryption scheme as implemented by Nextcloud 16. Previous versions of Nextcloud implemented slightly different schemes which Nextcloud still supports for backwards compatibility. Files that have been encrypted by a recent version of Nextcloud should follow the structure documented below. However, files that have been encrypted by previous versions of Nextcloud may have slightly different structures.
|
||||
.. note:: However, files that have been encrypted in Nextcloud versions 15 and lower may have slightly different structures.
|
||||
|
||||
Key type: master key
|
||||
--------------------
|
||||
|
||||
While the master key encryption had to be enabled explicitly by calling ``./occ encryption:enable-master-key`` in older versions of Nextcloud it is now the default encryption mode in newer versions including Nextcloud 16. With master key encryption enabled there is one central key that is used to secure the files handled by Nextcloud. The master key is protected by a password that can be generated by the server administrator. The advantage of the master key encryption is that the encryption is transparent to the users but has the disadvantage that the server administrator is able to decrypt user files without knowing any user password.
|
||||
This is the default encryption mode in Nextcloud. With master key encryption enabled there is one central key that is used to secure the files handled by Nextcloud. The master key is protected by a password that can be generated by the server administrator. The advantage of the master key encryption is that the encryption is transparent to the users but has the disadvantage that the server administrator is able to decrypt user files without knowing any user password.
|
||||
|
||||
Key type: public sharing key
|
||||
----------------------------
|
||||
@@ -36,7 +36,8 @@ The recovery key is used to provide a restore mechanism in cases where the user
|
||||
Key type: user key
|
||||
------------------
|
||||
|
||||
While the user key encryption has been enabled by default in older versions of Nextcloud it now has to be enabled explicitly in newer versions including Nextcloud 16 by calling ``./occ encryption:disable-master-key``. With user key encryption enabled all users have their own user keys that are used to secure the files handled by Nextcloud. The user keys are protected by the user passwords. The advantage is that the server administrator is not able to decrypt user files without knowing any user password - unless the file is publicly shared or a recovery key is defined - but has the disadvantage that files are permanently lost if the users forget their user passwords - unless the files are (publicly) shared or a recovery key is defined.
|
||||
User key encryption needs to be explicitly activated by calling ``./occ encryption:disable-master-key``. In older versions of Nextcloud this had been enabled by default.
|
||||
With user key encryption enabled all users have their own user keys that are used to secure the files handled by Nextcloud. The user keys are protected by the user passwords. The advantage is that the server administrator is not able to decrypt user files without knowing any user password - unless the file is publicly shared or a recovery key is defined - but has the disadvantage that files are permanently lost if the users forget their user passwords - unless the files are (publicly) shared or a recovery key is defined.
|
||||
|
||||
.. note:: This method cannot be used with SAML authentication, because Nextcloud does not get a hold of any credentials whatsoever and therefore cannot use any users' passwords for encryption.
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ See :doc:`auth_mechanisms` for more information on authentication schemes.
|
||||
SMB update notifications
|
||||
------------------------
|
||||
|
||||
Starting with Nextcloud 10, Nextcloud can use smb update notifications to
|
||||
Nextcloud can use smb update notifications to
|
||||
listen for changes made to a configured SMB/CIFS storage and detect external
|
||||
changes made to the storage in near real-time.
|
||||
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
=================================================
|
||||
Configuring External Storage (configuration file)
|
||||
=================================================
|
||||
|
||||
Starting with Nextcloud 9.0, the :file:`data/mount.json` file for configuring
|
||||
external storages has been removed, and replaced with a set of
|
||||
:ref:`occ commands <files_external_label>`.
|
||||
@@ -6,18 +6,11 @@ The External Storage Support application enables you to mount external storage
|
||||
services and devices as secondary Nextcloud storage devices. You may also allow
|
||||
users to mount their own external storage services.
|
||||
|
||||
Nextcloud 9.0 introduces a new set of :ref:`occ commands for managing external storage <files_external_label>`.
|
||||
|
||||
Also new in 9.0 is an option for the Nextcloud admin to enable or disable sharing
|
||||
on individual external mountpoints (see
|
||||
:ref:`external_storage_mount_options_label`). Sharing on such mountpoints is
|
||||
disabled by default.
|
||||
For configuration of external storages via occ command, see :ref:`occ documentation <files_external_label>`.
|
||||
|
||||
Enabling External Storage Support
|
||||
---------------------------------
|
||||
|
||||
.. warning:: Enabling this app will disable the **Stay logged in** checkbox on the login page.
|
||||
|
||||
The External storage support application is enabled on your Apps page.
|
||||
|
||||
.. figure:: external_storage/images/enable-app.png
|
||||
|
||||
@@ -12,7 +12,6 @@ File sharing and management
|
||||
default_files_configuration
|
||||
primary_storage
|
||||
external_storage_configuration_gui
|
||||
external_storage_configuration
|
||||
external_storage/auth_mechanisms
|
||||
encryption_configuration
|
||||
encryption_details
|
||||
|
||||
@@ -57,8 +57,8 @@ e.g. you want to send the hourly emails always at the full hour, daily emails be
|
||||
people start to work in the morning and weekly mails shall be send on monday morning,
|
||||
so people can read up when starting into the week.
|
||||
|
||||
Therefore in Nextcloud 12 a console command was added to allow sending those emails
|
||||
intentionally. This allows to set up special cron jobs on your server with the known
|
||||
A console command is available to trigger sending those emails.
|
||||
This allows to set up special cron jobs on your server with the known
|
||||
granularity, instead of relying on the Nextcloud cron feature which is not very flexible
|
||||
on scheduling.
|
||||
|
||||
|
||||
@@ -68,7 +68,7 @@ Running ``occ`` with no options lists all commands and options, like this
|
||||
example on Ubuntu::
|
||||
|
||||
sudo -u www-data php occ
|
||||
Nextcloud version 9.0.0
|
||||
Nextcloud version 19.0.0
|
||||
|
||||
Usage:
|
||||
command [options] [arguments]
|
||||
@@ -103,14 +103,14 @@ Run it with the ``-h`` option for syntax help::
|
||||
Display your Nextcloud version::
|
||||
|
||||
sudo -u www-data php occ -V
|
||||
Nextcloud version 9.0.0
|
||||
Nextcloud version 19.0.0
|
||||
|
||||
Query your Nextcloud server status::
|
||||
|
||||
sudo -u www-data php occ status
|
||||
- installed: true
|
||||
- version: 9.0.0.19
|
||||
- versionstring: 9.0.0
|
||||
- version: 19.0.0.12
|
||||
- versionstring: 19.0.0
|
||||
- edition:
|
||||
|
||||
``occ`` has options, commands, and arguments. Options and arguments are
|
||||
@@ -142,15 +142,15 @@ The ``status`` command from above has an option to define the output format.
|
||||
The default is plain text, but it can also be ``json``::
|
||||
|
||||
sudo -u www-data php occ status --output=json
|
||||
{"installed":true,"version":"9.0.0.19","versionstring":"9.0.0","edition":""}
|
||||
{"installed":true,"version":"19.0.0.9","versionstring":"19.0.0","edition":""}
|
||||
|
||||
or ``json_pretty``::
|
||||
|
||||
sudo -u www-data php occ status --output=json_pretty
|
||||
{
|
||||
"installed": true,
|
||||
"version": "9.0.0.19",
|
||||
"versionstring": "9.0.0",
|
||||
"version": "19.0.0.12",
|
||||
"versionstring": "19.0.0",
|
||||
"edition": ""
|
||||
}
|
||||
|
||||
@@ -164,7 +164,7 @@ Enabling autocompletion
|
||||
.. note:: Command autocompletion currently only works if the user you use to execute the occ commands has a profile.
|
||||
``www-data`` in most cases is ``nologon`` and therefor **cannot** use this feature.
|
||||
|
||||
Since Nextcloud 11 autocompletion is available for bash (and bash based consoles).
|
||||
Autocompletion is available for bash (and bash based consoles).
|
||||
To enable it, you have to run **one** of the following commands::
|
||||
|
||||
# BASH ~4.x, ZSH
|
||||
@@ -327,7 +327,7 @@ Getting a single configuration value
|
||||
These commands get the value of a single app or system configuration::
|
||||
|
||||
sudo -u www-data php occ config:system:get version
|
||||
9.0.0.19
|
||||
19.0.0.12
|
||||
|
||||
sudo -u www-data php occ config:app:get activity installed_version
|
||||
2.2.1
|
||||
@@ -1105,7 +1105,7 @@ You can delete users::
|
||||
View a user's most recent login::
|
||||
|
||||
sudo -u www-data php occ user:lastseen layla
|
||||
layla's last login: 09.01.2015 18:46
|
||||
layla's last login: 09.01.2020 18:46
|
||||
|
||||
Read user settings::
|
||||
|
||||
@@ -1257,7 +1257,7 @@ Then choose your ``occ`` options. This lists your available options::
|
||||
|
||||
sudo -u www-data php /var/www/nextcloud/occ
|
||||
Nextcloud is not installed - only a limited number of commands are available
|
||||
Nextcloud version 9.0.0
|
||||
Nextcloud version 19.0.0
|
||||
|
||||
Usage:
|
||||
[options] command [arguments]
|
||||
|
||||
@@ -36,7 +36,7 @@ Enforcing two-factor authentication
|
||||
-----------------------------------
|
||||
|
||||
By default 2FA is *optional*, hence users are given the choice whether to enable
|
||||
it for their account. Since Nextcloud 15, admins may enforce the use of 2FA.
|
||||
it for their account. Admins may enforce the use of 2FA.
|
||||
|
||||
|
||||
Enforcement is possible systemwide (all users), for selected groups only and can
|
||||
|
||||
@@ -20,7 +20,7 @@ by a background task. See :doc:`../configuration_server/occ_command` section Dav
|
||||
|
||||
Reminder notifications
|
||||
----------------------
|
||||
Since version 17, Nextcloud handles sending notifications for events.
|
||||
Nextcloud handles sending notifications for events.
|
||||
|
||||
Nextcloud currently handles two types of reminder notifications: Build-in Nextcloud notifications and
|
||||
email notifications. For the emails to be send, you'll need a configured email server.
|
||||
|
||||
@@ -406,15 +406,9 @@ The `Nextcloud VM`_ is maintained by
|
||||
`T&M Hansson IT <https://www.hanssonit.se/nextcloud-vm/>`_ and several different versions are
|
||||
offered. Collabora, OnlyOffice, Full Text Search and other apps can easily be installed with the included scripts which you can choose to run during the first setup, or download them later and run it afterwards. You can find all the currently available automated app installations `on GitHub <https://github.com/nextcloud/vm/tree/master/apps/>`_.
|
||||
|
||||
The VM is made with VMware version 10 and it comes in different sizes and versions:
|
||||
The VM comes in different sizes and versions.
|
||||
|
||||
- 40 GB (VMware, VirtualBox, Hyper-V)
|
||||
- 500 GB (VMware, VirtualBox, Hyper-V)
|
||||
- 1 TB (VMware, VirtualBox, Hyper-V)
|
||||
- 2 TB (VMware & VirtualBox, Hyper-V)
|
||||
- Custom size? Please `ask us <https://www.hanssonit.se/#contact>`_.
|
||||
|
||||
You can find all the different version `here <https://shop.hanssonit.se/product-category/virtual-machine/nextcloud-vm/>`_.
|
||||
You can find all the available versions `here <https://shop.hanssonit.se/product-category/virtual-machine/nextcloud-vm/>`_.
|
||||
|
||||
For complete instructions and downloads see:
|
||||
|
||||
|
||||
@@ -2,44 +2,4 @@
|
||||
Release notes
|
||||
=============
|
||||
|
||||
Changes in Nextcloud |version|
|
||||
------------------------------
|
||||
|
||||
A detailed log of all changes can be found in the official `Changelog
|
||||
<https://nextcloud.com/changelog/>`_. There are also all current and previous
|
||||
versions linked.
|
||||
|
||||
Updates to Nginx configuration
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* In the Nginx configuration the Same-Origin header was added. Please add
|
||||
this line to your Nginx config: ``add_header X-Frame-Options "SAMEORIGIN" always;``
|
||||
See :doc:`installation/nginx`
|
||||
* For improvements in serving HTTP requests the Nginx configuration now has
|
||||
HTTP 2 enabled. Please update your Nginx config accordingly. See
|
||||
:doc:`installation/nginx`
|
||||
* The GZip configuration for Nginx was updated. See :doc:`installation/nginx`
|
||||
for details.
|
||||
|
||||
Common questions
|
||||
----------------
|
||||
|
||||
Could not install core app bundle
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The following error message is shown during the update: "Repair warning: Could
|
||||
not install core app bundle: Could not download app <app>".
|
||||
|
||||
This basically means that Nextcloud could not fetch the app from the appstore
|
||||
automatically. This could have multiple reasons: either you disabled the
|
||||
appstore with the config.php flag or your server could not reach the app store.
|
||||
The instance will work fine, but the features that are usually provided by this
|
||||
app are not available.
|
||||
|
||||
Theming changes
|
||||
---------------
|
||||
|
||||
With Nextcloud 12, CSS files have been merged into one server.css so in order
|
||||
to keep your theme working you should consolidate your existing css styles into
|
||||
a server.css file. As for the example theme the styles.css file has been
|
||||
renamed to server.css.
|
||||
See `the official changelog <https://nextcloud.com/changelog/>`_ for release notes.
|
||||
|
||||
@@ -10,7 +10,7 @@ The classloader is provided by Nextcloud and loads all your classes automaticall
|
||||
PSR-4 autoloading
|
||||
-----------------
|
||||
|
||||
Since Nextcloud 10 there is a PSR-4 autoloader in place. The namespace **\\OCA\\MyApp**
|
||||
Nextcloud uses a PSR-4 autoloader. The namespace **\\OCA\\MyApp**
|
||||
is mapped to :file:`/apps/myapp/lib/`. Afterwards normal PSR-4 rules apply, so
|
||||
a folder is a namespace section in the same casing and the class name matches
|
||||
the file name.
|
||||
|
||||
@@ -16,7 +16,7 @@ First the :doc:`development environment <../general/devenv>` needs to be set up.
|
||||
cd server
|
||||
git submodule update --init
|
||||
|
||||
.. note:: ``$BRANCH`` is the desired Nextcloud branch (e.g. ``stable17`` for Nextcloud 17, ``master`` for the upcoming release)
|
||||
.. note:: ``$BRANCH`` is the desired Nextcloud branch (e.g. ``stable19`` for Nextcloud 19, ``master`` for the upcoming release)
|
||||
|
||||
First you want to enable debug mode to get proper error messages. To do that set ``debug`` to ``true`` in the **config/config.php** file::
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ The CSS files reside in the **css/** folder and should be included in the templa
|
||||
// include vendor file (also allows array syntax)
|
||||
vendor_style('myapp', 'style'); // adds vendor/style.(s)css
|
||||
|
||||
.. note:: Since the version 12 of Nextcloud, we support ``SCSS`` natively.
|
||||
.. note:: ``SCSS`` is supported natively.
|
||||
You can migrate your files by simply renaming your ``.css`` files to ``.scss``.
|
||||
The server will automatically compile, cache and and serve it.
|
||||
The priority goes to the scss file. So having two file with the same name and a ``scss`` & ``css`` extension
|
||||
|
||||
@@ -55,8 +55,6 @@ On the final login the server will do a redirect to a url of the following forma
|
||||
This information will be used by the client to create a new account.
|
||||
After this the webview is destroyed including all the state the webview holds.
|
||||
|
||||
.. note:: On Nextcloud 12 the returned server is just the server address without any possible subfolder. This is corrected in Nextcloud 13.
|
||||
|
||||
|
||||
Converting to app passwords
|
||||
---------------------------
|
||||
@@ -119,8 +117,6 @@ Login flow v2
|
||||
|
||||
While the login flow works very nice in a lot of cases there are especially on dekstop application certain hurdles. Special proxy configuration, client side certificates and the likes can cause trouble. To solve this we have come up with a second login flow that uses the users default webbrowser to authenticate. Thus ensuring that if they can login via the web they can also login in the client.
|
||||
|
||||
The login flow v2 is available since Nextcloud 16. So check the status.php if it can be used on a given server.
|
||||
|
||||
To initiate a login do an anonymous POST request
|
||||
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
SCSS
|
||||
====
|
||||
|
||||
Since version 12 of Nextcloud, we support SCSS natively.
|
||||
Nextcloud supports SCSS natively.
|
||||
You can migrate your files by simply renaming your ``.css`` files to ``.scss``.
|
||||
The server will automatically compile, cache and serve it.
|
||||
The SCSS file is prioritized. Having two files with the same name and a ``scss`` & ``css`` extension
|
||||
@@ -18,7 +18,7 @@ will ensure backwards compatibility with <12 versions as scss files will be igno
|
||||
CSS variables
|
||||
=============
|
||||
|
||||
Since Nextcloud 14, app developers should use CSS4 variables so you get the values which Nextcloud defines. This way you can be sure that the theming and accessibility app can dynamically adjust the values.
|
||||
App developers should use CSS4 variables so you get the values which Nextcloud defines. This way you can be sure that the theming and accessibility app can dynamically adjust the values.
|
||||
|
||||
A list of available variables is listed in the server repository:
|
||||
https://github.com/nextcloud/server/blob/master/core/css/css-variables.scss
|
||||
@@ -30,7 +30,7 @@ https://github.com/nextcloud/server/blob/master/core/css/css-variables.scss
|
||||
SCSS icon mixins
|
||||
================
|
||||
|
||||
Since Nextcloud 14, we added some SCSS mixins and functions to add and manage SVG icons.
|
||||
Some SCSS mixins and functions are employed to add and manage SVG icons.
|
||||
|
||||
These functions need to be used to add the icons via background-image. They create a list of every icon used in Nextcloud and create an associated list of variables.
|
||||
This allows us to invert the colors of the SVGs when using the dark theme.
|
||||
|
||||
@@ -66,7 +66,7 @@ Share
|
||||
shares with hyperlinks. You can also see who you have shared with already,
|
||||
and revoke shares by clicking the trash can icon.
|
||||
|
||||
.. note:: Since version 9.0, you can see all re-shares of your original file shares.
|
||||
.. note:: You can also see all re-shares of your original file shares.
|
||||
|
||||
If username auto-completion
|
||||
is enabled, when you start typing the user or group name Nextcloud will
|
||||
@@ -211,7 +211,5 @@ Creating or connecting to a Federation Share link
|
||||
-------------------------------------------------
|
||||
|
||||
Federated Cloud Sharing allows you to mount file shares from remote Nextcloud
|
||||
servers, and manage them just like a local share. In Nextcloud 9 the process for
|
||||
creating a new sharing link is easier and more streamlined. See
|
||||
:doc:`federated_cloud_sharing` to learn to how to create and connect to new
|
||||
Federated Cloud shares.
|
||||
servers, and manage them just like a local share. See :doc:`federated_cloud_sharing`
|
||||
to learn to how to create and connect to new Federated Cloud shares.
|
||||
|
||||
@@ -48,20 +48,6 @@ those individually if necessary.
|
||||
Device-specific passwords and password changes
|
||||
----------------------------------------------
|
||||
|
||||
The behaviour of device-specific passwords during changes of the main password
|
||||
changed in different versions of Nextcloud.
|
||||
|
||||
Up to Nextcloud 13
|
||||
Device-specific passwords are removed on password change and also are
|
||||
removed once they are not valid anymore if an external user backend is
|
||||
used.
|
||||
|
||||
Nextcloud 14
|
||||
For local user backend the device-specific passwords are updated properly
|
||||
and continue to work. For external user backends (like LDAP/AD) the
|
||||
device-specific passwords are still removed.
|
||||
|
||||
Starting with Nextcloud 15
|
||||
For password changes in external user backends the device-specific passwords
|
||||
are marked as invalid and once a login of the user account with the main
|
||||
password happens all device-specific passwords are updated and work again.
|
||||
For password changes in external user backends the device-specific passwords
|
||||
are marked as invalid and once a login of the user account with the main
|
||||
password happens all device-specific passwords are updated and work again.
|
||||
|
||||
@@ -75,8 +75,7 @@ Teilen
|
||||
wem diese geteilt wurden. Um die Freigabe aufzuheben genügt ein Mausklick auf
|
||||
das Papierkorb-Symbol.
|
||||
|
||||
.. note:: Seit Version 9.0, können alle wiederholt geteilte Inhalte der
|
||||
ursprünglichen Dateifreigabe eingesehen werden.
|
||||
.. note:: Auch alle Weiterverteilungen einer ursprünglichen Dateifreigabe können eingesehen werden.
|
||||
|
||||
Wenn die automatische Wortvervollständigung des Benutzernamen aktiviert ist,
|
||||
wird mit der Eingabe eines Benutzernamens oder des Gruppennamens das Wort
|
||||
@@ -230,6 +229,4 @@ Erstellen oder Verbinden mit einer Federated Link-Freigabe
|
||||
|
||||
Mithilfe von Federated Cloud Freigaben können Dateifreigaben von entfernten
|
||||
Nextcloud-Servern hinzugefügt und diese wie eine lokale Freigabe verwaltet
|
||||
werden. Ab Nextcloud 9 ist die Einbindung in ein Verbund mit neuen
|
||||
Freigabeverbindungen einfacher und effizienter. Siehe
|
||||
:doc:`federated_cloud_sharing` für den Umgang mit Federated Cloud Freigaben.
|
||||
werden. Siehe :doc:`federated_cloud_sharing` für den Umgang mit Federated Cloud Freigaben.
|
||||
|
||||
@@ -11,7 +11,7 @@ Eine neue Federated Freigabe erstellen
|
||||
|
||||
Die Federated Freigabe wird standardmäßig bei neuen oder aktualisierten
|
||||
Nextcloud-Installationen aktiviert. Gehen Sie folgendermaßen vor, um eine neue
|
||||
Freigabe mit anderen Nextcloud-Servern oder ownCloud-Servern ab Version 9 zu
|
||||
Freigabe mit anderen Nextcloud-Servern oder ownCloud-Servern zu
|
||||
erstellen:
|
||||
|
||||
1. Gehen Sie in der linken Seitenleiste auf ``Alle Dateien`` und klicken Sie
|
||||
|
||||
@@ -214,7 +214,5 @@ Criando ou conectando-se a um link de compartilhamento de federação
|
||||
--------------------------------------------------------------------
|
||||
|
||||
O Federated Cloud Sharing permite montar compartilhamentos de arquivos a partir do Nextcloud remoto
|
||||
servidores e gerenciá-los como um compartilhamento local. Em Nextcloud 9 o processo para
|
||||
criar um novo link de compartilhamento é mais fácil e simplificado. Vejo
|
||||
: doc: `federated_cloud_sharing` para aprender como criar e conectar-se a novos
|
||||
Compartilhamentos da nuvem federada.
|
||||
servidores e gerenciá-los como um compartilhamento local. Vejo : doc: `federated_cloud_sharing`
|
||||
para aprender como criar e conectar-se a novos Compartilhamentos da nuvem federada.
|
||||
@@ -53,19 +53,7 @@ Senhas específicas do dispositivo e alterações de senha
|
||||
O comportamento das senhas específicas do dispositivo durante as alterações
|
||||
da senha principal foi alterado em diferentes versões do Nextcloud.
|
||||
|
||||
Até Nextcloud 13
|
||||
As senhas específicas do dispositivo são removidas na alteração de senha
|
||||
e também são removidas quando não são mais válidas se um back-end de
|
||||
usuário externo for usado.
|
||||
|
||||
Nextcloud 14
|
||||
Para o usuário local backend, as senhas específicas do dispositivo são
|
||||
atualizadas corretamente e continuam funcionando. Para back-ends de usuários
|
||||
externos (como LDAP / AD), as senhas específicas do dispositivo ainda são
|
||||
removidas.
|
||||
|
||||
Começando com o Nextcloud 15
|
||||
Para alterações de senha em backends de usuário externo, as senhas
|
||||
específicas do dispositivo são marcadas como inválidas e, depois que um
|
||||
login da conta do usuário com a senha principal ocorrer, todas as senhas
|
||||
específicas do dispositivo serão atualizadas e funcionarão novamente.
|
||||
Para alterações de senha em backends de usuário externo, as senhas
|
||||
específicas do dispositivo são marcadas como inválidas e, depois que um
|
||||
login da conta do usuário com a senha principal ocorrer, todas as senhas
|
||||
específicas do dispositivo serão atualizadas e funcionarão novamente.
|
||||
|
||||
Reference in New Issue
Block a user