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

   ### Apache Airflow Provider(s)
   
   keycloak
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-keycloak==0.4.1
   
   ### Apache Airflow version
   
   3.1.5
   
   ### Operating System
   
   Ubuntu 22.04.1 LT
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   Packages airflow-core and apache-airflow-providers-keycloak installed via 
pip in virtualenv. Keycloak config is pointing to Keycloak instance deployed on 
OpenShift. The Keycloak access token is quite large because multiple realm 
roles are included in access token.
   
   ### What happened
   
   After logging in via Keycloak SSO the Airflow UI enters into a 401 
unauthorized loop. After successfull auth code flow, the cookie with access 
token + refresh token is not passed to Airflow UI because they exceed the 
cookie size limit of 4KB.
   
   <img width="1249" height="664" alt="Image" 
src="https://github.com/user-attachments/assets/7d3b4717-4197-47d5-be2f-6138d2b051d6";
 />
   
   ### What you think should happen instead
   
   After Keycloak login, the Airflow home page should display without any 401 
unauthorized errors.
   
   ### How to reproduce
   
   Login with a Keycloak user having a large access token, e.g., a user with 
15+ roles, so that access token + refresh token exceed cookie size limit of 4kB.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] 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