Such kind of verification would not be necessary for each and every service, it will be shared. That is necessary because of the terms and limitations of projects funding our services like ownCloud. We will only require that you to log in using your academic identity, from time to time, to show you still belong to the community. Social identities will appear in the list of possible institutions during login procedures when this functionality is turned on. That social identity (Google, Facebook) can be then used to sign in to ownCloud, for instance. You will be able to connect any social identity to your academia identity. We are preparing new features in the system. There are several reasons for this complexity. You will be logged in to ownCloud after clicking on the Authorize button. Those attributes are used to verify that you are authorized to use OwnCloud service.ĥ. After logging in you will be redirected to the websites, where you will be asked to express your approval to deliver several attributes required for OwnCloud service. Please select your identity provider and then log in.Ĥ. Now you shall be redirected to the selection list of an identity providers (e.g. At the website click on “Sign In to ownCloud” button.Ģ. Please remove such kind of files from syncing.ġ. Sync of such kind of data using ownCloud doesn't make much sense and overloads both servers as well as clients unnecessarily. Please note that ownCloud service (as well as any other sync'n'share solution) is not suitable for: software source codes kept in versioning systems, e-mails, Windows profile folders, temporary files, database dumps, archives of backup tools and similar data.
0 kommentar(er)
