Dpop check failing with nginx as a webserver #17

Activity

1. Potherca commented on Oct 21, 2021

   

   Potherca

   on Oct 21, 2021

   Member

   More actions

   To make sure it doesn't get lost in the noise, I am copy/pasting this relevant comment from #43 here:

   We have managed to log in in our app with nginx using the webid created by your plugin in nexcloud.

   In order to make it work with NGINX:

   • We have added the below to nextcloud.conf

        location = /.well-known/openid-configuration {
          add_header Access-Control-Allow-Origin "*";
          return 302 $scheme://$host:$server_port/apps/solid/openid;
        }
     

   • We also have added with brute force the following to site.conf

         #add_header Access-Control-Allow-Origin https://pr8.io;
         add_header Access-Control-Allow-Origin $http_origin;
         #add_header Access-Control-Allow-Origin http://localhost:3000;
         add_header Access-Control-Allow-Credentials true;
         add_header Access-Control-Allow-Headers "*, allow, authorization, content-type, dpop, slug, link, accept, map";
         add_header Access-Control-Allow-Methods "GET, PUT, POST, OPTIONS, DELETE, PATCH";
         add_header Accept-Patch "application/sparql-update";
         add_header Access-Control-Expose-Headers "Authorization, User, Location, Link, Vary, Last-Modified, ETag, Accept-Patch, Accept-Post, Updates-Via, Allow, WAC-Allow, Content-Length, WWW-Authenticate, MS-Author-Via";
         proxy_pass_request_headers on;
         proxy_no_cache $cookie_nocache $arg_nocache$arg_comment;
         proxy_no_cache $http_pragma $http_authorization;
         proxy_cache_bypass $cookie_nocache $arg_nocache $arg_comment;
         proxy_cache_bypass $http_pragma $http_authorization;
         proxy_set_header HTTP_AUTHORIZATION $http_authorization
     

   Originally posted by @ch1ch0gz in pdsinterop/solid-nextcloud#43 (comment)
2. Potherca

   added this to Solid Serverson Nov 26, 2021
3. ylebre commented on Sep 30, 2022

   

   ylebre

   on Sep 30, 2022

   MemberAuthor

   More actions

   All the CORS headers should no longer be needed in the site configuration, these are now set from the application layer instead of the webserver layer.

   The proxy_set_header for HTTP_AUTHORIZATION should probably still be there.