You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

OCI Token Caching

Gemeente Rotterdam

We recently transitioned our Oracle Integration Cloud (OIC) to use Fusion connection with JWT User Assertion, replacing our previous OAuth Authorization Code flow. Since making this change, we've encountered "Too Many Requests" errors, particularly in integrations where Fusion is called within a large iteration.

We raised a Service Request (SR) to investigate this issue. The outcome indicated that JWT tokens are used more frequently at token expiration compared to the OAuth Authorization Code flow. This is due to the fact that the Authorization Code flow involves an additional middle step that first authorizes the request (based on ID and Secret) before obtaining the access token. In contrast, the JWT flow directly fetches the access token. As a result, during peak usage times, OIC’s caching mechanism may not always be able to manage the token expiration effectively, leading to rate-limiting issues.

Tagged:
1 votes

Submitted · Last Updated

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!