152,052 packages matching “auth provider”
@sometic/auth-oidc
v1.0.11 · 22 days ago
OIDC Authorization Code + PKCE auth provider for Sometic.
No known vulnerabilities
@sometic/auth-local
v1.0.11 · 22 days ago
Configurable REST auth provider adapter for Sometic.
No known vulnerabilities
@cedarjs/auth-dbauth-web
v6.0.2 · 10 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
v6.0.2 · 10 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-api
v6.0.2 · 10 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-auth0-web
v6.0.2 · 10 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
v6.0.2 · 10 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-supabase-setup
v6.0.2 · 10 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-setup
v6.0.2 · 10 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
@beignet/provider-auth-better-auth
v0.0.56 · 1 hour ago
Better Auth provider for Beignet - adds auth port for authentication and session management
No known vulnerabilities
@cedarjs/auth-custom-setup
v6.0.2 · 10 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
v6.0.2 · 10 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
v6.0.2 · 10 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
@akord/akord-auth
v0.30.44 · 2 years ago
Akord Auth Provider
No known vulnerabilities
@cedarjs/auth-netlify-api
v6.0.2 · 10 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
v6.0.2 · 10 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
v6.0.2 · 10 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
v6.0.2 · 10 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
v6.0.2 · 10 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
v6.0.2 · 10 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