SCIM Provisioning

[dangtony98]

Description 📣

This PR adds preliminary support for SCIM provisioning with documentation for Okta, Azure, and JumpCloud SCIM clients.

Suppose the SCIM server is Infisical, providers like Okta are SCIM clients, and "The User" is an administrator. The expected flow is as follows:

1. The User in Infisical creates a SCIM token for the SCIM client to use under traditional Authentication Bearer header.
2. The User configures the SCIM client with the SCIM token from Step 1, their SCIM URL, and any other client-specific configuration. This allows the SCIM client to authenticate and forward updates to the SCIM server.
3. The SCIM client can now provision/deprovision users to/from the SCIM server.

More specifically, it includes:

• Frontend for SCIM token generation.
• Backend endpoints + schema for SCIM token management, scimEnabled field addition onto organization.
• Backend /Users endpoints for SCIM client to interface with Infisical.

Type ✨

• Bug fix
• New feature
• Breaking change
• Documentation

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[gitguardian]

⚠️ GitGuardian has uncovered 10 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9387833	Triggered	Generic Password	e15ed4c	docker-compose.pg.yml	View secret
9387833	Triggered	Generic Password	e15ed4c	docker-compose.dev.yml	View secret
9387833	Triggered	Generic Password	e15ed4c	.env.example	View secret
9387833	Triggered	Generic Password	e15ed4c	docker-compose.pg.yml	View secret
9387833	Triggered	Generic Password	e15ed4c	docker-compose.dev.yml	View secret
8529478	Triggered	Generic High Entropy Secret	e15ed4c	.env.example	View secret
9605379	Triggered	Generic High Entropy Secret	318ad25	backend/src/db/seed-data.ts	View secret
9605380	Triggered	Generic Private Key	318ad25	backend/e2e-test/routes/v3/secrets.spec.ts	View secret
9605380	Triggered	Generic Private Key	318ad25	backend/e2e-test/routes/v3/secrets.spec.ts	View secret
9605381	Triggered	Generic High Entropy Secret	318ad25	.env.test.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[maidul98]

Just make sure the migration you created 20240208234120 falls as the last one. To make sure, you can just create a new migration and update this time stamp with it before merging. Otherwise i skimmed through and didn't see anything major