This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Inconsistent behaviour of access token

Posted on 01-25-2021 03:51 AM
abhishekjha
New Member
Reply posted on --/--/---- --:-- AM

Hi Apigee Support Team,

We are facing an issue while calling the Api proxy. There are three proxies exposed. 2 proxies are working fine , returning 200 response, but the third one is returning 401 Unauthorized error using the same access token. Scope is same for all the proxies. This is on Prod env.

It is incosistent behaviour. After some time the same token works fine.

By looking at the Apigee Analytics it failed due to policy VerifyAccessTokenOpenid violation.

ax_edge_execution_fault_code | keymanagement.service.invalid_access_token

ax_execution_fault_policy_name | Global.VerifyAccessTokenOpenid

Could you please help us on this.

0 1 214
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
dchiesa1
Staff
Reply posted on --/--/---- --:-- AM

Is this reproducible ?

Does it happen with every new token you issue?

What version of Apigee are you using?

Have you checked the obvious, that the 3rd proxy is included in the API Product?

What happens if you create a a different API product and add those same 3 proxies into the product? If you issue new tokens for that API Product, ... do the newly issued tokens (authorized on the newly created product) behave in the same manner?

0 Likes