SuperAPI AI Directory
Partner中文AI newsFavorites
Skillstesting-auth-setup

testing-auth-setup

Security & auditing

View repository

Updated 10-16 05:33

About this skill

Testing Auth Setup

Runs the Scalekit dryrun CLI to validate that your auth integration is correctly configured against a live environment.

Guardrails

  • MUST confirm SCALEKIT_ENVIRONMENT_URL and SCALEKIT_CLIENT_ID are set before running the dryrun command.
  • MUST ask for organization_id before running sso mode if it wasn't provided.
  • MUST show the dryrun output and explain what passed/failed in plain language, not just report success or failure silently.
  • MUST NOT guess between fsa and sso mode when it's ambiguous — ask the user which to use.

Modes

Mode What it tests When to use
fsa Full-stack auth login flow User is setting up or verifying login, callback, and session handling
sso Enterprise SSO flow User is setting up or verifying SAML/OIDC SSO with an identity provider

Prerequisites

Confirm these environment variables are available:

  • SCALEKIT_ENVIRONMENT_URL — your Scalekit environment URL
  • SCALEKIT_CLIENT_ID — your client ID from app.scalekit.com > Settings

Running the test

Full-stack auth (fsa)

npx @scalekit-sdk/dryrun --env_url=$SCALEKIT_ENVIRONMENT_URL --client_id=$SCALEKIT_CLIENT_ID --mode=fsa

Enterprise SSO

Requires an organization_id — ask for it if not provided.

npx @scalekit-sdk/dryrun --env_url=$SCALEKIT_ENVIRONMENT_URL --client_id=$SCALEKIT_CLIENT_ID --mode=sso --organization_id=<organization_id>

Choosing the mode

If the user doesn't specify a mode, do not silently pick one:

  1. Scan the project for clear signals only (e.g. SAML/OIDC IdP config files, organization_id in env, SSO skill already applied).
  2. If signals strongly indicate SSO, ask to confirm sso (and collect organization_id if missing).
  3. If signals strongly indicate full-stack auth only, ask to confirm fsa.
  4. If ambiguous or no signals — MUST ask the user which mode (fsa or sso) to use. Never default without confirmation.

After running

  • Show the command output.
  • Explain what passed and what failed in plain language.
  • If the test fails, map common failures to next steps:
Symptom / message Likely cause Next step
Invalid client / unauthorized Wrong SCALEKIT_CLIENT_ID or env URL Re-check credentials from app.scalekit.com → Settings
redirect_uri mismatch Callback not registered Add exact callback under Allowed Redirect URIs
organization not found Bad/missing organization_id in sso mode Confirm org id; re-run with --organization_id=…
Connection refused / DNS Wrong SCALEKIT_ENVIRONMENT_URL Verify env URL includes https:// and correct host
Timeout / network Firewall or offline Retry; check network access to the Scalekit env

When to switch skills

  • Use implementing-saaskit for the initial auth setup.
  • Use implementing-modular-sso for SSO configuration.
  • Use production-readiness-saaskit for a full pre-launch review.