posit-dev / posit-dev/team-operator
Remove generation of workbench_nss.conf
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Problem
The team-operator is generating /etc/rstudio/workbench_nss.conf (note the underscore) which configures the NSS module to use the HTTP address:
server-address=http://workshop-workbench.posit-team.svc.cluster.local:80
Workbench already auto-generates the correct /etc/rstudio/workbench-nss.conf (note the hyphen) which uses the unix socket:
server-address=unix:/var/run/rstudio-server/rstudio-rserver/user-service.socket
admin-token-path=/etc/rstudio/admin-token
user-token-path=/etc/rstudio/user-token
verify-ssl-certs=1
Using the HTTP address instead of the unix socket is a known deadlock scenario for user provisioning. This was observed during a workshop with ~2,100 users where initial login via Keycloak OIDC/JIT provisioning was failing intermittently (users had to retry 3+ times to successfully sign in).
Expected Behavior
The team-operator should not generate workbench_nss.conf. Workbench handles this automatically and correctly uses the unix socket path by default.
Context
- Observed on the
dev.workshop.posit.teamdeployment - Environment: Keycloak as IdP, Workbench configured as OIDC client with JIT provisioning
- ~2,107 registered users at the time of the issue
- Slack thread: https://positpbc.slack.com/archives/C0AUN9L3L3G/p1781711339011129
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
Search the repository for the literal workbench_nss.conf and trace the code that writes it. Confirm the operator no longer produces the underscore-named file while the hyphenated Workbench-managed file remains unaffected, then run the relevant Go tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100