gbonazzoli commented on issue #58552: URL: https://github.com/apache/airflow/issues/58552#issuecomment-3584345544
@bugraoz93 I tried but the problem still exists and by the why it seems the best solution is to have "*" as Valid Redirect URI, at least it will display the login window. In my tests I tried both chains: - all "https with domain names, eg https://keycloak-prod.colombinigroup.com"; - all "http with IP Addresses, eg. http://192.168.99.11:30026";. What I think is that if you have an Airlfow on a vritual machine (in my case 172.16.80.246) and Keycloak on a different virtual machine (in my case on a Kubernetes cluster, eg. http://192.168.99.11:30026 on the configuration) you have somewhere wirtten on the code (or computed on the code) to return control to 127.0.0.1:8080 and not to 172.16.80.246:8080. Probably some networking mechanism (NAT ???) will confuse the code ? If Airflow and Keycloak are both on same machine (for example linked together with docker-compose) probably you can have a configuration that works. It is only an hypothesis. -- 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]
