Versions Compared

Old Version 5

changes.mady.by.user Technische Redaktion

Saved on

compared with

New Version Current

changes.mady.by.user Technische Redaktion

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The result is a JSON structure containing a validationErrors list, which could be an empty list.

As of Versionproduct version 2021 Autumn | component version 2021 Autumn
Request MethodPOST
Response FormatJSON
Required Permission

available if listed in authorization.accesses in authentication-prod.yml and the specified access condition is matched.

>> AUTHENTICATION Service
Description


Excerpt
Validates an Validate the XML schema file to be used file passed in the request body for the usability as tenant schema for the tenant specified by the {tenant} path parameter.



The

validation response is returned in JSON format

currently used tenant schema is NOT updated.

For details and examples regarding request and response please visit Schema - Defining Object Types.

Request HeadersContent-Type: application/xmlResponse Example
Code Block
title200 - no validation errors, the schema has been updated
{
    "validationErrors": []
}
Code Block
title422 - there were validation errors, the schema was not updated
{ "validationErrors": [ { "message": "Ambiguous IDs. There are 2 property type definitions with the ID 'tenTenant1:from'.", "serviceErrorCode": 2110 }, { "message": "Wrong base ID. The base ID of the system:document type definition 'tenTenant1:email' must be 'system:document', but it is 'system:folder'.", "serviceErrorCode": 2131 }, { "message": "Invalid property reference 'fromm' in type definition 'tenTenant1:email'.", "serviceErrorCode": 2132 }, { "message": "Invalid secondary object type reference 'appAcl:aclowner' in type definition 'tenTenant1:email'.", "serviceErrorCode": 2135 } ] }