Setup and integration manual

Integration of the Nextcloud Directory service is very similar to integration of the Directory Content service. There are two differences:

Login :

Lorsque l'utilisateur n'est pas connecté à Nextcloud, seule une balise <not-connected> est généré. Afin d'afficher un bouton de connexion, un helper est fournis par le plugin. Importer le fichier service:nextcloud://stylesheets/helper.xsl pour les utiliser.

You then have the choice of using the connect-button template, which takes auri prefix, a CSS class and a i18n key as parameters for adding a button, or using the connect-action template, which supplies only the JS to be added as the onclick action of your own button.

<xsl:when test="/not-connected">
    <xsl:call-template name="connect-button">
        <xsl:with-param name="uri-prefix" select="$uri-prefix"/>
    </xsl:call-template>
</xsl:when>

<xsl:when test="/not-connected">
    <xsl:call-template name="connect-button">
        <xsl:with-param name="uri-prefix" select="$uri-prefix"/>
    </xsl:call-template>
</xsl:when>

<xsl:when test="/not-connected">
    <xsl:call-template name="connect-button">
        <xsl:with-param name="uri-prefix" select="$uri-prefix"/>
    </xsl:call-template>
</xsl:when>

URL resource :

Nextcloud resources don't have a Ametys identifier and therefore can't be resolved using the resolver. Instead, resource nodes directly carry a href attribute pointing to their URL in the Nextcloud application.