Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Set the config Parameter "server.federation.login_enabled=true" in the PowerFolder.config file of your server. Restart your server afterwards.
  • Ensure that your server has a valid TLS certificate and can get accessed via httpsHTTPS. http HTTP only is prohibited for security reasons.
  • Ensure that your web ports and your data ports can get reached by the federated servers and their clients.

...

  • Federated proxy accounts can get merged by other accounts, when they add the external mail address to their own account. All future invitations will be handled locally.
  • At the moment for every mail address a proxy account gets created. Even if it is the same user.
  • Permission management is not possible. When inviting a user initially the permission can get set but not changed. Only R/W and Read Only are possible!
  • Deleting permissions on the hosting service doesn't delete the folder on the federated service, but files aren't accessable accessible any longer.
  • When the user on the federated system leaves a folder he is not deleted in the member list on the folder in the hosting system.
  • When a federated service has dynamic folder mounting activated the client might not be possible to connect to the folder of this federated service until a user logs in who has direct access to the folder.
  • The function to show files in web is not working automatically on a federated folder.
  • Adding the services on both sides results in no invitation to accept the mutual trust. Please only add a service on one side and accept it on the other.

...