pdsinterop / solid-nextcloud

A plugin to make Nextcloud compatible with Solid
https://pdsinterop.org/solid-nextcloud/
MIT License
72 stars 11 forks source link

authentication not working against pod with webid on many applications- nextcloud:25.0.9-fpm / solid app 0.7.2 #131

Closed dounoit closed 10 months ago

dounoit commented 1 year ago

I just did a fresh install of nextcloud via docker - its a pretty vanilla setup using Version

Nextcloud Hub 3 (25.0.9) - i read the plugin was in "experimental" status for later versions of NC.

specifically the image im using is: image: nextcloud:25.0.9-fpm

image

we got the regular webid: https://trident-uat.holosailapps.io/apps/solid/@holoapps-admin/profile/card#me

image

when i start with the app - https://notepod.vincenttunru.com/

image

while penny https://penny.vincenttunru.com/explore/?url=https%3A%2F%2Ftrident-uat.holosailapps.io%2Fapps%2Fsolid%2F%40holoapps-admin%2Fprofile%2Fcard%23me shows me:

image

when i try to connect to the pod - i receive this - perhaps im not using the right address - i'll try it with two different ones:

https://trident-uat.holosailapps.io/apps/solid/@holoapps-admin/profile/card#me:

image

and https://trident-uat.holosailapps.io image

wow - i just refreshed penny and it redirected me successfully somehow to login: image

of course - that's the first time its worked!


on to lqid.chat - i know there may be some issues with some of these apps and how they interface with pod servers with spec updates etc

https://liqid.chat redirects me to add it to the allow apps list in nextcloud which is cool :-) on redirect back to the app i get this: image image

just tried to login to liqid.chat again and got the same - theres an entry in the web log: image

i noticed the .well-known/openid-confiiguration - 301 - i'm not sure of this mechanism or if this is something with the nginx config or if there is something in the solid pod profile that needs to be in place to work properly? like a functional skeleton of permissions or something?

proxy_1 | 44.192.71.208 - - [22/Jul/2023:03:11:12 +0000] "GET /.well-known/openid-configuration HTTP/1.1" 301 162 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" "-"


ok - this is another error i get on some apps - in this case: https://solidos.solidcommunity.net/public/ when i try to login on the top right - i'm challenged to select an identity provider and i get an error about no registration endpoint: webid: https://trident-uat.holosailapps.io/apps/solid/@holoapps-admin/profile/card#me image

looks like the error in the log is a 404? proxy_1 | 102.165.16.44 - - [22/Jul/2023:03:18:02 +0000] "GET /apps/solid/@holoapps-admin/profile/.well-known/openid-configuration HTTP/2.0" 404 11 "https://solidos.solidcommunity.net/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0" "-"


and another: image


unleash the kraken - cool when works on nss: https://noeldemartin.github.io/media-kraken/login image

i tried with the shortened pod server url instead of full webid: https://trident-uat.holosailapps.io with and without a tailing "/" image


app: https://ohmypod.netlify.app/login

i get: image


app: https://otto-aa.github.io/solid-filemanager/ image


app: https://scenaristeur.github.io/solid-vue-panes/ info: it just looks like its getting an error 301 when it tries to use the pop-up challenge to login to the pod - im not sure where to dig further into that one - is it an nginx config? nextcloud? the soliid plugin? I am using the latest nginx config from nextcloud for this build - it appears to take care of the finger / webdav urls - so i'm kinda stumped :-/

image


app: https://bourgeoa.solidcommunity.net/public/solid-file-widget/ image


app: https://vincenttunru.gitlab.io/poddit/

image


app: https://thewebalyst.solidcommunity.net/plume/#

image


app: https://oxfordhcc.github.io/solid-media/login?redirect=%2Fsolid-media%2F

image


app: https://gca-solid.vercel.app/login

image


app: https://linkeddata.github.io/profile-editor/#/profile/edit?webid=https:%2F%2Ftrident-uat.holosailapps.io%2Fapps%2Fsolid%2F@holoapps-admin%2Fprofile%2Fcard%23me

image

i was able to make some updates to first / last / nick

image

and phone number: image

now when i view the profile - it shows the changes like its supposed to :-) app: https://linkeddata.github.io/profile-editor/#/profile/view?webid=https:%2F%2Ftrident-uat.holosailapps.io%2Fapps%2Fsolid%2F@holoapps-admin%2Fprofile%2Fcard%23me

image


now back to NC - i see the solid folder has shown up: image

image

the only files i have in here are: image


I'm going to continue testing apps and see if it "populates" my pod with whatever metadata it may be looking for - i know one worked - it was a profile editor or something - i noticed you don't get a solid directory until you use certain apps for authentication / access - then it creates one for you with assets in it. I'm still learning about the profile structure etc and how its laid out.

its good to note - i'm also running an NSS server on another server url - i set that up so i can begin working on some other apps we want to deploy - its also helping me look n learn about the solid pod directory structures - id prefer to use nextcloud ultimately as our pod server for users. if you have any help or pointers for troubleshooting - id be truly grateful my friend :-)

dounoit commented 1 year ago

is there anything that pops out as a "no brainer" that i've missed? thanks! -daveK

michielbdejong commented 1 year ago

Hi! Thanks a lot for the detailed screenshots, and sorry for not getting to the issue earlier!

I'm now troubleshooting a similar, possibly related issue, will get back here once I have that working and see what else might be missing from your setup. -> https://github.com/pdsinterop/solid-nextcloud/issues/132

It feels like we should set up a tester tool which we can include in the Solid test suite somehow so that we don't have to be looking at screenshots and web console logs! -> https://github.com/solid-contrib/test-suite/issues/161

ylebre commented 12 months ago

I've started work on mitigating this issue in this PR: https://github.com/pdsinterop/solid-nextcloud/pull/140 - these changes allow the use of both poddit and notepod.

They are both pre-dpop implementations, which is the reason it was not working before. I had hoped that these applications would be updated to the newer state of the spec, but alas. From what I've seen so far, it seems like a good idea to have futher backwards compatibility in our implementation so we can play nice with more of the earlier applications.

ylebre commented 10 months ago

We've just finished releasing 0.8.1 that addresses a lot of these issues. It would help a lot if you are able to verify that this reduces the number of problematic apps. If any of them are still not working as expected, could you open separate issues for them so we can take a more specific look at them?

dounoit commented 9 months ago

I sure will check it out! thanks for your help friend! :-)

-daveD

On Friday 19 January 2024 08:18:18 AM (-05:00), Yvo Brevoort wrote:

We've just finished releasing 0.8.1 that addresses a lot of these issues. It would help a lot if you are able to verify that this reduces the number of problematic apps. If any of them are still not working as expected, could you open separate issues for them so we can take a more specific look at them?

— Reply to this email directly, view it on GitHub https://github.com/pdsinterop/solid-nextcloud/issues/131#issuecomment-1900413191 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJSIEIYI6IYH7GGDUL2Z5LYPJXBVAVCNFSM6AAAAAA2TSQSM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBQGQYTGMJZGE . You are receiving this because you authored the thread.

-- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com