search

otetard / ownpad

Ownpad is a Nextcloud application that allows to create and open Etherpad and Ethercalc documents.
GNU Affero General Public License v3.0
57 stars 24 forks source link

Trouble shooting new API integration Etherpad? #49

Closed poVoq closed 10 months ago

poVoq commented 6 years ago

Ok, I seem to have managed fixing my other issues with enabling the API version of this app, but I can't seem to actually use it with Etherpad and the API.

I have configured my Etherpad to only allow creation of new pads via the API, so that all other requests result in: "You do not have permission to access this pad".

I have also configured Ownpad with the APIKEY and the subdomain of my VPS where Etherpad runs, i.e. Nextcloud runs on mydomain.com, and Etherpad on etherpad.mydomain.com/pad/ (Nginx reverseproxy, different SSL certificate). Thus I put in etherpad.mydomain.com in the Ownpad settings.

Now it seems to be able to communicate with the API fine, as I can create new regular and protected pads in Nextcloud without the cannot connect with API popup that comes if you missconfigure the API key. But when I actually try to open the new pads then I also get the "You do not have permission to access this pad" message in Etherpad.

I guess it is somehow related to the cookie domain setting? Or any other tip for what I might check?

otetard commented 6 years ago

I guess it is somehow related to the cookie domain setting?

If your Nextcloud instance is hosted on example.org and your Etherpad instance is hosted on etherpad.example.org, then you should set example.org for your “Etherpad cookie domain”.

Olivier;

m0urs commented 5 years ago

I see exact the same behaviour. The cookie is set correctly to my domain "urspringer.de" and both Nextcloud and Etherpad are using that domain name.

I can create and access unprotected pads just fine from Owncloud. Protected pads are created in Etherpad but then I have no access rights to access them via Owncloud.

UPDATE:

Ok, sorry. Seems to be an issue with my security settings in my Apache configuration. I have set some HEADER directives and ant least one of these seems to break that thing. I need to investigate more but if I disable all of them, everything works fine!

Please look here: https://github.com/otetard/ownpad/issues/83

otetard commented 10 months ago

I’m closing this issue since this is a very old one. Please open a new issue if you still encounter this issue with the latest version of Ownpad!