We at HRS are running tasks on daily basis using Airflow from AWS - MWAA, which stands for Managed Workflows for Apache Airflow. We want to load our data from S3 to Exasol using Spark on EMR cluster. We have Airflow task that submits Spark Job on EMR cluster. …

To be able to use keycloak with OIDC you should use this container amundsen-metadata-oidc instead of amundsen-metadata The same for frontend container.

For some reason, localhost might be not a proper host to communicate with. To fix it change localhost -> 0.0.0.0 in keycloak.json. for instance: "issuer": "http://localhost:8080/auth/realms/master" -> "issuer": "http://0.0.0.0:8080/auth/realms/master"

When you do export FLASK_OIDC_SECRET_KEY='base-flask-oidc-secret-key' the value should be from keycloak.json: "client_secret": "c177eab4-71db-4543-a841-b707d4a0677c" In the abovementioned case the result would be: export FLASK_OIDC_SECRET_KEY='c177eab4-71db-4543-a841-b707d4a0677c'

Let’s say you want to let your data users connecting, querying, and visualizing your data sources. Due to security policy, you cannot create a single general user and share these credentials with all the users. Authentication comes into play right here. We don’t use third-party platforms for SSO such as…