I need some direction on JWT and auth config about frequi HOT 8 CLOSED

Not really at the moment, as this project is still at the very early alpha stage, aimed at developers familiar with setting up the environment.

We will simplify setup fpr users in the future, but thats currently no real priority.

What error are you receiving? (Http errorcodes) ... Maybe also in the console log of the browser

from frequi.

The most important thing maybe, running yarn serve will not start freqtrade, but youll have to run an instance seperately.

from frequi.

I'm familiar with python, and have been tinkering with Vue for over a year, I'm comfortable with APIs, but haven't delved much into the authentication side of things. freqtrade is running fine, posting to my exchange and to telegram. Below is the STDOUT for freqtrade, I was getting 401's when attempting to integrate frequi. (which is a wonderful name BTW 👍 )

2020-07-09 01:39:41,462 - freqtrade.data.converter - INFO - Missing data fillup for ZEC/USD: before: 522 - after: 719
2020-07-09 01:39:41,487 - freqtrade.data.converter - INFO - Missing data fillup for DAI/USD: before: 633 - after: 719
2020-07-09 01:39:41,514 - freqtrade.data.converter - INFO - Missing data fillup for BAT/USD: before: 652 - after: 719
2020-07-09 01:39:41,541 - freqtrade.data.converter - INFO - Missing data fillup for QTUM/USD: before: 677 - after: 716
2020-07-09 01:39:41,566 - freqtrade.data.converter - INFO - Missing data fillup for XLM/USD: before: 705 - after: 719
2020-07-09 01:39:41,610 - freqtrade.data.converter - INFO - Missing data fillup for REP/USD: before: 697 - after: 717
2020-07-09 01:39:41,634 - freqtrade.data.converter - INFO - Missing data fillup for LTC/USD: before: 709 - after: 719
2020-07-09 01:39:41,657 - freqtrade.data.converter - INFO - Missing data fillup for WAVES/USD: before: 710 - after: 719
2020-07-09 01:39:41,681 - freqtrade.data.converter - INFO - Missing data fillup for ATOM/USD: before: 671 - after: 719
2020-07-09 01:39:41,704 - freqtrade.data.converter - INFO - Missing data fillup for ETC/USD: before: 536 - after: 719
2020-07-09 01:39:41,748 - freqtrade.data.converter - INFO - Missing data fillup for EOS/USD: before: 704 - after: 718
2020-07-09 01:39:41,772 - freqtrade.data.converter - INFO - Missing data fillup for XTZ/USD: before: 674 - after: 714
2020-07-09 01:39:41,836 - freqtrade.data.converter - INFO - Missing data fillup for DASH/USD: before: 682 - after: 700
2020-07-09 01:39:46,395 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:46] "GET /api/v1/status HTTP/1.1" 401 -
2020-07-09 01:39:46,399 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:46] "GET /api/v1/show_config HTTP/1.1" 401 -
2020-07-09 01:39:46,402 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:46] "GET /api/v1/trades HTTP/1.1" 401 -
2020-07-09 01:39:46,404 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:46] "GET /api/v1/whitelist HTTP/1.1" 401 -
2020-07-09 01:39:46,407 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:46] "GET /api/v1/blacklist HTTP/1.1" 401 -
2020-07-09 01:39:51,359 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:51] "GET /api/v1/status HTTP/1.1" 401 -
2020-07-09 01:39:51,361 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:51] "GET /api/v1/show_config HTTP/1.1" 401 -
2020-07-09 01:39:51,362 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:51] "GET /api/v1/trades HTTP/1.1" 401 -
2020-07-09 01:39:51,364 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:51] "GET /api/v1/whitelist HTTP/1.1" 401 -
2020-07-09 01:39:51,365 - werkzeug - INFO - 127.0.0.1 - - [09/Jul/2020 01:39:51] "GET /api/v1/blacklist HTTP/1.1" 401 -

and when I attempt to hit the API in Chrome (without tinkering with headers) I get unauthorized as expected.

Honestly I haven't researched JWT yet, or fired up postman to test header combinations to troubleshoot. I guess I assumed the placeholders would all exist in vue conf, and a global search for JWT in the project didn't reveal anything obvious, so I came here first for some hints. If having folks figure it out on their own is the best approach, I'm cool with that. 👍

from frequi.

Best try to logout and back in ...(top right corner).
You do have 2 options on login, either through the vue /webpack proxy or to connect directly to the flask api(by changing the url to localhost:8081).

If you are using the direct method, you MUST add http://localhost:8080 to the allowed cors list in freqtrade, otherwise requests will fail.

The first request upon login then should go to /login.

Also, every 15 minutes you might notice a few requests ending in 401, but they're followed with token refresh requests so should not be a huge problem (but a known one nonetheless).

Also, its better to have the chrome side of the logs ... I doubt that the problem is freqtrade.

from frequi.

Additional point - did you actually log in (click the login button)?

as said, the project is early alpha - so the "requires auth" page is not yet fully protected, so you CAN get to that page - but it'll then not show anything as the authentication to the api is missing.

from frequi.

so the "requires auth" page is not yet fully protected, so you CAN get to that page - but it'll then not show anything as the authentication to the api is missing.

This is what I did the first time, I didn't see the login button and went straight to the trade view, but without CORS_origins defined on the freqtrade side, Vue wasn't able to retrieve any data.

After adding CORS_origins the data is loading as expected 👍

I increased the timeout in apiService.ts, and everything runs smoothly now with no errors in the console.

Thanks for the help & support! These are great projects!

from frequi.

I increased the timeout in apiService.ts, and everything runs smoothly now with no errors in the console.

This is interresting - what did you increase it to - and which calls did make problems?

are you running it "offline" (both on localhost) - or is it "real" networking - where freqtrade is running on some remote host?

from frequi.

I've increased the timeout to 5s now (hope that'll do).
Also, when not loggedin, no requests are beeing made from now on.

We'll still work on properly protecting the trades (and subsequent pages) which require authentication.

from frequi.