Update Allowed Origins

POST 
/api/client-applications/:clientApplicationId/update-origins

Add url origins to the client application whitelist. The Initiate Login endpoint will reject non-whitelisted origins. Warning! This is a destructive operation. The allowed origins will be overwritten with the provided list. Use the Get Client Application endpoint to retrieve the current list of allowed origins.

Request

Path Parameters

clientApplicationId stringrequired
Id of the client application.
Example: 65a7e8ef0d230d0a6bf755e07d39eb02

application/json

Body

required

allowedOrigins string[]

The allowed origins for the client application. Minimum one origin is required.

Responses

204

No content

application/json

Schema

Schema

any

400

Request parameters are invalid

application/json

Schema

Schema

statusCode integerrequired
statusName stringrequired
errorCode stringrequired

errors

object[]

Array [

message string

path string

The location of the invalid path param, query param or payload attribute.

]

Example (from schema)

{
  "statusCode": 400,
  "statusName": "Bad Request",
  "errorCode": "INVALID_REQUEST_INPUT",
  "errors": [
    {
      "message": "Invalid type",
      "path": "items[1].attributes.invalidField"
    }
  ]
}

403

Subject is not allowed to perform the action with the reason stated in the errorCode

FORBIDDEN Resource does not exist or there are no sufficient permissions to perform the action.

application/json

Schema

Schema

statusCode integerrequired
statusName stringrequired
errorCode stringrequired
reason string

Example (from schema)

{
  "statusCode": 403,
  "statusName": "Forbidden",
  "errorCode": "FORBIDDEN",
  "reason": "Unauthorized"
}

Loading...