Update the allowed origins

Add url origins to the client application whitelist. The Generate a challenge 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 a client application endpoint to retrieve the current list of allowed origins.

Path Parameters

• clientApplicationId string required

  Id of the client application.

  Example: 65a7e8ef0d230d0a6bf755e07d39eb02

application/json

Request Body required

• allowedOrigins string[]

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

Responses

• 204
• 400
• 403

---

No content

application/json

• Schema

---

Schema

any

Request parameters are invalid

application/json

• Schema
• Example (from schema)

---

Schema

• statusCode integer required
• statusName string required
• errorCode string required
• errors string[]

{
  "statusCode": 400,
  "statusName": "Bad Request",
  "errorCode": "BAD_REQUEST",
  "errors": [
    "Expected string, received number"
  ]
}

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
• Example (from schema)

---

Schema

• statusCode integer required
• statusName string required
• errorCode string required
• reason string

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

Loading...