io.net CTO: Reaching the rate limit of third-party authentication provider Okta may cause connection failure

According to BlockBeats, on May 3, Gaurav_IO, CTO of Solana ecosystem DePIN protocol io.net, posted on social media that “The Auth0 process of third-party authentication provider Okta on the working 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 encounter potential connection failures. It is suspected that malicious users may impersonate io.net and attack Okta, thereby affecting 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. More updates will be shared later.”