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

web admin: better handling of invalid Fingerbank key #4802

Closed
nqb opened this issue Sep 11, 2019 · 2 comments
Closed

web admin: better handling of invalid Fingerbank key #4802

nqb opened this issue Sep 11, 2019 · 2 comments

Comments

@nqb
Copy link
Contributor

nqb commented Sep 11, 2019

An invalid Fingerbank key is not correctly handle when saved.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Fingerbank -> General settings
  2. Enter your API key: Zayme
  3. Save
    => Next four API calls reply with 200 (upstream/collector/query/proxy)
  4. Leave this menu and come back
    => your API key has disappeared, API call to account_info return:
{"errors":[],"message":"Invalid key","status":401}

but /usr/local/fingerbank/conf/fingerbank.conf contains your API key.

Expected behavior
Have an error message when your key is not valid.

@nqb
Copy link
Contributor Author

nqb commented Sep 11, 2019

Certainly related to #4805

@extrafu extrafu assigned julsemaan and unassigned satkunas Sep 11, 2019
@julsemaan
Copy link
Collaborator

#4805 currently prevents me from working on this issue since the settings section is broken in the admin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants