View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007316 | GraphQL Base | General | public | 2022-03-29 16:42 | 2022-04-06 09:45 |
Reporter | tte | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | v6.0.1 | ||||
Fixed in Version | v6.0.2 | ||||
Summary | 0007316: Internal server error 500 when requesting JWT | ||||
Description | Following the instructions on https://docs.oxid-esales.com/interfaces/graphql/en/6.0/requests.html and https://github.com/OXID-eSales/graphql-base-module I tried to obtain a token for proper authentication: curl \ -X POST \ -H "Content-Type: application/json" \ --data '{"query": "{token(username: \"<my-username>\", password: \"<my-password>\")}"}' \ https://<my-shop-domain>/graphql/ Unfortunately, this results in an internal server error (500) which eventually can be traced back to GraphQL\Language\Visitor::visit:273: $result = call_user_func($visitFn, $node, $key, $parent, $path, $ancestors); <my-username> => OXID account/email with admin rights <my-password> => OXID account password <my-shop-domain> => OXID shop domain Is there something I have to take care of before obtaining the token? In addition, which users are allowed to obtain a token? OXID version: 6.4.1 Regards, Tobias | ||||
Tags | No tags attached. | ||||
|
Hey Tobias, I checked the issue and I could reproduce it by following the current documentation. That's because a version is pulled by composer which isn't released yet. A workaround would be to declare the exact version you want to install by the following command composer require oxid-esales/graphql-base ^6.0.1 Alternative composer require oxid-esales/graphql-storefront ^2.0.0 Since it works with this version (tested it with your provided curl command and with the tool Altair), the issue isn't reproducible in the tagged version. But I will acknowledge this issue, since the documentation needs to be changed. Thank you for bringing this to our attention. Kind regards Michael |
|
Fixed in 6.0.2 base patch. Can now be installed with minimum-stability 'stable' as the upload fork was tagged. |