psn-php: Client does not have grant type: 'authorization_code'

Client does not have grant type: 'authorization_code'

This error comes up when trying to login with an npsso. Is that something new?

Btw. that error from the API also triggers an uncaught ApiException:

Fatal error: Uncaught Tustin\Haste\Exception\ApiException in /project/vendor/tustin/haste/src/Http/Middleware/ResponseHandlerMiddleware.php:59 Stack trace: #0 /project/vendor/tustin/haste/src/Http/Middleware/ResponseHandlerMiddleware.php(32): Tustin\Haste\Http\Middleware\ResponseHandlerMiddleware->handleErrorResponse(Object(GuzzleHttp\Psr7\Response), Object(Tustin\Haste\Http\JsonStream)) #1 /project/vendor/guzzlehttp/promises/src/FulfilledPromise.php(41): Tustin\Haste\Http\Middleware\ResponseHandlerMiddleware->__invoke(Object(GuzzleHttp\Psr7\Response)) #2 /project/vendor/guzzlehttp/promises/src/TaskQueue.php(48): GuzzleHttp\Promise\FulfilledPromise::GuzzleHttp\Promise\{closure}() #3 /project/vendor/guzzlehttp/promises/src/Promise.php(248): GuzzleHttp\Promise\TaskQueue->run(true) #4 /project/vendor/guzzlehttp/promises/src/Promise.php(224): GuzzleHttp\Promise in /project/vendor/tustin/haste/src/Http/Middleware/ResponseHandlerMiddleware.php on line 59

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 39 (8 by maintainers)

Commits related to this issue

Most upvoted comments

Thanks @Ragowit and @andshrew for the solution! Seems to be fine now – I’ve pushed it to master and will draft a release for PHP <8.1 version, along with a new version that works for PHP 8.1 🥳

Experiencing the same issue. I’ll try to dig a bit further, must be a recent change since everything was working fine until this morning.

Perfect. Many thanks once again !

@Tustin Awesome, thank you! Can you also release a 3.0.4 when you get the chance please? 😃

Should be good to go now 😃 Let me know if there’s any other issues!

Hi, I’m working on a Laravel and after setting de Npsso it returns an exception error, I think a bad request 400. It is possible that is the same thing and they changed something on the API?

Thanks.

@wescopeland Link is working now. I just was logged in and didn’t understand

@wescopeland I see similar behaviour. I can spot the following as a response:

  body: "{\"error\":\"invalid_scope\",\"error_code\":4153,\"error_description\":\"Invalid scope\"}",

Looking into it further.