At Activeloop, ensuring an exceptional user experience is our top priority. Alongside our recent achievement of SOC 2 Type II Compliance, we have another exciting update on the security front. On February 10th 6am PST, we are transitioning to Auth0, a leading authentication and authorization platform. This change will make accessing Activeloop more secure and seamless. It reflects our ongoing commitment to enhancing security and optimizing our services to deliver the best user experience possible.
Will there be any downtime during the migration?
Yes, to facilitate a smooth migration, we’ve scheduled a downtime on February 10th 6am PST for 3 hours. During this period, access to Activeloop will be temporarily unavailable. We appreciate your patience and understanding as we work to improve your experience.
What This Means for You as Our User
The migration to Auth0 involves different processes for our users based on your current method of accessing Activeloop. We’ve designed these processes to be as straightforward as possible, ensuring you can continue to use Activeloop with minimal disruption. Here’s what you need to know.
How will the Auth0 migration affect my current login method?
For Users with Google/GitHub Single Sign-On (SSO)
If you’ve used Google or GitHub SSO to sign up with us, your transition to Auth0 will be automatic, ensuring you can access your account without any extra steps. The first time you encounter the new Auth0 login interface, you can simply proceed with your Google or GitHub account as usual. There’s no additional action required on your part.
For Verified Users Who Signed Up with Email and Password
If you originally signed up with an email and password, you’ll receive an email prompting you to reset your password. Once you’ve reset your password according to the instructions provided, you’ll regain access to your account. Should you attempt to log in before resetting your password, you will encounter a password-related error message.
For Unverified Users Who Signed Up with Email and Password
If your account is not yet verified, we strongly recommend doing that before the downtime. After the transition, you’ll be directed to a linking page. Here, you’ll need to enter your legacy email or username and password. This step does not require SSO, as it’s a part of the verification process. If the email address you provide does not match the email associated with your account, you’ll be prompted to log in to the legacy account that matches that email. For those who may have forgotten their passwords, a legacy password reset link will be available. To ensure maximum security, users who don’t remember their emails will not be able to regain access to their accounts.
Important Update for API Token Users- Legacy API Tokens Will Be Invalidated
As part of our migration to Auth0, all existing (legacy) API tokens will be invalidated. This is a necessary step to ensure that our enhanced security measures extend to all aspects of our platform, including API access. We understand the importance of uninterrupted service and access for our users who rely on Activeloop’s APIs for their projects and workflows.
How to Reissue Your API Tokens?
To continue using Activeloop Deep Lake API services without disruption, please follow these steps to reissue your API tokens under the new system:
Log in to Your Account: After successfully migrating to Auth0, sign in to your Activeloop account using your updated login credentials.
Navigate to the API Section: Once logged in, go to the API section within your account settings. This is where you can manage your API tokens.
Generate a New API Token: Follow the prompts to generate a new API token. Ensure you save this token securely, as it will be required for your API requests. The newly issued API tokens will come with a default validity period of one year. However, during the token generation process, you have the option to adjust this expiry date to meet your specific requirements.
Update Your Applications: Replace the invalidated legacy API tokens in your applications with the newly generated tokens to restore access. We recommend doing this as soon as possible after the migration to avoid any potential interruptions in your work.
Support and Assistance
Should you encounter any difficulties in reissuing your API tokens, or if you have any questions about the process, our support team is here to help. We’re committed to making this transition as smooth as possible and to ensuring that you have the support you need to continue leveraging Activeloop’s capabilities to their fullest.
We appreciate your understanding and cooperation as we upgrade our systems to serve you better. Thank you for being a valued member of the Deep Lake community!
FAQs
What happens if I try to log in and face an error?
If you encounter an error during login, it might be due to the migration process. For verified users with an email and password, ensure you have followed the password reset process from the email sent to you. For unverified users, make sure you complete the steps on the linking page accurately. If problems persist, our support team is here to assist you.
What if my email doesn’t match during the verification process for unverified accounts?
If the email you enter does not match the one associated with your account, you will be prompted to log into the legacy account that has the matching email. This step is crucial for verifying your identity and securing your account. If you have forgotten your credentials, a password reset link will be available to help you regain access.
What should I do if I didn’t receive a password reset email?
First, check your spam or junk mail folder to ensure the email hasn’t been misdirected. If you still cannot find the password reset email, please contact our support team for assistance via live chat. We’ll be glad to assist you.
Who can I contact for help during the migration?
Our support team is available to assist you with any questions or concerns you may have during this transition via livechat or Deep Lake community slack. Don’t hesitate to reach out for help navigating the new system or for any other support you may need.