Handling of expired access tokens when CF CC rate limiting exhausts

Hi All,

This issue is same as related to one opened on CF CLI

https://github.com/cloudfoundry/cli/issues/1582

CF CC has a rate limit of unauthenticated calls per IP. In our situation some of the CF applications share the same IP due to NAT.

In case of performing operations with expired access tokens from multiple apps we easily reach the unauthenticated rate limit and CF responds with 429.

I checked the code in AbstractReactorOperations

Token is only refreshed when 401 unauthorised is thrown.

It will be helpful we can check the suggestions mentioned the attached bug.

Please let me know if i am missing something or if the same CLI bug does not apply to CF java client.

Best Regards,
Saurav

Beginne damit, cloudfoundry-client-reactor/src/main/java/org/cloudfoundry/reactor/util/AbstractReactorOperations.java zu lesen, und vergleiche dessen Verhalten bei der Token-Erneuerung mit dem zugehörigen CF CLI issue #1582. Ermittle, wie abgelaufene Tokens mit der 429-Antwort von CF CC interagieren, und überprüfe anschließend, dass der Client dieses Szenario behandelt, ohne das Rate-Limit für nicht authentifizierte Anfragen auszuschöpfen.