Cloud plugin (OwnCloud/NextCloud)

Descriptive title for this contribution

Cloud plugin (OwnCloud/NextCloud)

Step by step description of this contribution

The cloud plugin would allow to add a cloud quota attribute to a user, like we have a mail quota attribute

Schemas needed by this contribution

Proposed schema:

##
## cloud-fd.schema - Fusion Directory cloud plugin
##

# Attributes
attributetype ( 1.3.6.1.4.1.38414.80.1.1 NAME 'fdCloudQuota'
  DESC 'FusionDirectory - template field'
  EQUALITY caseIgnoreMatch
  SUBSTR caseIgnoreSubstringsMatch
  SYNTAX  1.3.6.1.4.1.1466.115.121.1.15)

# Objectclasses
objectclass (1.3.6.1.4.1.38414.80.2.1 NAME 'fdCloud'
  DESC 'FusionDirectory - cloud tab'
  MUST ( )
  MAY ( fdCloudQuota ) )

Benefits

Quota management for OwnCloud/NextCloud

Possible Drawbacks

There is already a plugin for SeaFile, but much more complex: https://github.com/gallak/fusiondirectory-plugins-seafile

I think both plugins can be useful

Actual use cases

Will be used in W'Sweet (https://www.wsweet.org)

added plugin-cloud label

assigned to @bmortier

added PJ1802-0188 label

hello @coudot,

• could you share the link to the owncloud/netcloud documentation about quota
• Could you put into schema what this field is for ex: quota size in mb for example
• Is this the only value interesting in the case of quota management
• Could you provide the code for the user tab

Cheers

could you share the link to the owncloud/netcloud documentation about quota

https://docs.nextcloud.com/server/18/admin_manual/configuration_user/user_auth_ldap.html#special-attributes

Could you put into schema what this field is for ex: quota size in mb for example

You mean in attribute description?

Is this the only value interesting in the case of quota management

Maybe we can also add an attribute for "User Home Folder Naming Rule"

Could you provide the code for the user tab

Yes, will be done

@coudot,

• After reading the doc i think we should support the 4 entries.
• In Fusiondirectory we have a rule that a plugin should have a 1:1 meaning with a software so i would be in favor of naming it Nextcloud.
• that we it can be expanded later if other ldap attributes specific to Nextcloud are needed

added 10m of time spent at 2020-05-15

added 10m of time spent at 2020-05-15

I you read carefully the documentation,you will see there is no need of specific attributes for all options:

• Quota Default: not read in LDAP, default value set on nextcloud side
• Email Field: settings on nextcloud side

I can call it NextCloud if you want, but this also works for OwnCloud

I you read carefully the documentation,you will see there is no need of specific attributes for all options:

• Quota Default: not read in LDAP, default value set on nextcloud side

ok

• Email Field: settings on nextcloud side

Yes but can be read from ldap, so it sould be included

I can call it NextCloud if you want, but this also works for OwnCloud

yes i just checked the owncloud documentation and its the same interface. my first idea its that we will put a note in our official documentation about it

Cheers

• Email Field: settings on nextcloud side

Yes but can be read from ldap, so it sould be included

My understanding of the documentation is that you put here the name of the LDAP attribute containing the mail that should be used by NextCloud. Could be used to set gosaMailAlternateAddress for example. I don't see the need to create a new email attribute just for NextCloud, but if you want to add it, I'll do it.

@coudot,

yes from what i understand you store there the attribute that need to be used by Nextcloud as the email address of the user directly from ldap, I don't know the usage exactly but i think we can provide the option.

Cheers

We don't really understand the same thing.

This option in NextCloud is used to set the name of an LDAP attribute which contains the email. I don't see the need to create a new attribute in user entry to store an email, we already have other attributes in FD for this.

Do you really want to add a new email attribute?

the way i understand it is: it allows to tell Nextcloud in which attribute is the email address of your user stored.

So this field in your plugin should be used to store the ldap attribute name that is storing the email of the user if its not in a classical one, think about the various attributes in the supann schema for example.

SupannMailPerso, SupannAutreMail etc

Yes, but NextCloud will not read this setting into LDAP, there is no need to add an attribute for this.

The plugin will just contains attributes that can be used by NextCloud, like quota, or the document path. These are not configuration settings, these are data.

haa ok i finally got it :)

Cheers

added 10m of time spent at 2020-05-15

added 5m of time spent at 2020-05-15

added 5m of time spent at 2020-05-15

added 5m of time spent at 2020-05-15

Hi,

I created a branch here: https://gitlab.fusiondirectory.org/coudot/fd-plugins/-/tree/issue-6053-cloud-plugin

OpenLDAP schema: https://gitlab.fusiondirectory.org/coudot/fd-plugins/-/blob/issue-6053-cloud-plugin/nextcloud/contrib/openldap/nextcloud-fd.schema

Plugin class: https://gitlab.fusiondirectory.org/coudot/fd-plugins/-/blob/issue-6053-cloud-plugin/nextcloud/personal/nextcloud/class_nextcloudAccount.inc

For the moment, nothing appears on the interface. Could you tell me what is missing?

Most likely you forgot to run fusiondirectory-setup --update-cache.

If I run this I get a crash because of the syntax error in plInfo. Then I get an LDAP error when saving the tab because the objectClass is structural instead of auxiliary.

I added my comments on both commits:

• coudot/fd-plugins@e3892321
• coudot/fd-plugins@ca81b6c9

Thanks a lot, I will look into it.

I also reserved the number 80 for the schema: https://fusiondirectory-developer-documentation.readthedocs.io/en/1.4/schemas/numberrules.html#attribution

Hello @MCMic

I updated my code thanks to your remarks. Plugin is now working well on my side.

Could you tell me what would be missing before I create a merge request? Maybe translations? Documentation?

@coudot,

you can add a locale/en directory like show here

https://fusiondirectory-developer-documentation.readthedocs.io/en/1.4/coding/sourcecode.html?highlight=locale#file-hierarchy-system

clone https://gitlab.fusiondirectory.org/fusiondirectory/dev-tools

and run fusiondirectory-update-locale -g

inside your plugin

Cheers

@coudot,

for the documentation we use rst format and its done in https://gitlab.fusiondirectory.org/fusiondirectory/user-manual

you put your plugin manual into a subdirectory of /source/plugins and update the index.rst in plugin to add your plugin in the index

all the plugin are described in the same way you can look at an plugin to see how to format your documentation

Cheers

Ok, so documentation needs a different merge request, as it is stored in another project. Thanks.

added 10m of time spent at 2020-05-20

mentioned in issue #6057 (closed)

added 10m of time spent at 2020-05-20

assigned to @coudot and unassigned @bmortier