{"id":16353,"date":"2018-07-25T16:26:30","date_gmt":"2018-07-25T14:26:30","guid":{"rendered":"https:\/\/belvg.com\/blog\/?p=16353"},"modified":"2019-07-18T08:21:17","modified_gmt":"2019-07-18T06:21:17","slug":"api-calls-dont-work-after-updating-magento-to-2-2-5-version","status":"publish","type":"post","link":"https:\/\/belvg.com\/blog\/api-calls-dont-work-after-updating-magento-to-2-2-5-version.html","title":{"rendered":"API Calls Don’t Work After Updating Magento to 2.2.5 Version"},"content":{"rendered":"\n

We have recently updated the Magento platform from version 2.2.3 to 2.2.5 to one of our clients and faced a painstaking issue: every API call return us an error message: `Consumer is not authorized to access %resources`.<\/p>\n

<\/p>\n

The full stack trace of error is:<\/p>\n

{\r\n   \"message\": \"Consumer is not authorized to access %resources\",\r\n   \"parameters\": {\r\n       \"resources\": \"Magento_Sales::sales\"\r\n   },\r\n   \"trace\": \"#0 \/var\/www\/html\/vendor\/magento\/module-webapi\/Controller\/Rest\/RequestValidator.php(68): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\RequestValidator->checkPermissions()\\n#1 \/var\/www\/html\/vendor\/magento\/module-webapi\/Controller\/Rest\/InputParamsResolver.php(86): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\RequestValidator->validate()\\n#2 \/var\/www\/html\/vendor\/magento\/module-webapi\/Controller\/Rest.php(322): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\InputParamsResolver->resolve()\\n#3 \/var\/www\/html\/vendor\/magento\/module-webapi\/Controller\/Rest.php(239): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest->processApiRequest()\\n#4 \/var\/www\/html\/vendor\/magento\/framework\/Interception\/Interceptor.php(58): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest->dispatch(Object(Magento\\\\Framework\\\\App\\\\Request\\\\Http))\\n#5 \/var\/www\/html\/vendor\/magento\/framework\/Interception\/Interceptor.php(138): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\Interceptor->___callParent('dispatch', Array)\\n#6 \/var\/www\/html\/vendor\/magento\/framework\/Interception\/Interceptor.php(153): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\Interceptor->Magento\\\\Framework\\\\Interception\\\\{closure}(Object(Magento\\\\Framework\\\\App\\\\Request\\\\Http))\\n#7 \/var\/www\/html\/generated\/code\/Magento\/Webapi\/Controller\/Rest\/Interceptor.php(39): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\Interceptor->___callPlugins('dispatch', Array, Array)\\n#8 \/var\/www\/html\/vendor\/magento\/framework\/App\/Http.php(135): \r\nMagento\\\\Webapi\\\\Controller\\\\Rest\\\\Interceptor->dispatch(Object(Magento\\\\Framework\\\\App\\\\Request\\\\Http))\\n#9 \/var\/www\/html\/generated\/code\/Magento\/Framework\/App\/Http\/Interceptor.php(24): \r\nMagento\\\\Framework\\\\App\\\\Http->launch()\\n#10 \/var\/www\/html\/vendor\/magento\/framework\/App\/Bootstrap.php(256): \r\nMagento\\\\Framework\\\\App\\\\Http\\\\Interceptor->launch()\\n#11 \/var\/www\/html\/index.php(39): Magento\\\\Framework\\\\App\\\\Bootstrap->run(Object(Magento\\\\Framework\\\\App\\\\Http\\\\Interceptor))\\n#12 {main}\"\r\n}<\/pre>\n
We looked for the solution to this issue on GitHub, but couldn’t find it there, so we began the debugging process. What caused this issue was the method \\Magento\\Webapi\\Model\\Authorization\\TokenUserContext::isTokenExpired.<\/p>\n
<\/a>
\"migration
Migration to Magento 2<\/h3>
Take your online store to the next level with BelVG Magento migration<\/p>Visit the page<\/span><\/a><\/div><\/div><\/div>\n
As soon as we found the cause of the issue we checked this file on a `2.2-develop` branch on GitHub and found a patch<\/a>. After that we found an issue<\/a> on GitHub:<\/p>\n
private function isTokenExpired(Token $token): bool\r\n{\r\nif ($token->getUserType() == UserContextInterface::USER_TYPE_ADMIN) {\r\n   $tokenTtl = $this->oauthHelper->getAdminTokenLifetime();\r\n} elseif ($token->getUserType() == UserContextInterface::USER_TYPE_CUSTOMER) {\r\n   $tokenTtl = $this->oauthHelper->getCustomerTokenLifetime();\r\n} else {\r\n   \/\/ other user-type tokens are considered always valid\r\n   return false;\r\n}\r\nif (empty($tokenTtl)) { \/\/this part should be added\r\n   return false; \/\/to avoid the token issue\r\n}\r\nif ($this->dateTime->strToTime($token->getCreatedAt()) < ($this->date->gmtTimestamp() - $tokenTtl * 3600)) {\r\n   return true;\r\n}\r\nreturn false;\r\n}<\/pre>\n
Since this issue is relevant to the currently available version of Magento (the current version now is 2.2.5), I hope you will find this article helpful.<\/p>\n
<\/a>
Magento Development <\/h3>
Take your online store to the next level with BelVG Magento development<\/p>Visit the page<\/span><\/a><\/div><\/div><\/div>\n
Looking for a reliable partner to migrate your Magento store<\/a> to the newest version? Turn to BelVG!<\/p>\n\n","protected":false},"excerpt":{"rendered":"The API issue that happens after updating Magento to 2.2.5 version","protected":false},"author":12,"featured_media":16356,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"image","meta":{"_acf_changed":false,"footnotes":""},"categories":[491,389],"tags":[],"class_list":["post-16353","post","type-post","status-publish","format-image","has-post-thumbnail","hentry","category-magento-2","category-magento2-development","post_format-post-format-image"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t