cambium-auth-credentials

Manage Cambium authentication credentials and Railway deployment variables.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-auth-credentials
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cambium-auth-credentials
Source: https://github.com/ecnepsyroc-bot/Dejavara/tree/main/deploy/skills/cambium-auth-credentials
Command: npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-auth-credentials

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides clear, operational guidance to prevent and recover from authentication and credential failures in the Cambium service, reducing deployment outages caused by misconfigured connection strings, missing JWT secrets, or accidental admin overrides.

Core Features & Use Cases

  • Credential safety rules: Enforces Railway Variable Reference usage for DATABASE_URL and documents blast radius implications for hardcoded connection strings.
  • Admin recovery pattern: Explains the emergency ADMIN_DEFAULT_PASSWORD override, how to perform a safe recovery, and the requirement to remove the env var immediately after use.
  • Auth architecture guidance: Describes the dual JWT + Cookie scheme, DataProtection key handling, token expiry behavior, and common 401 causes.
  • Pre-push checklist: Step-by-step verification items to run before pushing to main, including schema checks, build/tests, and env var validations.

Quick Start

Verify that Railway Variables contain DATABASE_URL set to ${Postgres.DATABASE_URL}, confirm JWT_SECRET_KEY is present, and run the pre-push checklist before deploying to Railway.

Frequently Asked Questions about cambium-auth-credentials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Railway DATABASE_URL for a PostgreSQL connection string?

Configure the Railway DATABASE_URL variable as a reference using ${Postgres.DATABASE_URL} to prevent hardcoded connection strings and avoid deployment outages caused by misconfigured database credentials.

Why does my ASP.NET Core JWT authentication return 401 errors after deployment?

ASP.NET Core JWT authentication returns 401 errors when the JWT_SECRET_KEY environment variable is missing, DataProtection keys are mishandled, or token expiry behavior is misconfigured during Railway deployment.

What's the best way to perform an admin password emergency reset in Cambium?

Perform an admin password emergency reset by setting the ADMIN_DEFAULT_PASSWORD override, executing a safe recovery, and immediately removing the environment variable afterward to prevent unauthorized access.

What should be on a pre-push deployment checklist for Railway?

A pre-push deployment checklist should include schema verification checks, build and test execution, JWT_SECRET_KEY presence validation, and DATABASE_URL variable reference confirmation before pushing to main.

Can I use hardcoded PostgreSQL connection strings instead of Railway variable references?

Hardcoded PostgreSQL connection strings are discouraged because they create a larger blast radius for credential failures; Railway variable references like ${Postgres.DATABASE_URL} ensure safe deployments.

How does the dual JWT and cookie authentication scheme work in Cambium?

The dual JWT and cookie authentication scheme combines ASP.NET Core JWT tokens with cookie-based auth, requiring proper DataProtection key handling and JWT_SECRET_KEY configuration to prevent common 401 authentication failures.