How to use the new API?

[fluppie]

Hi, I'm running the current github state and I have https working (cost me some fiddling with letsencrypt certs) but it's running.
I tried the swagger API interface but always get:

  "status": 401,
  "error": "Unauthorized",
  "message": "The user does not exist, exists but is disabled or has API access disabled.",

I click the auth button:

Used the regular admin username and pass and also tried with webapi.key as username and webapi.value as password

Any pointers here on how to get it working :-)?

[fluppie]

@goekay @juherr
Sorry for tagging you guys, but I would like to use the API instead of a direct connection to the MariaDB database.
Could you tell me how to get this going?

[juherr]

Users are now stored in database.
Check if your user is well configured.

[fluppie]

Aha, I think I need to fill-in an API password? In plain text or does it need some encryption?

[MaticBobnar]

I used copy&paste to test it out if that was indeed the issue - not a smart solution but for testing it's okay.
Afterwards I forked the project and modified the startup phase code so that it reads the api_password property from configuration and sets it accordingly. I set it to use the same encoding method as it is for normal webUser password.
Hope that helps !

[fluppie]

Good to know. I'll also try the copy paste thingy.

[fluppie]

Copy paste admin's encoded "password" into "api_password" works. But that's of course a dirty workaround :)

[goekay]

hey there, i have been waiting #1544 to stabilize/finalize and be merged to migrate the api pwd to the new flow. since this PR is taking a bit, i will create a fix PR that migrates the existing "header value" as encoded api pwd to the database.

edit: addressed and fixed in #1608