Agilix Learning Suite Release Notes

Login, Login2, and Login3 authenticate users with a Buzz username and password and return a session token for subsequent API requests. Although Login and Login2 were deprecated previously, all three commands currently remain functional. Beginning in September 2027, they will no longer support API authentication.

Learn more about Login3

To improve security for your users, domain owners should encourage administrators and teachers to configure MFA on their accounts now.

If you don’t have automated integrations that authenticate to the API, make a plan to start enforcing MFA for administrators in your domain as soon as possible.

If you have automated integrations that use Login, Login2, or Login3, migrate them to OAuth as soon as possible. Integrations that continue using username/password authentication beyond September 2027 will stop working after the change.

OAuth authentication is designed to support automated API processes while improving long-term security and alignment with stronger account protection options.

Adopting this model as soon as possible will give you improved security and performance and allow you to enforce MFA for admin accounts.

Learn more: OAuth 2.0 Application Identity

In order to support adoption of the faster and more secure model, we have published complete, runnable code samples in 7 languages that use OAuth to call the Buzz API: Sample Code - xLi

• OAuth is 3x faster than Login3 and satisfies MFA requirements.
• The samples properly handle retry with exponential backoff.