We have a scenario where in we have enabled ExternalAuthorization true and storing the token in Apigee.
So we are hitting a backend getting back the cookie value , and storing that.
When I am trying to retive the token via management call I am getting below error.
{ "code": "keymanagement.service.AccessTokenDoesntExists", "message": "Access Token doesnt exists", "contexts": [] }
Curl call is as below :
curl -X GET -H "Authorization: Basic username:password" -H "Cache-Control: no-cache" -H "Postman-Token: c0935c0a-62cb-f106-6d80-adcec43fc87f" "https://api.enterprise.apigee.com/v1/organizations/tmobileqat/oauth2/accesstokens/ehT%2Bxg8AFKdCLpqR..."
If I am doing a verification of the token using verify access token , the token gets validated and returns the attribute .
Hello @akshay.anand9
I observed the same behavior.
However, I was able to successfully delete the token that I created.
curl -X GET --header "Authorization: Basic" "https://api.enterprise.apigee.com/v1/organizations/myorg/oauth2/accesstokens/1234567"
I was also able to approve and revoke the token.
curl -X POST --header "Content-Type: application/octet-stream" --header "Authorization: Basic" "https://api.enterprise.apigee.com/v1/organizations/myorg/oauth2/accesstokens/1234567?action=approve"
When I approve the token or revoke it, then I was able to retrieve it with the GET request.
It seems unusual that the GET request does not work when the token is first minted. I'm checking on this behavior.
User | Count |
---|---|
7 | |
2 | |
2 | |
1 | |
1 |