for /v1/Repositories//%(repoId)/Token
Should it be authorisation_code?
After updating your Keyed Integrator License in your appsettings.json file, you'll still use a password grant type associated with an account, but you'll have more concurrent sessions available.
grant_type=password&username={username}&password={password}
Thanks Andrew. And if self-hosted, should the account be a Repository account, LFDS, or Windows AD? Excuse the dumb questions but I don't have a KIL to test with.
With the .Net Framework API, the documentation simply says to set the Session.ApplicationID to the UUID/GUID. In which case, a password isn't required.
Hi Ben,
By setting Keyed Integrator License in your appsettings.json, self-host Repository API server could add it to Session.ApplicationID for you. It also needd username and password to generate an access token to call other Repository APIs. Repository account, LFDS, and Windows AD all would work.
Thanks both for your replies and confirmation.