401 error while using Airflow API

[megha120]

Apache Airflow version

2.1.0

What happened

Getting the following error while trying out the Airflow API:
{
"detail": null,
"status": 401,
"title": "Unauthorized",
"type": "https://airflow.apache.org/docs/apache-airflow/2.1.0/stable-rest-api-ref.html#section/Errors/Unauthenticated"
}

What you think should happen instead

The API should work properly as I am passing the username and password as required for basic authentication.

Even with the swagger ui I am getting the same error.

How to reproduce

I am using the local installation of Apache Airflow (https://airflow.apache.org/docs/apache-airflow/stable/start/local.html)

Operating System

Linux

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[ephraimbuddy]

You need to set the configuration for basic authentication properly. See https://airflow.apache.org/docs/apache-airflow/2.1.0/security/api.html, let me know if it worked for you, if not I will reopen the issue

[megha120]

I have set the configuration to airflow.api.auth.backend.basic_auth. You can check in the screenshot below,

But it is still not working.

[megha120]

You need to set the configuration for basic authentication properly. See https://airflow.apache.org/docs/apache-airflow/2.1.0/security/api.html, let me know if it worked for you, if not I will reopen the issue

@ephraimbuddy It is still not working for me, kindly assist.

[potiuk]

I am afraid it does not work this way - if you have some findings and want to discuss it and share with others your errors - feel free to open discussion and discuss it. Unless you can point out to the exact issue of airlfow - you can just hope on someone who has an experience with setting to help you - but this is not a "bug" of airflow and people here help in their free time/when they have enough knowledge and experience (maybe - there is no guarantee). I think you have some configuration problem - because the authorization works for basically many people (including our tests) - but unless you show logs and set that there is an airflow issue, this is at most a discussion.

BTW. I think you might have webserver misconfigured. The fact that your CLI works does not mean that the webserver is configured the same way - make sure your configuration is the same everywhere and that your websever properly reads it. Also you should look at the log files to try to understand what happens.

[ctmuthu]

I'm facing the same issue. I have the config in place. I'm using 2.2.5 Version

[zachik250]

If I change the url - I can see that the page cannot be found - with mean that when I'm with correct URL I realy get to the server but having auth issue.

Where can I found the server logs (not the dags log?)
What else can be the issue ?

[ctmuthu]

401 means your username and password has some issue. In my case, the auth_backend config was the problem.

I guess your config looks like this

[api]
auth_backend = airflow.api.auth.backend.basic_auth

Do you have another user to test?

[zachik250]

I have the user I created manually , and the admin user that I can see when the server is start up - both not working

[potiuk]

@zachik250 - I think yiou simply need to debug it - likely you have some error in configuration - maybe another typo. It's possible that you just step in with the debugger over Airlfow webserver (same as any other python application and try to debug it). That's what I'd do, but I can't - you are the only one with the superpowers of debugging your configuration.

Airflow is open-source and that gives you the extra option that you can just check what's going on - I do it all the time with other 3rd-party libraries.

[liurida]

I have the user I created manually , and the admin user that I can see when the server is start up - both not working

after creating a test account with Admin/User/Op roles, I could access the api with the new account.