Ilardi opened a new issue, #59277:
URL: https://github.com/apache/airflow/issues/59277

   ### Apache Airflow version
   
   Other Airflow 2/3 version (please specify below)
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   3.1.4
   
   ### What happened?
   
   I have the same issue described in 
[#56614](https://github.com/apache/airflow/issues/56614). 
   When i make a request to the Airflow API using a valid Airflow token that 
contains an expired access token from Keycloak i receive a 500 internal server 
error instead of 401/403 or such. I thought the issue would be fixed in 3.1.4 
but apparently it is not.
   
   ### What you think should happen instead?
   
   The application should not raise an exception but it should handle it with 
an appropriate http response code.
   
   ### How to reproduce
   
   1) Create a token at /auth/token
   2) Wait 5 minutes (or whatever the access token expiration date is) and make 
a request to the Airflow API using that token
   
   ### Operating System
   
   Ubuntu 24.04.1 LTS
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   I use this Dockerfile to build a custom image:
   <code>FROM apache/airflow:3.1.4
   USER airflow
   COPY requirements.txt /
   RUN pip install --no-cache-dir "apache-airflow==${AIRFLOW_VERSION}" -r 
/requirements.txt
   </code>
   
   The package installed from requirements is apache-airflow-providers-keycloak
   I am using keycloak:26.4.0
   
   ### 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