Title: Multi-Tenant Support for SCIM2 Server · Issue #9 · python-scim/scim2-server · GitHub
Open Graph Title: Multi-Tenant Support for SCIM2 Server · Issue #9 · python-scim/scim2-server
X Title: Multi-Tenant Support for SCIM2 Server · Issue #9 · python-scim/scim2-server
Description: The current implementation lacks proper multi-tenant isolation, which is needed when serving multiple identity providers through a single API endpoint. The server currently uses a single bearer token for authentication without any mechan...
Open Graph Description: The current implementation lacks proper multi-tenant isolation, which is needed when serving multiple identity providers through a single API endpoint. The server currently uses a single bearer tok...
X Description: The current implementation lacks proper multi-tenant isolation, which is needed when serving multiple identity providers through a single API endpoint. The server currently uses a single bearer tok...
Opengraph URL: https://github.com/python-scim/scim2-server/issues/9
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Multi-Tenant Support for SCIM2 Server","articleBody":"The current implementation lacks proper multi-tenant isolation, which is needed when serving multiple identity providers through a single API endpoint. The server currently uses a single bearer token for authentication without any mechanism to segregate data between different tenants.\n\nWe propose enhancing the implementation with tenant isolation by: \n\n1) Extending the authentication system to map bearer tokens to specific tenant IDs\n2) Modifying the backend interface to include tenant ID in all resource operations, ensuring data isolation regardless of the storage mechanism used\n3) Updating the resource filtering to respect tenant boundaries. \n\nThis approach maintains compatibility with the SCIM protocol while adding the necessary security boundaries between tenants, making the server suitable for multi-tenant environments where different organizations connect their identity providers to the same SCIM endpoint.\n\nIs this something you would be interested in merging into the code? I can submit a pull request, if so. ","author":{"url":"https://github.com/Th3R3p0","@type":"Person","name":"Th3R3p0"},"datePublished":"2025-03-03T22:30:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/9/scim2-server/issues/9"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:df70b574-d6fc-319a-6bea-ebb943171646 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | CA50:2A86E:4EEEEC:658D1A:698E78C4 |
| html-safe-nonce | a58fda4c2d1c519159e3dad0fcd3163c5e680e57ed6dab4e441aff257a2429fa |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDQTUwOjJBODZFOjRFRUVFQzo2NThEMUE6Njk4RTc4QzQiLCJ2aXNpdG9yX2lkIjoiMTMyMjQyOTkzMjY3NzAwMzQ2MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | a9f095e50ea9247d62668b2da554a80ae3fa82e27164f06889f2011a7d28a6de |
| hovercard-subject-tag | issue:2892466607 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python-scim/scim2-server/9/issue_layout |
| twitter:image | https://opengraph.githubassets.com/e4bb762abe1fa59a02b27811d58c80b67dbca866690b319c6bd4b67dbfa4b2cd/python-scim/scim2-server/issues/9 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/e4bb762abe1fa59a02b27811d58c80b67dbca866690b319c6bd4b67dbfa4b2cd/python-scim/scim2-server/issues/9 |
| og:image:alt | The current implementation lacks proper multi-tenant isolation, which is needed when serving multiple identity providers through a single API endpoint. The server currently uses a single bearer tok... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Th3R3p0 |
| hostname | github.com |
| expected-hostname | github.com |
| None | cb2828a801ee6b7be618f3ac76fbf55def35bbc30f053a9c41bf90210b8b72ba |
| turbo-cache-control | no-preview |
| go-import | github.com/python-scim/scim2-server git https://github.com/python-scim/scim2-server.git |
| octolytics-dimension-user_id | 187060383 |
| octolytics-dimension-user_login | python-scim |
| octolytics-dimension-repository_id | 844512592 |
| octolytics-dimension-repository_nwo | python-scim/scim2-server |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 844512592 |
| octolytics-dimension-repository_network_root_nwo | python-scim/scim2-server |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | f7a12861f7011eecb14bcc4388a767d829a52dfc |
| ui-target | canary-1 |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width