You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we just encountered a situation where the API told us, that the access_token is not a valid AddressConstenToken.
The cause was that we extracted the value with $_REQUEST['access_token'] and simply passed it on to the call.
The format was ATza%7d... instead of Atza|..., so the call failed. A urldecode solved the problem.
Could you please add a check, so that the value can be passed in and the SDK takes care about the rest?
Best wishes
Daniel
The text was updated successfully, but these errors were encountered:
hi Daniel
the code in the lines below should have worked. i URL decode the access token and encode it again as that is the required manner in which the access token has to be sent. I will also double verify and check this by sending the accesstoken both ways (Atza% & Atza |)
// To make sure double encoding doesn't occur decode first and encode again.
$accessToken = urldecode($accessToken);
$url = $this->profileEndpoint . '/auth/o2/tokeninfo?access_token=' . urlEncode($accessToken);
Hi Shravan,
we just encountered a situation where the API told us, that the access_token is not a valid AddressConstenToken.
The cause was that we extracted the value with $_REQUEST['access_token'] and simply passed it on to the call.
The format was ATza%7d... instead of Atza|..., so the call failed. A urldecode solved the problem.
Could you please add a check, so that the value can be passed in and the SDK takes care about the rest?
Best wishes
Daniel
The text was updated successfully, but these errors were encountered: