<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y0000AYo9cuSQBOkta Classic EngineAdministrationAnswered2021-09-07T13:26:27.000Z2021-02-26T09:12:15.000Z2021-02-26T09:13:21.000Z

AshwiniM.34323 (Customer) asked a question.

How to find cause of rate limit warning raised by Okta System (SystemPrincipal)?

A lot of times we are getting rate limit warning where actor is Okta System  (SystemPrincipal). It is mostly for target -

Target (id: /oauth2/{authorizationServerId}/v1) URL Pattern.

 

Is there a way to find out the causes for it? Or is it safe to assume that the no of calls to the specified url exceeded the limit for that minute?


  • AshwiniM.34323 (Customer)

    Also, it does have client information in the logs, which differs every time, naturally may be indicating the initiator?

This question is closed.
Loading
How to find cause of rate limit warning raised by Okta System (SystemPrincipal)?