io.net CTO: Rate limit by third-party authentication provider Okta may cause connection failure

Gaurav, CTO io.net Solana Ecosystem DePIN Protocol, said in an X post, "The Auth0 process of Okta, a third-party authentication provider on the worker node, is experiencing problems because the io.net reaches the rate limit on the Okta side, resulting in limited authentication rates. Some devices may experience problems accessing the API and experience potential connection failures. Suspected malicious users may impersonate io.net and attack Okta, which in turn affects io.net authentication solution. io.net are actively working with Okta to resolve this issue and prevent such incidents from happening again in the future, and will share more updates in the future."