Data-Importer personal token authentication not working #8832
Unanswered
CallumCarmicheal
asked this question in
Q&A
Replies: 2 comments 3 replies
-
Could you show me the start of this log? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Ah check, so it never actually manages to authenticate, that was my worry. But indeed, this combination of variables is tricky because you can't just overrule the one with the other and hope for the best. It works best when it's always the same set of information. I'll look into it. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am having a issue trying to setup a cron job that automatically imports data from Nordigen/GoCardless. Following the documentation I had setup the importer using a public client id which allows user's to authenticate themselves when visiting the importer web ui but doesn't seem to allow any automation.
Although no matter how I attempt to pass in the access token I am unable to, even printing the access token from bash like
echo $FIREFLY_III_ACCESS_TOKEN
yield's the token but when ever I run the command I get the followingThe last 25 chars of the access token are:
with no token appended.[1] For example running
docker exec firefly-iii-importer-1 /bin/bash -c "php artisan importer:import /configurations/nordigen.json"
will give me the outputAfter reading around it seemed I needed a personal key to get that to work so I appended one to the environment like this:
And recieve the following error: [2]
You can't set FIREFLY_III_ACCESS_TOKEN together with FIREFLY_III_CLIENT_ID. One must remain empty.
.After further trial and error I had created this
This clears the client id from environment letting me set the access token, although I am left with the same error as *[1] without the personal token even being visible in the output.
After several attempts I am still unable to get this to work. I even attempted to use a http request
Even in that I get the same error in the log about authentication... I then tried the API directly with the auth code and it worked
http://192.168.0.2:992/api/v1/accounts?type=all&page=1&limit=250
.Error log of the POST request that actually let me get past the initial error of passing along the token:
Have I misconfigured something or is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions