Introducción a Auth0
¿Ya tomaste el Curso de Introducción a OAuth 2.0 y OIDC?
¿Qué es Auth0?
¿Qué es Universal Login?
Autenticación rápida con el SDK de Next.js
Conexiones sociales
¿Cómo hacer un login con GitHub?
¿Cómo hacer un login con Twitch?
¿Cómo hacer un login custom con Discord?
Conexiones sin password
¿Cómo implementar el login con SMS?
¿Cómo implementar el login con Email?
Protegiendo una API
¿Cómo usar la Auth0 Management API?
¿Cómo configurar una API en Auth0?
¿Cómo proteger un endpoint?
Auth0 SDKs
Single Page Apps: React SDK
Regular Web Apps: Express SDK
Machine to Machine: Express.js
Administración de usuarios
¿Cómo administrar usuarios?
¿Cómo administrar roles?
Reglas y Acciones en Auth0
¿Qué son las reglas y acciones en Auth0?
¿Cómo implementar una regla?
¿Cómo implementar una acción?
Multifactor Authentication
¿Qué es multifactor authentication?
WebAuthn con FIDO Security Keys
One-time Password
Casos en producción
Actividad y Monitoreo en Auth0
¿Cómo integrar Firebase Auth?
Implementación Firebase Auth: Admin
Implementación Firebase Auth: Rules
¿Quieres más cursos de autenticación?
You don't have access to this class
Keep learning! Join and start boosting your career
Surely you know how easy it is to configure functions such as multifactor authentication or passwordless in Auth0 by simply activating a check. However, have you thought about the integration of Auth0 and Firebase Authentication? Until June 2017, this integration was as simple as one click in Auth0. Due to security issues, it was disabled, making it necessary to perform this process manually. Learn how to build effective code for this complex but fascinating integration.
The Next.js integration is a reference. By using the Next.js SDK, authentication can be implemented with just a few lines of code. We log in with services like GitHub, Auth0 manages the session and we can protect pages, displaying user information. This is possible through the use of ID tokens and access tokens.
A common challenge is the protection of external APIs. Auth0 offered us a solution by establishing an audience, allowing us to obtain specific access tokens to consume those APIs, and, if they are properly signed, access protected resources.
We have used Firebase to access collections such as the movie collection in Firestore, but with completely open initial access rules. While it may seem easy to replicate the external API protection strategy, the Firebase and Auth0 systems operate differently. Firebase has its own authentication solution, with its own user database. However, centralization of the user directory is paramount to avoid multiple databases, which could make maintenance expensive and complicated.
The goal is to connect Auth0 with Firebase without managing users directly in Firebase. This is where Firebase Admin comes in, allowing us to create a more complex flow through an endpoint called createCustomToken
.
The main challenge lies in differentiating between using the Firebase authentication module and accessing Firestore. Be sure to enable these features to maximize the security and functionality of your application.
Maintaining a modular and centralized architecture is crucial. You can use alternatives such as Superbase Auth, which is an open source version of Firebase, and apply an architecture similar to the one shown between Auth0 and Firebase to optimize user management.
Stay motivated! Knowledge is your ally and mastering system integration will boost your application development skills. Keep a focus on security and centralization to build scalable and efficient solutions. In future classes, we will explore practical implementation in more detail.
Contributions 0
Questions 0
Want to see more contributions, questions and answers from the community?