Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build secure authentication with sessions, JWT, OAuth, passwordless, MFA, and SSO for web and mobile apps.
Build secure authentication with sessions, JWT, OAuth, passwordless, MFA, and SSO for web and mobile apps.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill is a reference guide. It contains code examples that demonstrate authentication patterns. Important: The code examples in this skill: Are templates for developers to adapt Show placeholder values (SECRET, API_KEY, etc.) Reference external services as examples only Are NOT executed by the agent The agent provides guidance. The developer implements in their own project.
User needs guidance on implementing authentication. Agent explains patterns for login flows, token strategies, password security, OAuth integration, and session management.
TopicFileSession vs JWT strategiesstrategies.mdPassword handlingpasswords.mdMFA implementationmfa.mdOAuth and social loginoauth.mdFramework middlewaremiddleware.md
This skill ONLY: Explains authentication concepts Shows code patterns as examples Provides best practice guidance This skill NEVER: Executes code Makes network requests Accesses credentials Stores data Reads environment variables
Code examples in auxiliary files show: Environment variables like process.env.JWT_SECRET - these are placeholders API calls to OAuth providers - these are reference patterns Secrets like SECRET, REFRESH_SECRET - these are example names The agent does not have access to these values. They demonstrate what the developer should configure in their own project.
Authentication: Who you are (this skill) Authorization: What you can do (different concern) Auth happens FIRST, then authorization checks permissions
Use CaseStrategyWhyTraditional web appSessions + cookiesSimple, instant revocationMobile appJWT (short-lived) + refresh tokenNo cookies, offline supportAPI/microservicesJWTStateless, scalableEnterpriseSSO (SAML/OIDC)Central identity managementConsumerSocial login + email fallbackReduced friction
Use bcrypt (cost 12) or Argon2id for passwords Use battle-tested libraries for JWT, OAuth Never implement password hashing, token signing manually Never store plaintext or reversibly encrypted passwords
Rate limiting -> CAPTCHA -> Account lockout -> MFA -> Audit logging
httpOnly + Secure + SameSite=Lax for cookies Short token lifetimes (15min access, 7d refresh) Regenerate session ID on login Require re-auth for sensitive operations
// Bad - reveals if email exists if (!user) return { error: 'User not found' }; // Good - same error for both cases if (!user || !validPassword) { return { error: 'Invalid credentials' }; }
LogDo Not LogLogin success/failurePasswordsIP, user agent, timestampTokensMFA eventsSession IDsPassword changesRecovery codes
Storing passwords with MD5/SHA1 - use bcrypt or Argon2id JWT with long expiry (30d) - use short access + refresh token Revealing if email exists - use generic error message Hard account lockout - enables denial of service SMS for MFA - vulnerable to SIM swapping No rate limiting on login - enables brute force
If useful: clawhub star auth Stay updated: clawhub sync
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.