Allowing ownCloud as a backend - Arkisto-Platform/describo-online GitHub Wiki
The owncloud configuration is in two parts: a ui section and an api section.
If you don't have the ui section then the toggle to use owncloud as a backend will not show in the interface.
Further, since part of the oauth transaction happens on the API and requires a clientSecret the configuration is defined in the api services section.
{
"ui": {
...
"services": {
"owncloud": true
...
}
},
"api": {
....
"services": {
"owncloud": [
{
"name": "{ the name of your owncloud }",
"url": "http://localhost:8000",
"internalUrl": "http://owncloud_server:8080",
"clientId": "{ the client id for this app to use with oauth }",
"clientSecret": "{ the client secret for this app to use with oauth }",
"redirectUri": "http://localhost:9000/owncloud-callback",
"oauthAuthoriseEndpoint": "/index.php/apps/oauth2/authorize",
"oauthTokenEndpoint": "/index.php/apps/oauth2/api/v1/token",
"webdavEndpoint": "/remote.php/dav"
}
]
},
}
}
name: whatever you want,url: the url to owncloud - in development this will be a localhost addressinternalUrl: the url to access owncloud inside the docker network from the API. Leave this blank if talking to a real owncloud instance at a routable addressclientId: the id for this oauth service registration in owncloudclientSecret: the secret for this oauth service registration in owncloudredirectUri: the location of the callback to redirect to - the host here should be the same as the host in theurlpropertyoauthAuthoriseEndpoint: the endpoint to authorize an oauth transactionoauthTokenEndpoint: the endpoint the API will interact with to exchange an oauth code for an access_tokenwebdavEndpoint: the webdav endpoint for file interaction