You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update readme, add instructions on how to add auth during generation (apache#33)
Because openapi schema is not listing the supported authentication
schemas under security-section. The generated openapi client will not
pass on any authenticaion configuration at all.
Before generating the client, the relevant sections must be added.
For more background, see
apache/airflow#17172 and
apache/airflow#17174
Edit the file `airflow/airflow/api_connexion/openapi/v1.yaml`
107
+
Make sure it has the following `securitySchema`s listed under security `section`
108
+
```yaml
109
+
security:
110
+
- Basic: []
111
+
- GoogleOpenId: []
112
+
- Kerberos: []
113
+
```
114
+
If your deployment of Airflow uses any different authentication mechanism than the three listed above, you might need to make further changes to the `v1.yaml` and generate your own client, see [OpenAPI Schema specification](https://swagger.io/docs/specification/authentication/) for details.
115
+
(*These changes should not be commited to the upstream `v1.yaml` [as it will generate misleading openapi documentaion](https://github.com/apache/airflow/pull/17174)*)
116
+
117
+
```bash
111
118
cd airflow
112
119
113
120
# bump up the version in python.sh & run the following command
0 commit comments