317,433 packages matching “custom auth”
@cedarjs/auth-dbauth-api
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-custom-setup
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-dbauth-web
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-netlify-web
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-netlify-api
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-firebase-setup
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-dbauth-setup
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-azure-active-directory-web
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-firebase-api
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-netlify-setup
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-supertokens-setup
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-supertokens-web
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-supertokens-api
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-firebase-web
v7.0.0 · 2 days ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
amplify-authenticator-react-custom
v1.2.2 · 2 years ago
A set of hooks and a component to easily implement completely custom auth components.
No known vulnerabilities
harshil-auth
v2.6.9 · 8 months ago
Custom auth library
No known vulnerabilities
mojang-auth
v1.0.1 · 5 years ago
Mojang authentication client, re-implementing parts of `node-yggdrasil` in classes, and adding support for custom auth servers.
No known vulnerabilities
flowlink-auth
v2.9.5 · 7 months ago
Custom auth library
No known vulnerabilities
@edirect/auth
v11.0.67 · 5 days ago
Authentication and authorization module for eDirect NestJS applications. Supports two auth providers — **Keycloak** (OIDC/JWT) and a **custom Auth Service** — with guards, middleware, decorators, and multi-tenant realm support.
No known vulnerabilities
@apicrafthq/script-sdk
v0.1.0-beta.6 · 1 month ago
TypeScript types for API Craft middleware and custom-auth scripts.
No known vulnerabilities