1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
0
Hello, and thanks for reaching out!
So, the key things going on with how the auth token is being handled has to do with:
- The lack of an auto-refresh mechanism upon each invocation with regard to the auth tokens being used by the API Destination Connector and
- The HTTP 403 response received from your API for the requests using the expired token.
EventBridge documentation will point out that among others, no 4XX error codes other than 429 are retried.
However, this has a slight caveat to it, in that in the event of an expired auth token, an HTTP response of 401 or 407 will result in a retry process in which the token will be refreshed.
UPDATE: Information regarding 401 and 407 responses refreshing OAUTH tokens has now been updated in AWS Documentation
With this in mind, you can modify the response given by your API to either 401 or 407 instead of 403 in the event of an expired auth token, and this should enable the token refresh process.
Conteúdo relevante
- AWS OFICIALAtualizada há 8 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há um ano