Create new auth client
POST/login/client
Creates a new auth client.
Redirect urls defaults to empty list.
If no redirectURLs are specified the client will be unusable until they are updated.
If requiresSecret
is true
, authorization as this client won't work until a client secret is added
(see POST /login/client/:id/clientSecret).
Needs admin persmissions.
Request
- application/json
Body
required
The name to set for the auth client.
If given, must be non empty and match /^[a-zA-Z0-9+/-_= ]+$/g
A list of url strings containing at least one url. These are the URLs the oauth autorize endpoint will redirect back to
Defaults to []
on create
If given, sets the validity flag of the auth client.
Defaults to true
on create
If given, setns the need for the client to authenticate using a secret
Defaults to true
on create
Responses
- 201
- 400
The auth client that was created
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
The unique ID of this client
The (human readable) name of the auth client to be able to keep track ofit.
Doesn't need to be unique, can be null
The list of valid enpoints to redirect the user back to after authentication has finished.
The actual url to use is given in the authorize request and must be included in this list. If none is given, the first one from this list will be used
If this is false
the client is not valid and no authorization, token, ... requests from it should be answered.
If true
requesting a token as this client requires the use
of a client secret accoring to the oauth specification.
If false
client secrets can be present and given but are not required
[
{
"id": "12345678-90ab-cdef-fedc-ab0987654321",
"name": "string",
"redirectUrls": [
"https://example.com/oauth/callback?query=value"
],
"isValid": true,
"requiresSecret": false
}
]
If the input data didn't match the schema