stephen-bracken opened a new issue, #68943:
URL: https://github.com/apache/airflow/issues/68943

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   3.2.1
   
   ### What happened and how to reproduce it?
   
   When dag bundles are assigned to teams that are not defined in the keycloak 
client resources keycloak returns a 500 `resource not found: Dag:myteam` 
response on the `/dags` and `/` (home) screens. This is because the auth 
manager sends a request to keycloak to verify access to each dag by checking 
the resources.
   
   
https://github.com/apache/airflow/blob/4aafb9523bee458f68ab6b19470b43bb8eb4730e/providers/keycloak/src/airflow/providers/keycloak/auth_manager/keycloak_auth_manager.py#L439
   
   ### What you think should happen instead?
   
   The `KeycloakAuthManager` or `BaseAuthManager` should gracefully handle 500 
errors from keycloak due to missing resources for teams, and log them. This is 
important because if a team is added to airflow but not keycloak, all other 
teams will lose access to the `/dags` screen due to the 500 error response.
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Apache Airflow Provider(s)
   
   keycloak
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-keycloak==0.7.1
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   1.33.5
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   Some additional pip / apt packages
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to