Hello @deepsbuns!!
Thanks for reaching out here! What modifications did you need to make to the helm chart, if you don't mind me asking? Anything features we are missing that could be helpful?
Please feel free to submit issues / PRs!
Unfortunately user provisioning for Workbench is still in a very VM-like world today. The way we generally see administrators do this is via an AD or LDAP server and sssd used to sync users to the linux OS. I realize this is not a great fit for Kubernetes, the Cloud, or Okta, because such a server may not be available.
In the meantime, another workaround might be writing a little sidecar service that creates users based on requests to the Okta API, a list in a configmap, etc. The Workbench container has supervisord as its init mechanism, so it should be fairly straightforward (though far less than ideal) to inject such a service. One very important element to keep in mind is that users' UIDs should always remain consistent across the cluster, and their linux username should match an assertion attribute coming from Okta (which attribute can be configured).
We are aiming for a better long-term solution to this problem using SCIM, but unfortunately do not yet have any expected ETA on when such a feature might be available for release.
I realize this is not much good news
Please feel free to reach out to your account representative if you would like to set up a call to discuss these sorts of items directly!