DEV Community: Jessica Temporal

Go watch it =)

Jessica Temporal — Fri, 28 Aug 2026 15:53:48 +0000

Carla Urrea Stabile for Auth0 for Developers

Aug 27

"You Don't Need to Read the Code Anymore"

#ai #programming #python #security

2 min read

Undo anything in Git: reset vs revert, explained

Jessica Temporal — Wed, 26 Aug 2026 10:30:00 +0000

Made a mess in Git? You can undo almost anything, and I'll show you how.

In this video:

git reset and its three flavors (soft/default/hard)
reset vs revert, and which to use when
git reflog to recover "lost" commits
git commit --amend comes in around

Resources:

🛠️ Gear I use

Mic
Camera (As an Amazon Associate I earn from qualifying purchases.)

👋 Let's connect
Blog • X/Twitter • LinkedIn • Bluesky

Federated Identity vs Single Sign-On (SSO) | Stop Confusing IAM Architecture

Jessica Temporal — Mon, 24 Aug 2026 13:00:00 +0000

Are you confused about the difference between Federated Identity and Single Sign-On (SSO)? You’re not alone. While both deal with authentication and access control, they solve fundamentally different architectural challenges.

In this video, we break down Federated Identity vs. SSO with real-world developer examples, protocol overviews (SAML, OAuth, OIDC), and clear diagrams so you can design secure identity systems with confidence.

💡 What You'll Learn

The core technical definitions of SSO and Federated Identity
Key differences: Single domain vs. Cross-domain trust relationships
How identity providers (IdPs) operate across enterprise boundaries
Real-world protocols: SAML, OpenID Connect (OIDC), and OAuth 2.0
When to implement SSO vs. when you actually need Federation

Read the full blog post by Andrea Chiarelli here

We Let AI Resurrect a 2-Year-Old Flask Python App (Cursor + Auth0)

Jessica Temporal — Mon, 17 Aug 2026 13:00:00 +0000

Updating old codebases usually means hours of re-configuring environments, fixing broken dependencies, and hunting for lost secrets. In this walkthrough, we use Cursor IDE and the new Auth0 plugin to automatically resurrect a 2-year-old Python Flask application. Watch how AI seamlessly sets up the Auth0 CLI, generates environment variables, and configures our authentication tenant from scratch.

What You'll Learn

How to install and navigate the Auth0 plugin within Cursor IDE.
Using AI prompts to automate Auth0 tenant creation and Flask secret key generation.
Navigating the Auth0 CLI device authorization code flow inside an AI environment.
Troubleshooting AI prompt timeouts and natively restarting development servers via Cursor.

Resources & Links

How to Give Claude Real-Time Auth0 Docs Access (MCP Server)

Jessica Temporal — Mon, 10 Aug 2026 13:00:00 +0000

Stop relying on outdated LLM training data or incomplete web scrapes when writing identity code. In this video, we walk through how to add Auth0 documentation MCP (Model Context Protocol) servers directly to your setup, giving Claude Code real-time access to the Auth0 documentation.

We walk through adding both the "Auth0 for AI Agents" documentation server and the "General Auth0 Documentation" server, verifying their connections, and putting them to the test with real-world prompt scenarios like human-in-the-loop consent and Auth Code vs. Client Credentials flows.

🚀 What You'll Learn

The problem with generic LLM training data for precise identity management.
How to add the Auth0 for AI Agents documentation server for protected agent architectures.
How to add the General Auth0 documentation server for quick access to SDKs and flows.
Verifying and listing active MCP servers within Claude Code.
Real-world prompt testing (CIBA/Backchannel authentication and flow comparison).

🔗 Related Videos and Playlists

Recovering lost commits with git reflog

Jessica Temporal — Sat, 20 Jun 2026 12:00:00 +0000

There is a particular kind of panic that hits when a commit looks like it just vanished. Maybe you ran a hard reset, or a rebase went sideways, and the work you had a minute ago is nowhere in your history. Before you assume it is gone for good, there is one command that may be able to bring it back: git reflog.

What is the reflog?

Git keeps a private log of everywhere HEAD has been. Everything you do in Git that moves the HEAD pointer is recorded, whether you made a commit, did a checkout, ran a reset, or a rebase or merge moved it around.

The log of that movement lives in the reference log (reflog for short), and it is local to your machine. So even when a commit no longer shows up when you do git log, the reference to it usually still lives in the reflog.

Finding the commit you lost

To see the reference log you can run the command below:

git reflog

You get a list of recent moves, with the most recent entry at the top, like shown in the following image.

Each line has a short hash, a reference like HEAD@{2}, and a description of what happened, things like “commit”, “reset: moving to”, or “checkout”.

Even though it may be hard to get used to reading this new format of log, the description and order usually make it clear where you were and can be the indication you need to know where you want to go.

Getting back to it

Once you have spotted the right entry, copy its hash. Then move your branch back to that point:

git reset --hard <hash>

Replace <hash> with the hash you found in the reflog.

For example, thinking of the image above, if you want to go to the state before the reset you’d need to run the following:

git reset --hard a68cffa

And after that, your working state matches the moment before the mistake, like it never happened.

A quick note of caution: git reset --hard discards your current uncommitted changes, so make sure you actually want to land on that older state before you run it. If you are not sure, you can use git switch to the hash first to look around without moving your branch.

Recap

Most people learn about the reflog the hard way after losing the work to a reset or a rebase, so knowing it exists can be extremely helpful in a pinch.

Here’s a recap of the steps to restore a previous lost state with reflog:

Find the state you want to go back to, and copy its hash.
Check if that’s the actual state you want to restore with git switch <hash>. If it’s not, repeat steps 1 and 2 until you find the correct state.
Run git reset --hard <hash> to get back to it.

Recuperando commits perdidos com git reflog

Jessica Temporal — Sat, 20 Jun 2026 11:00:00 +0000

Tem um tipo específico de pânico que bate quando parece que um commit simplesmente sumiu. Talvez você tenha rodado um hard reset, ou um rebase deu errado, e o trabalho que estava aí um minuto atrás não aparece em lugar nenhum do seu histórico. Antes de assumir que ele foi embora para sempre, tem um comando que pode te ajudar a trazer isso de volta: git reflog.

O que é o reflog?

O Git mantém um registro privado de todos os lugares por onde o HEAD passou. Tudo o que você faz no Git que move o ponteiro HEAD fica registrado, seja porque você fez um commit, deu um checkout, rodou um reset, ou porque um rebase ou merge mexeu nele.

Esse registro de movimento fica no log de referência (do inglês reference log ou reflog, para encurtar) e ele é local na sua máquina. Então, mesmo quando um commit não aparece mais no git log, a referência para ele geralmente ainda está no reflog.

Encontrando o commit que você perdeu

Para ver o reference log, você pode rodar o comando abaixo:

git reflog

Você vai ver uma lista de movimentos recentes, com a entrada mais recente no topo, como na imagem abaixo.

Cada linha tem um hash curto, uma referência como HEAD@{2}, e uma descrição do que aconteceu, coisas como “commit”, “reset: moving to” ou “checkout”.

Mesmo que seja difícil se acostumar a ler esse novo formato de log, a descrição e a ordem geralmente deixam claro onde você estava e podem ser a indicação que você precisa para saber para onde quer voltar.

Voltando para lá

Quando você encontrar a entrada certa, copie o hash. Depois, mova o seu branch de volta para aquele ponto:

git reset --hard <hash>

Substitua <hash> pelo hash que você encontrou no reflog.

Por exemplo, pensando na imagem acima, se você quiser voltar para o estado antes do reset, você precisaria rodar o seguinte:

git reset --hard a68cffa

Depois disso, o seu estado de trabalho volta a bater com o momento antes do erro, como se nada tivesse acontecido.

Uma observação rápida: git reset --hard descarta as suas mudanças não commitadas. Então tenha certeza de que você realmente quer cair nesse estado anterior antes de rodar o comando. Se você não tiver certeza, você pode usar git switch para ir até o hash primeiro e dar uma olhada sem mover o seu branch.

Recapitulando

A maioria das pessoas aprende sobre o reflog do jeito difícil, depois de perder trabalho por causa de um reset ou de um rebase. Então saber que ele existe pode ser uma mão na roda numa emergência.

Recapitulando os passos para restaurar um estado anterior perdido com o reflog:

Encontre o estado para o qual você quer voltar e copie o hash.
Confira se esse é mesmo o estado que você quer restaurar com git switch <hash>. Se não for, repita os passos 1 e 2 até encontrar o estado certo.
Rode git reset --hard <hash> para voltar para ele.

agenticstack.sh: compare tools for building AI agents

Jessica Temporal — Fri, 19 Jun 2026 03:00:00 +0000

If you are building AI agents and wondering which tools to use, agenticstack.sh is worth bookmarking. 🔖

This website lets you compare tools like auth, email, hosting, CMS, and others, so you’ll pick the best one for your use case.

It has comparative tables you can use to make an informed decision.

And since we are talking about AI here, it even has skills that you can install so you can ask questions right in your AI assistant chat. 😄

Let me know if you try it!

Follow along for more tips like this!

git stash: save your work without committing

Jessica Temporal — Thu, 18 Jun 2026 03:00:00 +0000

You’re working, some priority comes up, but you’re not ready to make a commit yet, and you need to switch branches. What do you do? 🤔

Some people like to make a throwaway commit just to save the work so they can undo it later, but I prefer git stash.

Think of it like a stack. You take the changes you made, bundle them up, save them locally, and then your working directory goes back to a clean state.

Each bundle is a stash and it gets saved on index zero.

You can then switch branches, do whatever you need to do, and when you come back, you can pop or apply the stash, and your most recent changes go back to where they were.

One heads up though: if you have new files that git isn’t tracking yet, they won’t be automatically added to this stash. So before you make a stash with new files, you need to stage them first. 😅

Want the full breakdown on git stash? I covered it in more depth here: Using git stash: pop, apply, and drop

If you want more git tips that save your work, follow along!

Preview Auth0 Changes Safely with Deploy CLI Dry Run

Jessica Temporal — Tue, 16 Jun 2026 22:25:31 +0000

Managing your Auth0 tenant configuration as code shouldn't be a "guess and check" process. In this video, I'll demonstrate how to use the Auth0 Deploy CLI's Dry Run feature. Learn how to preview exactly which resources will be created, updated, or deleted before you ever touch your production environment.

What You'll Learn

How to configure the Auth0 Deploy CLI with a config.json file.
The proper syntax for exporting your current tenant configuration to YAML.
How to use the --dry-run flag to validate local changes.
Best practices for keeping sensitive credentials out of your Git history.

Resources

📄 Auth0 Deploy CLI Documentation
💻 GitHub Repository

How to Decode, Encode, and Validate JWTs inside Claude Code

Jessica Temporal — Fri, 29 May 2026 17:42:15 +0000

Stop context switching and start debugging. Let me show you how to supercharge your AI agent with JWT Skills. Learn how to decode, encode, and validate JSON Web Tokens (JWTs) directly within your terminal session using Claude Code. Whether you're troubleshooting an expired token or testing a custom claim, these tools bring security insights right into your development flow.

What You'll Learn:

How to install the jwt-skills
Decoding tokens to inspect headers, payloads, and claims.
Identifying security flags like expired tokens or PII in payloads.
Generating test tokens with custom claims for edge-case testing.
Validating tokens against JWKS endpoints for production-level checks.

Resources:

🛠 Get the Skills
📖 JWT Deep Dive

Manage Your Auth0 Tenants Faster with the Gemini CLI Extension

Jessica Temporal — Wed, 29 Apr 2026 21:01:35 +0000

Stop switching between your browser and terminal to manage identity. In this video, I'll show you how to integrate the Auth0 MCP Server directly into your Gemini CLI.

Learn how to leverage AI to query your applications, initialize tenants, and manage APIs using natural language commands without leaving your development environment.

What You'll Learn

How to find the Auth0 extension on the official Gemini page.
The one-command installation process for the Auth0 MCP server.
Authenticating and initializing your Auth0 environment via CLI.
Using natural language to list applications and create new API resources.