Superset /api/v1/security/csrf_token return msg': 'Missing Authorization Header'

[temuujinmo4]

Bug description

response = requests.get("https://report.databank.mn/api/v1/security/csrf_token', headers={
            'Content-type': 'application/json',
            # 'Authorization': 'Bearer {}'.format(access_token)
        })

return msg': 'Missing Authorization Header'

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

To resolve the "Missing Authorization Header" issue when accessing the /api/v1/security/csrf_token endpoint in Superset, you need to include the appropriate Authorization header in your request. The Authorization header typically requires a Bearer token, which you can obtain through the authentication process.

Here's an example of how you might modify your request to include the Authorization header:

response = requests.get(
    "https://report.databank.mn/api/v1/security/csrf_token",
    headers={
        'Content-type': 'application/json',
        'Authorization': 'Bearer {}'.format(access_token)  # Ensure access_token is correctly set
    }
)

Make sure that access_token is a valid token obtained from your authentication provider. If you haven't obtained an access token yet, you'll need to authenticate first to get one.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[hainenber]

Dosu is correct, you actually commented out the Authorization header part.

[temuujinmo4]

'Authorization': 'Bearer {}'.format(access_token)

still error

[hainenber]

Right, the security token is broken currently due to PyJWT. I'll link the previous PR to fix this issue too.

[rusackas]

Trying to get a little more attention on the linked PR. Feel tree to verify on your branch that the fix proposed in the PR works for you!