I'm working on upgrading from 0.8.1 to 0.8.8 today...
# troubleshoot
o
I'm working on upgrading from 0.8.1 to 0.8.8 today, using the helm chart at https://github.com/acryldata/datahub-helm. I was surprised to learn this morning that file-based basic authentication is now the default behavior for the DataHub frontend (https://github.com/linkedin/datahub/pull/2818). For version 0.8.8, is it possible to disable auth entirely in
datahub-frontend
?
m
@big-carpet-38439: do you know the answer for this?
b
It still is possible, yes!
โค๏ธ 1
You can use the AUTH_JAAS_ENABLED=false config in your docker.env for datahub-frontend to disable
o
ah ok, thank you. Would a PR to expose that in the helm chart be supported? I'd be happy to add it.
oh wait nevermind, just noticed the
extraEnvs
thing that allows you to modify the environment for individual deployments. No changes to the
helm
chart necessary ๐Ÿ˜€ thanks again for the help and quick response!
b
of course ! please let me know if there are any issues using this^
(we do use it for the demo.datahubproject.io site)
o
I just re-deployed and that worked well! For anyone finding this thread from search, the trick was including something like this in
values.yaml
for the
helm
chart
Copy code
datahub-frontend:
  enabled: true
  extraEnvs:
    - name: AUTH_JAAS_ENABLED
      value: "false"
let me know if there are any issues using this
One thing I've noticed now that I set this up... setting
AUTH_JAAS_ENABLED
isn't exactly the same as the login behavior I saw before. On 0.8.1, we didn't have auth set up but there was still a log-in screen where users were prompted for a username and password. Any username and password would get you in, but at least that information was being captured. I was hoping to use that when we enable analytics, so I could see who is looking at certain datasets. On 0.8.8, setting
AUTH_JAAS_ENABLED=false
on the frontend, now when I navigate to the frontend I'm just immediately logged in. Clicking "log out" doesn't do anything. Not a huge deal at all, just wanted to call it out.
b
Got it - Didn't realize anyone would actually want the behavior of allowing any login!!
Are you folks able to enable SSO with OIDC?
o
Our long-term goal is to enable SSO with OIDC, but we're not doing that today. Just haven't prioritized that work yet (our small team runs several other services besides DataHub). So definitely not asking you to do any work to re-enable "allow any login but force the use of some login" haha. Totally not blocking us. All this means is that "get finer-grained analytics" will be an additional benefit of the SSO work when we do it.
b
Okay great to hear. Let me know when you guys do get to enabling OIDC and I can be on deck to make sure itโ€™s smooth for you
o
thanks very much, appreciate that!
p
@big-carpet-38439 I would like to integrate Superset and Looker over Okta ๐Ÿ˜„ We run DataHub on EKS Cluster in our test environment at Udemy. Could you help me about this issue?
Here is the PR : https://github.com/linkedin/datahub/pull/3043. Ok, I need to wait for it.
b
direct messaged you ๐Ÿ™‚
โค๏ธ 1