A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

hi, I'm seeing `Failed to log in! An unexpected error occurred.` on a newly setup instance on kubernetes when trying to sign in with the default datahub user, I also don't see any logs in the /tmp/ directory, any suggestions? (the same deployment for a different instance is currently working, so not sure if I'm missing some setup? the elasticsearch, mysql, and kafka setup jobs already ran)

Hi, Sufyan, could you share a little bit of information about the environment where the deployment is failing and it’s how different from the environment where it’s succeeded?

the environment should be similar, it's connecting to a different mysql/kafka/elasticsearch instance but that should be about it, is there any initial setup besides those 3 setup jobs that needs to be performed?

<@U042KCFV9GX> actually even in the other instance which is running fine, I don't see the logs under `/tmp` , only the logs from `kubectl logs` which says `Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...`

And you do in fact have log4j configured?

I don't think so, is there any documentation for what needs to be configured for it?

<@U042KCFV9GX> are there any commands I can run inside the datahub-frontend or datahub-gms pods to help debug?

<@U042KCFV9GX> ingestion seems to be working and I do see gms logs updating fine but the login is still broken

Hi <@U04E2ML0WE7>, the login to datahub itself? You don’t have it configured with sso correct?

right, just logging in with the default "datahub" username/password

I tried it with okta authentication as well

```AUTH_OIDC_ENABLED: 'false',
                  AUTH_OIDC_DISCOVERY_URI: 'https://&lt;&gt;.<http://okta.com/.well-known/openid-configuration|okta.com/.well-known/openid-configuration>',
                  AUTH_OIDC_BASE_URL: conf.baseUrl,
                  AUTH_OIDC_SCOPE: 'openid profile email',
                  AUTH_OIDC_JIT_PROVISIONING_ENABLED: 'true',
                  METADATA_SERVICE_AUTH_ENABLED: 'false',```

And you said the login works fine in a different environment? Is it possible that the permissions for the new instance aren’t correctly configured?

yeah, the login works fine in the other environment with those settings

what permissions would need to be configured?

OIDC would be really helpful here I think- could you try enabling it? It’s turned off in the recipe you posted

sure, I can re-enable it, I was just trying to get the default login working first

I understand- we’ve had a few users run into this issue in the past as well

<https://datahubspace.slack.com/archives/C029A3M079U/p1676878960321899>