bugraoz93 commented on code in PR #58605: URL: https://github.com/apache/airflow/pull/58605#discussion_r2561865936
########## contributing-docs/21_keycloak_client_settings.rst: ########## @@ -0,0 +1,47 @@ + .. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +Setting up Keycloak Client for Breeze Review Comment: It's worth mentioning, but since it is available in Breeze docs, I haven't mentioned it again the command. ``` breeze start-airflow --integration keycloak ``` There are a couple of things we need to do, even with the above command. It is not updating the auth manager in the cfg (which is required for CLI) or in the env var, which is making the API Server boot up with SAM. I need to specifically set these things from environment variables and afterwards from `airflow.cfg`, which is persistent across breeze environments. Creating the client is still manual. While creating, I have tried some possible scenarios while writing this document. I have tried doing next next while creating a client, which ended up `Invalid parameter: redirect_uri`. Afterwards, of course, you can set * for login/redirect or + for logout redirect makes of course everything open, but I set up the proper values generally -- 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]
