Versions Compared

Old Version 7

changes.mady.by.user Technische Redaktion

Saved on

compared with

New Version 8

changes.mady.by.user Technische Redaktion

Saved on

Key

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

...

As of Versionproduct version 1.0 | component version 1.0
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
DescriptionThis endpoint is used to update the global permissions file of the yuuvis® system. Similar to other schema update endpoints in yuuvis®, this infers a schema validation and returns its result to the user, performing the update only after successful validation.
Request HeadersContent-Type: application/xml
Request Example

/api/system/permissions

Code Block
languagexml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<roleSet xmlns="http://optimal-systems.org/ns/dmscloud/roleset/">
    <role>
        <name>ReadDeleteEmail</name>
        <permission>
            <action>read</action>
            <action>delete</action>
            <condition>system:objectTypeId = 'email:email'</condition>
        </permission>
    </role>
    <role>
        <name>ReadDocument</name>
        <permission>
            <action>read</action>
            <condition>system:objectTypeId = 'document'</condition>
        </permission>
    </role>
    <role>
        <name>ReadEmailAndDocument</name>
        <permission>
            <action>read</action>
            <condition>system:objectTypeId in ('email:email', 'document')</condition>
        </permission>
    </role>
    <role>
        <name>DeleteDocument</name>
        <permission>
            <action>delete</action>
            <condition>system:objectTypeId in ('document')</condition>
        </permission>
    </role>
    <role>
        <name>AdminRole</name>
        <permission>
            <action>read</action>
            <action>create</action>
            <action>delete</action>
        </permission>
    </role>
</roleSet>


Response Example

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

Code Block
title200 - no validation errors, the role set has been updated
{
    "validationErrors": []
}


Code Block
title422 - there were validation errors, the role set was not updated
{
    "validationErrors": [
        {
            "message": "Unable to unmarshal schema. [line: 148][column: 1323] cvc-complex-type.2.4.a: UngültigerInvalid Contentcontent wurdewas beginnendfound mitstarting Elementwith element 			'condition' gefunden.'{\"http://optimal-systems.org/ns/dmscloud/roleset/\":conditio}'. One of '{\"http://optimal-systems.org/ns/dmscloud/roleset/\":action, \"http://optimal-systems.org/ns/dmscloud/roleset/\":condition}' wirdis erwartet."expected.",
            "serviceErrorCode": 0
        }
    ]
}