All Auth0 Administrators are now required to enroll in MFA.
You can check which tenant you are signed into at the bottom of the Codespaces window. If you are signed into the wrong tenant, click this area and two options will pop up at the top of the window. Simply select Switch tenant and you can select the correct tenant in the tab that opens.
The Labs extension currently only works with public cloud Auth0 tenants registered from Auth0.com. Please ensure you have completed your registration process! If you do not, you will not have a tenant associated with your account and you will receive an Access Denied message when trying to connect to the Labs extension.
Free tier Auth0 accounts created after October 31, 2023 are now limited to one development/staging environment and one production environment. You can use the default tenant (starts with dev-
) for these labs. We always recommend using a fresh development tenant to ensure all configurations are at their defaults. You can register for an additional free tier Auth0 account using a Gmail alias such as username+test@gmail.com (where username@gmail.com is your Gmail address).
If you’ve accidentally closed or lost the CodeTour panel, you can reopen it. Expand the CodeTour section in the right panel of your Codespace and select the step that you completed. The CodeTour panel will reappear.
Sometimes your application won’t launch correctly because you don’t have a configuration set up in a .env
file. The .env
file is created by the Auth0 Labs extension, but it will only be created if you are logged in to the correct tenant (See: I signed into the wrong tenant) and you have named your application exactly as instructed by the lab.
If you already have a .env
correctly configured with the expected values with the correct tenant, you may just need to allow your application more time to launch. You can check the status by going to the Debug Console.
In order to re-run the command that will create the .env
file, open VSCode’s Command Palette (CMD+SHIFT+P on Mac or CTRL+SHIFT+P on Windows), type in Auth0, and select Auth0: Configure Local Environment.
You can then check if the .env
file was successfully created (in src/web-app
for the Web App, src/api
for the API, and src/spa-app
for the SPA app).
This may be due to the Codespaces port-forwarding service being down. You can check GitHub’s Codespace service status here.
You can work around this by opening your Codespace in the VSCode Desktop application (you will need to download VSCode to your local machine if you do not already have it):
CTRL
+SHIFT
+P
(Windows) or CMD
+SHIFT
+P
(Mac)Every once in a while, a Codespace dev container just doesn’t load correctly. In this case, try reloading the Codespace or even deleting the Codespace and creating a new one. If none of these steps help, check GitHub’s status page.
Disconnect from any VPN you may be connected to as it may be blocking certain services Codespaces requires. If this still doesn’t work, see GitHub Codespaces services are blocked on my device / I want to complete the labs locally.
If you cannot access Codespaces from your device, you can complete the labs locally after a bit of setup. You can follow these same steps if you just prefer to complete the labs locally.
Next, you will clone the repo to your local machine and open it in VSCode. If you already know how to do that, please do so now and skip to Step 11.