Replies: 2 comments
-
Hello, have you tried the new updated doc ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
First, roles must be created in Keycloak client as described in here Then, you have two solutions:
Then, pay attention to this line It says that roles must be found under You can use I hope it will help you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are using Apache Airflow 3.0.2 with the official Helm chart version 1.17.0, deployed on Kubernetes via Terraform. We're integrating SSO using Keycloak.
Problem
After successful SSO login, users with the
"Admin"
role in Keycloak are being mapped to"Viewer"
in Airflow. We expect users with theAdmin
role in Keycloak to retain theirAdmin
role in Airflow as well.Configuration
We have the following
webserver_config.py
to configure Keycloak as the OAuth provider:Despite this configuration, the user gets assigned the
"Viewer"
role after login.Attempted Solution
We implemented a custom
SecurityManager
to override the role assignment behavior, as follows:Result
Now, users with the
Admin
role do get mapped correctly and can log in as admins.Issue
However, after this change, we are seeing frequent
500 Internal Server Error
responses on various Admin pages (e.g., under Security or Manage sections in the UI).Question
role_keys
are passed or howAUTH_ROLES_MAPPING
interacts withCustomSecurityManager
?Any guidance or examples of working SSO setup with role preservation in Airflow 3.0+ would be really appreciated.
Beta Was this translation helpful? Give feedback.
All reactions