-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test with Solid bot example #76
Comments
First one: https://test.server.com/.well-known/openid-configuration redirects to https://test.server.com/apps/solid/openid with a 302 and https://www.npmjs.com/package/openid-client doesn't like that. It wants a 200 response directly. |
According to the openid spec Redirects are allowed in the webfinger part of discovering someone's issuer: but we're not allowed to do a redirect in the provider configuration response: |
The 302 is coming from https://github.com/pdsinterop/solid-nextcloud/blob/531f6c4/init-live.sh#L6 |
If I change -sed -i '96 i\ RewriteRule ^\\.well-known/openid-configuration /apps/solid/openid [R=302,L]' /var/www/html/.htaccess
+sed -i '96 i\ RewriteRule ^\\.well-known/openid-configuration /apps/solid/openid [PT]' /var/www/html/.htaccess I get a 404 instead of a 302, with a body |
Hm, none of the flag combinations I tried seem to work, even though https://httpd.apache.org/docs/2.4/rewrite/flags.html seems to say it should just work the same way, but with passthrough or proxy instead of redirect. Will try with https://github.com/pdsinterop/solid-nextcloud/tree/test-server-24 now. |
That fixed it! :) Next error:
|
Fixed in the test-server-24 branch. Next error: |
The web console shows:
|
It does work correctly when I try to log in to https://noeldemartin.github.io/media-kraken/ with my test server. |
Hm, I put the bot example on http://test.server.com:3000 but that didn't help either. Maybe Nextcloud wants the redirect to be https? |
@ylebre any idea? (I sent you the test server URL and credentials via Slack) |
I saw in the database that it does set the client id to the domain with https, so i'll try if i can get my bot example working if i deploy it to Heroku |
Hm, same error when trying to log in to https://solid-bot-example.herokuapp.com/login :( |
I'm trying to use https://github.com/michielbdejong/solid-bot-example
in combination with https://github.com/pdsinterop/solid-nextcloud/blob/main/setup-test-server.sh and debuggin g the errors I run into.
The text was updated successfully, but these errors were encountered: