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?

[juherr]

The api_password should be automatically set during the startup phase. See https://github.com/steve-community/steve/pull/1545/files
If not, maybe there is an issue somewhere.

[MaticBobnar]

Hi!
I've noticed the same issue. The api_password is never set and saved during startup phase or read from configuration.
I solved the issue by copying encoded password to api_password, but that is not really a practical solution.
Should maybe be looked into, I might've missed something

[fluppie]

Do you know how to encode? Or can you just copy paste your admin password and use the same, although that's not very smart to re-use it.
Myself I had an earlier Steve git clone (before these changes) and did one or two git pulls to sync to the latest version. Maybe it works fine on a fully new/clean install?
But keen to know how to encode a password so I can fix it manually in the time being :-)

[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.