io.net CTO: Encountering rate limits from third-party authentication provider Okta may cause connection failures

io.net CTO Gaurav_IO posted on X Platform that the Auth0 process of the third-party authentication provider Okta on the worker node encountered problems because io.net reached the rate limit on the Okta side, resulting in a limited authentication rate. Some devices may encounter problems when accessing the API and experience potential connection failures. Malicious users may attack Okta, which in turn affects the io.net authentication solution. io.net is actively working with Okta to resolve this issue and prevent such incidents from happening again in the future, and will share more updates later.