From: Jeny Sheth <jeny.sadadia@collabora.com>
To: Trevor Gamblin <tgamblin@baylibre.com>
Cc: kernelci@lists.linux.dev
Subject: Re: KernelCI Local Instance docs have missing/outdated info
Date: Tue, 28 Nov 2023 10:13:22 +0530 [thread overview]
Message-ID: <9820b359-cfc0-45b6-9edc-722b50e533c7@collabora.com> (raw)
In-Reply-To: <7ee32af8-341f-429b-96c1-ca407cb17f0d@baylibre.com>
Hello Trevor,
Thanks for reporting the issue. Due to recent API updates on user
management side, a few endpoints have been redesigned and renamed.
Endpoint to get access tokens has been renamed to `/user/login`.
We have updated documentation accordingly and updates have been
rolled-out to https://kernelci.org/docs/api. You can continue referring
to the same link. Sorry for the hurdles you had to face.
Thank you, Jeny
On 14/11/23 3:13 am, Trevor Gamblin wrote:
> Hello,
>
> While following https://kernelci.org/docs/api/local-instance/, I have
> run into an issue when trying to generate an admin API token:
>
> [tgamblin@homunculus ~]$ curl -X 'POST' \
> 'http://localhost:8001/latest/token' \
> -H 'accept: application/json' \
> -H 'Content-Type: application/x-www-form-urlencoded' \
> -d 'grant_type=&username=admin&password=hello&scope=admin users'
> {"detail":"Not Found"}[tgamblin@homunculus ~]$
>
> The previous steps to start the instance and confirm API availability
> work fine, but the "token" endpoint doesn't appear to be up, and I
> can't continue without it.
>
> Is there a newer set of documentation that can be followed, or can
> someone point me at what I've missed?
>
> Thanks,
>
> - Trevor
>
>
next prev parent reply other threads:[~2023-11-28 4:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 21:43 KernelCI Local Instance docs have missing/outdated info Trevor Gamblin
2023-11-28 4:43 ` Jeny Sheth [this message]
2023-11-28 21:34 ` Trevor Gamblin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9820b359-cfc0-45b6-9edc-722b50e533c7@collabora.com \
--to=jeny.sadadia@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=tgamblin@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).