Skip to content

Add instructions on how to use authentication in readme. #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 25, 2021

Conversation

hterik
Copy link
Contributor

@hterik hterik commented Oct 22, 2021

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.

The new section describes ways to work around this limitation.

For more background, see
apache/airflow#17172 and
apache/airflow#17174

@msumit
Copy link
Contributor

msumit commented Oct 22, 2021

Why don't we generate the client with all three auth mechanisms or at least with Basic one & not commit v1.yaml in the main airflow repo? The benefit would be that users don't need to go through all of these & we can add this info in the client's release doc instead of readme.

@hterik hterik force-pushed the auth_instructions branch from 9c22aba to 7fb0000 Compare October 25, 2021 06:15
@hterik
Copy link
Contributor Author

hterik commented Oct 25, 2021

Ok, reverted those changes and added instructions on how to adjust the schema under the release process section instead..

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
@hterik hterik force-pushed the auth_instructions branch from 7fb0000 to 88289d8 Compare October 25, 2021 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy