152,047 packages matching “auth provider”
@cedarjs/cli-helpers
v6.0.2 · 10 days ago
This package is used by auth provider setup scripts.
No known vulnerabilities
@backstage/plugin-auth-backend-module-google-provider
v0.3.19 · 2 days ago
A Google auth provider module for the Backstage auth backend
No known vulnerabilities
@backstage/plugin-auth-backend-module-gcp-iap-provider
v0.4.19 · 2 days ago
A GCP IAP auth provider module for the Backstage auth backend
No known vulnerabilities
@redwoodjs/cli-helpers
v8.9.0 · 11 months ago
This package is used by auth provider setup scripts.
No known vulnerabilities
@cedarjs/auth
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-clerk-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-clerk-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
@jskit-ai/auth-provider-local-core
v0.1.103 · 10 minutes ago
Local auth provider with a file backend default and no database requirement.
No known vulnerabilities
@salte-auth/popup
v3.1.0 · 4 years ago
A Salte Auth provider for authenticating via Popup!
No known vulnerabilities
@cedarjs/auth-clerk-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
@sometic/auth-firebase
v1.0.11 · 22 days ago
Firebase Auth provider adapter for Sometic.
No known vulnerabilities
@semapps/auth-provider
v1.1.0-patch.1 · 10 months ago
React-Admin auth provider for SemApps
No known vulnerabilities
@dashadmin/dash-auth
v1.3.71 · 1 day ago
> Authentication utilities and auth provider for Dash.
No known vulnerabilities
autohost-github-auth
v1.0.0-beta-1 · 10 years ago
GitHub auth provider for autohost
No known vulnerabilities
@sometic/auth-supabase
v1.0.11 · 22 days ago
Supabase Auth provider adapter for Sometic.
No known vulnerabilities
@cedarjs/auth-supabase-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
@o3co/auth-provider-redis
v0.14.0 · 1 day ago
Redis-backed adapters (ChallengeStore, ReplaySeenSet) for @o3co/auth-provider-core
No known vulnerabilities
@cedarjs/auth-auth0-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-azure-active-directory-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-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