Developer Resources

Downloadable tools and references to help you build and debug BlokSec integrations faster.

BlokSec OIDC integration skill

A ready-made skill for AI coding assistants. It teaches the assistant the BlokSec-specific OIDC behaviors that the discovery document does not reveal, so it gets your integration right the first time instead of falling back on generic OIDC assumptions:

• The issuer carries an /oidc suffix (ID token validation fails without it)
• Access tokens are opaque, not JWTs (use introspection or /oidc/me)
• Refresh tokens require both offline_access and prompt=consent
• Revocation returns an empty 200 (RFC 7009), which trips up some libraries at signout
• Non-standard endpoint paths (/oidc/me, /oidc/session/end)

It also includes a proven oidc-client-ts configuration and a symptom-to-fix table for the mistakes integrators hit most often.

Who it’s for: developers using Claude Code (or another assistant that supports the standard SKILL.md format) to add “Sign in with BlokSec” to a web app, SPA, or backend.

Download

Download SKILL.md — the skill is a single Markdown file.

Install for Claude Code

Drop the file into your project’s skills directory and Claude Code discovers it automatically:

mkdir -p .claude/skills/bloksec-oidc-integration
curl -o .claude/skills/bloksec-oidc-integration/SKILL.md \
  https://docs.bloksec.com/skills/bloksec-oidc-integration/SKILL.md

To make it available across all your projects, install it personally instead, under ~/.claude/skills/bloksec-oidc-integration/SKILL.md.

Once installed, ask the assistant to add BlokSec login and it will invoke the skill on its own. You can also open the file and read it directly as a reference.

Note

The skill mirrors the OIDC Reference. When in doubt, the reference is the source of truth, and the OIDC Quickstart walks through a full integration step by step.