Azure SSO Kubernetes instructions seem outdated compared to 0.12.0 Helm chart
ehausig opened this issue · 0 comments
It looks like the instructions for setting up Azure SSO for Kubernetes may be out-of-date with release 0.12.0.
I have completed the instructions on the Azure SSO page. However, I've encountered a couple of potential issues on the Azure SSO for Kubernetes page:
- The docs show that Airflow's configuration for Azure SSO resides under the following field:
global.airflow.openmetadata.azure
However, the Helm chart's values.yaml
file shows it under the following field:
global.airflow.openmetadata.authConfig.azure
-
It looks like the
org.openmetadata.service.security.DefaultAuthorizer
authorizer class has been replaced with theorg.openmetadata.catalog.security.DefaultAuthorizer
in 0.12.0? (If I try to use the authorizer shown in the docs, it throws a "class not found" error.) -
If I use the
org.openmetadata.catalog.security.DefaultAuthorizer
authorizer class, I no longer get a "class not found" error. However, I do get a "java.lang.NullPointerException". (It's possible that this error is unrelated to the authorizer class, but I thought I'd include it just in case it has different requirements in the values.yaml file.)
Before I further troubleshoot the NullPointException issue, I'd like to confirm that the docs are up-to-date for 0.12.0. Could someone please take a look at the Azure SSO for Kubernetes page and update it to reflect what is required for 0.12.0? I'll be happy to test the changes. (My deepest apologies in advance if it is "user error", but there do seem to be some discrepancies. :)