Actions Supported by Policy-based Authorization
This section describes the SparkRTC actions supported by policy-based authorization.
Supported Actions
SparkRTC provides system-defined policies that can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are API-specific. See the following common concepts related to policies:
- Permissions: statements in a policy that allow or deny certain operations
- APIs: REST APIs that can be called by a user who has been granted specific permissions.
- Actions: specific operations that are allowed or denied in a custom policy.
- Dependencies: actions which a specific action depends on. When allowing an action for a user, you also need to allow any existing action dependencies for that user.
- IAM projects/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. For details about the differences between IAM and enterprise management, see Differences Between IAM and Enterprise Management.
When assigning permissions to a user group in IAM, you cannot select Enterprise projects when setting Specify the authorization scope on the Select Scope page.
SparkRTC supports the following actions that can be defined in custom policies.
| Permission | API | Action | IAM (Project) | Enterprise Project |
|---|---|---|---|---|
| Creating an application | rtc:app:create | √ | × | |
| Querying applications | rtc:app:list | √ | × | |
| Querying an application | rtc:app:get | √ | × | |
| Deleting an application | rtc:app:delete | √ | × | |
| Enabling an application | rtc:app:enable | √ | × | |
| Disabling an application | rtc:app:disable | √ | × | |
| Creating or updating a recording template | rtc:recordRule:save | √ | × | |
| Querying recording templates | rtc:recordRule:list | √ | × | |
| Querying a recording template | rtc:recordRule:get | √ | × | |
| Updating a recording template | rtc:recordRule:update | √ | × | |
| Deleting a recording template | rtc:recordRule:delete | √ | × | |
| Updating the automatic recording configuration | rtc:app:updateAutoRecord | √ | × | |
| Querying the automatic recording configuration | rtc:app:getAutoRecord | √ | × | |
| Configuring a recording event callback | rtc:app:updateRecordCallbackConf | √ | × | |
| Querying a recording event callback | rtc:app:getRecordCallbackConf | √ | × | |
| Removing an online user | rtc:room:removeUsers | √ | × | |
| Dismissing a room | rtc:room:dismiss | √ | × | |
| Listing access control parameters | - | rtc:app:getUrlAuth | √ | × |
| Controlling access to an application | - | rtc:app:updateUrlAuth | √ | × |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot