Backport SCIM related files to CE

[biazmoreira]

Description

Backport SCIM related files to CE.

These files were added in https://github.com/hashicorp/vault-enterprise/pull/9101, but were not backported due to this feature not being available in CE. However, some parts of the implementation live in CE files. This PR syncs up these files from ent to ce.

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• Jira: If this change has an associated Jira, it's referenced either in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vault-ui	Ready	Preview	Comment	Dec 1, 2025 1:21pm

[github-actions]

CI Results:
All Go tests succeeded! ✅

[bosouza]

Is there some PR that failed to be backported? which one is it? can you reflect those PRs in the history of this branch with cherry-picks?

[biazmoreira]

Is there some PR that failed to be backported? which one is it? can you reflect those PRs in the history of this branch with cherry-picks?

There is not backport that failed. We chose not to backport it.