Given this url:

http://example.com/entity/field_storage_config/node.field_main_workplace?_format=hal_json

and the curl

curl -i -X GET \
   -H "Content-Type:application/hal+json" \
   -H "PHP_AUTH_USER:admin" \
   -H "PHP_AUTH_PW:test" \
   -H "Accept:application/json" \
 'http://example.com/entity/field_storage_config/node.field_main_workplace?_format=hal_json'

I am trying to get the list options dynamically to a second server via rest.
It constantly gives me a 403

Seems like no matter what I do (even testing by giving rest + administer fields access to anonymous), I cannot get anything else than this 403.

Node type request works:

curl -i -X GET \
   -H "Content-Type:application/hal+json" \
   -H "PHP_AUTH_USER:admin" \
   -H "PHP_AUTH_PW:test" \
   -H "Accept:application/json" \
 'http://example.com/entity/node_type/deltaker?_format=hal_json'

Field config request works

curl -i -X GET \
   -H "Content-Type:application/hal+json" \
   -H "PHP_AUTH_USER:admin" \
   -H "PHP_AUTH_PW:test" \
 'http://example.com/entity/field_config/node.deltaker.field_main_workplace?_format=hal_json'

But not field storage config requests. Have I missed some permissions for field_storage_config?

Comments

farald created an issue. See original summary.

farald’s picture

Issue summary: View changes
farald’s picture

Issue summary: View changes
Wim Leers’s picture

Status: Active » Closed (duplicate)
Related issues: +#2300677: JSON:API POST/PATCH support for fully validatable config entities

This is a config entity. Config entities are not yet supported. See #2300677: JSON:API POST/PATCH support for fully validatable config entities.

farald’s picture

Gotcha, thanks for the info!