3 min readTechnical Guide

Advanced Auth Debugging: JWTs, Cookies, and Localhost Anxiety

DevConsole Team
DevConsole Team
Engineering @ DevConsole
Advanced Auth Debugging: JWTs, Cookies, and Localhost Anxiety

The Auth Loop of Doom

We’ve all been there: You're trying to test an admin-only feature, but your browser is stuck in a redirect loop. You clear your cookies, restart your dev server, and manually decode a JWT on a random website just to check a role claim.

Auth debugging is notoriously friction-heavy. Because security headers are often restricted and cookies are scoped to domains, standard developer tools offer a fragmented view of your Identity Layer.

DevConsole: Your Security Command Center

DevConsole was built to provide "God Mode" visibility into your auth state without compromising your security posture.

1. Transparent JWT Inspection

Forget copy-pasting strings into jwt.io. DevConsole's Auth Feature automatically detects subatomic tokens in your headers or cookies and decodes them inline.

  • See the Claims: Instantly check if exp, iat, or custom roles like is_beta_user are correct.
  • Identify Expiry: DevConsole highlights tokens that are about to expire, preventing those "Why did I just get logged out?" moments.

2. Cookie Jar Management

Managing httpOnly cookies on localhost is a nightmare. DevConsole allows you to see the presence and metadata (Secure, SameSite, Domain) of these cookies even if they aren't accessible via document.cookie.

"Visibility is the first step to security. If you can't see your cookies, you can't trust your sessions."

3. Testing RBAC (Role-Based Access Control)

Using the State Injection capability, you can temporarily override your local user object to simulate different permission levels.

  • Does the "Delete Project" button actually hide for non-admins?
  • Does the API return a 403 when you manually manipulate the request?

Frequently Asked Questions (FAQs)

Why can't I see my session cookies in the regular Application tab?

Many modern auth providers set cookies as httpOnly, meaning they are invisible to client-side JavaScript for security reasons. DevConsole works at the protocol level to surface this information safely during development.

Does DevConsole support OAuth2 flows?

Yes. DevConsole can track the various redirects and state parameters used in OAuth2 and OpenID Connect flows, making it easy to see where a handshake is failing.

can I use DevConsole to test refresh token logic?

Absolutely. By manipulating the expiration time of your local access token, you can force your application's refresh logic to trigger, allowing you to test the "Silent Refresh" experience without waiting an hour for a real timeout.

Strategic Internal Links

External Documentation


Secure your workflow and ship with confidence. Download DevConsole for your local environment.