Provide docs and template to make it easy to use SCIM with Workbench
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Starting in 2024.04.0 Workbench supports user provisioning via SCIM for certain IdPs. It would be really helpful to users of the helm chart to have a quick way to setup the proper token for this to work + documentation on the steps needed specific to K8s/Helm.
The steps from what I can tell are:
- In
conf.server.rserver.confadd:user-provisioning-enabled: 1 - Create a
Secretcontaining a token (should give guidance on how to create one) - Add the following to
values.yaml
pod:
env:
- name: WORKBENCH_USER_SERVICE_AUTH_TOKEN_PATH
value: "/etc/scim-token/scim_token"
volumes:
- name: secret-volume
secret:
secretName: scim-token
volumeMounts:
- name: secret-volume
readOnly: true
mountPath: "/etc/scim-token"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Workbench setting in conf.server.rserver.conf and the Helm values.yaml configuration shown in the issue. Document the Kubernetes/Helm steps for enabling SCIM, creating the token Secret, and mounting it through WORKBENCH_USER_SERVICE_AUTH_TOKEN_PATH; add the requested reusable template or quick-start configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100