| Page Properties |
|---|
|
| Status | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | progress |
|---|
|
|
|---|
| Priority | 2 |
|---|
| Note |
|
|---|
| Assignee | Inga for review |
|---|
Resources |
...
Complete role set files can be supplied to one of the endpoints via an HTTP POST request, overwriting the previous role set present at that position. Thus, retrieving and extending the previous role set state using a GET request on the same endpoint is strongly recommended. New role sets can also be validated by posting them to the role set endpoint URLs using the added URL suffix /validate.
>> Code examples in gitHub
Summary
Now that you know how you can interact with the permission system, you may want to proceed to creating a permissions file befitting your requirements. Find example permission files in the Permissions via Roles concept article.
| Info |
|---|
|
More Tutorials| Section |
|---|
| Column |
|---|
| This tutorial shows how to authenticate a Java client at the Core API. Keep reading |
| Column |
|---|
| Details about the structure of the Permission System, including example files. Keep reading |
| Column |
|---|
| | Insert excerpt |
|---|
| Access Authorization for Endpoints |
|---|
| Access Authorization for Endpoints |
|---|
| nopanel | true |
|---|
|
Keep reading
|
|
|
...