403 for Anonymous Users Despite Having "access resource restws_resource"

Thanks for the patch!

1. +++ b/restws_resource_discovery.module
   @@ -17,12 +17,17 @@ function restws_resource_discovery_entity_info() {
    
   +function restws_resource_discovery_access() {
   

   Missing doc block.

2. +++ b/restws_resource_discovery.module
   @@ -17,12 +17,17 @@ function restws_resource_discovery_entity_info() {
   +
   

   Extra new line.

Thanks for the update. One nitpick below. I'll try testing.

1. +++ b/restws_resource_discovery.module
   @@ -4,7 +4,6 @@
    function restws_resource_discovery_entity_info() {
   -
      $info = array();
   

   Sorry I wasn't clear. Not this empty line. The line below.

2. +++ b/restws_resource_discovery.module
   @@ -17,12 +16,20 @@ function restws_resource_discovery_entity_info() {
   + */
   +function restws_resource_discovery_access() {
   +  return user_access('access content');
   +}
   +
   +
    /**
   

   Extra line.

Simplytest.me is down so I'll try to test when it's back up.

The patch works for the restws_resource but it does not work for the other types in permissions for example node.

This patch just seems to push the problem down the road. After applying it, I get a whole host of other 403s for basically every content type. Some of these files resolve when pulled directly using the browser, some of them should be 404s

Starting to fetch data from Drupal
...file.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...og_membership_type.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...og_membership.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...rate_limit.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...node.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...taxonomy_vocabulary.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...workbench_moderation_transition.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...cache_fragment.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...redirect.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...user.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...paragraphs_item.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.
...rules_config.json  Request failed with status code 403
Proceeding anyway, but you should ensure you do not need access to this resource.

I'm seeing the same list of errors as the user above; though the patch pretty much takes care of the initial 403 error, there are more errors that ensue. Anyone else trying to use Gatsby with Drupal 7?

I have the same issue when fetching data from gatsby. Is there any workaround?

Not sure why @sokru marked RTBC but putting back to "Needs work" based on comments.

Same problem (yes, also with the purpose of using it with Gatsby via https://github.com/porkloin/gatsby-source-drupal7).

Has anyone found a solution or a workaround?

Same problem as #17, unable to use gatsby with drupal because it is unable to fetch nodes with error code 403

Yep, same here. Also trying to use D7 with Gatsby as described in #17.

Only idea I can think to fix this is migrate site to drupal 9 and hopefully the issue is flushed out, what I am currently in the process of for a site with over 40k nodes