github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #3277] [CLOSED] SCIM Provisioning Enhancement on SSO Plugin #30333

New Issue
Closed
opened 2026-04-17 21:27:10 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 21:27:10 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3277
Author: @Whats-A-MattR
Created: 7/6/2025
Status: ❌ Closed

Base: v1.3 ← Head: feat/sso-scim

📝 Commits (3)

  • 2750b66 initial implementation, untested and probably broken
  • 25bc521 changing approach - getting rid of JWT
  • 9c857d5 updates, nothing major. added hooks from interface to endpoints

📊 Changes

1 file changed (+417 additions, -0 deletions)

View changed files

📝 packages/better-auth/src/plugins/sso/index.ts (+417 -0)

📄 Description

Implementing SCIM provisioning on the SSO plugin. This is great functionality to have if Better-Auth looks to support Enterprise deployments (like you'd see with SAML).

My opinion is that this is really tightly bound to enterprise auth, and it makes sense to extend the SSO Plugin rather than create an additional plugin for this particular feature/enhancement.

Still very very early, completely untested, just wanted to get it on the table.
Addresses: #3276

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/3277 **Author:** [@Whats-A-MattR](https://github.com/Whats-A-MattR) **Created:** 7/6/2025 **Status:** ❌ Closed **Base:** `v1.3` ← **Head:** `feat/sso-scim` --- ### 📝 Commits (3) - [`2750b66`](https://github.com/better-auth/better-auth/commit/2750b66f4fe21bc35061283a6d0a24b13f0a3ebf) initial implementation, untested and probably broken - [`25bc521`](https://github.com/better-auth/better-auth/commit/25bc521cc1b586823d5268fa6184a45e05532c59) changing approach - getting rid of JWT - [`9c857d5`](https://github.com/better-auth/better-auth/commit/9c857d56e9c795495a3bf1a770f12bbf3a3f6f40) updates, nothing major. added hooks from interface to endpoints ### 📊 Changes **1 file changed** (+417 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/plugins/sso/index.ts` (+417 -0) </details> ### 📄 Description Implementing SCIM provisioning on the SSO plugin. This is great functionality to have if Better-Auth looks to support Enterprise deployments (like you'd see with SAML). My opinion is that this is really tightly bound to enterprise auth, and it makes sense to extend the SSO Plugin rather than create an additional plugin for this particular feature/enhancement. Still very very early, completely untested, just wanted to get it on the table. Addresses: #3276 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-17 21:27:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#30333
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?