Skip to content
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

[BUG] ApiKey to access FlowiseApi is expired after some time #3748

Open
AKamilyanov opened this issue Dec 20, 2024 · 0 comments
Open

[BUG] ApiKey to access FlowiseApi is expired after some time #3748

AKamilyanov opened this issue Dec 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@AKamilyanov
Copy link

AKamilyanov commented Dec 20, 2024

I am using the cloud version of Flowise.
I have generated an ApiKey from the Flowise menu to access the API with a simple GET request (list existing chatflows in account).
I added this key in authentication header of my request. I got response from Api as expected.
But after some period of inactivity I got error "401-Unauthorized" and suggestion to go to flowise.com/auth/login
When I login to Flowise with web browser, then ApiKey become valid again.

To Reproduce

  1. Go to "API Keys" menu. Generate new key or use Default
  2. Use this key to send request
    curl --request GET \ --url https://<sample>.flowiseai.com/api/v1/chatflows \ --header 'Authorization: <generated key>'
  3. Make sure you have the correct expected result
  4. Wait for 1-2 days (do not login or use account this time)
  5. Repeat point 2
  6. You will get 401 result with "redirectTo: https://flowise.com/auth/login"

Expected behavior
ApiKey will not expire, or it will be possible to login again with an http post request (flowise.com/auth/login endpoint requires web browser).

Screenshots
image

Setup

  • Cloud version at flowise.com
  • Flowise Version 2.2.1
  • Browser chrome/cURL
@HenryHengZJ HenryHengZJ added the bug Something isn't working label Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants