Genesys Cloud – Deprecation: Access control based on role name
| Announced on (YYYY-MM-DD) | Effective date (YYYY-MM-DD) | Aha! idea |
|---|---|---|
| 2017-08-09 | 2017-11-15 | - |
Currently there are still endpoints in public API that allow access to users that are assigned a role of a specific name. This functionality will be removed and access only granted for users with correct permissions. Certain views in the Genesys Cloud UI do interact with these endpoints, so even users who only use the UI may be affected.
On August 9, 2017, Genesys will:
- Remove public APIs that allow access to users that are assigned a role of a specific name documentation from the Resource Center.
On November 15, 2017 Genesys will:
- No longer allow access in public API by checking that users are assigned a role of a specific name.
- Remove the feature from Genesys Cloud.
FAQs
Am I affected?
Most likely not. Genesys continually monitors for access based on role names and our support and account management teams work with customers to rectify the issue.
Which APIs are affected by the deprecation?
Below is a list of public API endpoints that will be changed, along with the permissions that will be required for access and the role names that currently allow access.
| API endpoint | Verbs | Required permission | Allowed role name | Functionality |
|---|---|---|---|---|
api/v2/evaluations/favoritetemplates/{templateId} | DELETE | quality:evaluationForm:edit | qualityAdmin | Remove a question template from the favorites toolbar. |
api/v2/evaluations/favoritetemplates | GET, POST | quality:evaluationForm:edit | qualityAdmin | Get a list of question templates from the favorites toolbar or add a question. |
api/v2/evaluations/templates/{templateId} | DELETE, GET, PUT | quality:evaluationForm:edit | qualityAdmin | Delete, view, or edit a question template. |
api/v2/evaluations/templates | GET, POST | quality:evaluationForm:edit | qualityAdmin | Get a list of question templates or create a new question template. |
api/v2/recording/mediaretentionpolicies | DELETE | recording:retentionPolicy:delete | qualityAdmin | Bulk delete media retention policies. |
api/v2/recording/mediaretentionpolicies | GET | recording:retentionPolicy:view | qualityAdmin | Get a list of media retention policies. |
api/v2/recording/mediaretentionpolicies | POST | recording:retentionPolicy:add | qualityAdmin | Create a media retention policy. |
api/v2/recording/mediaretentionpolicies/{policyId} | DELETE | recording:retentionPolicy:delete | qualityAdmin | Delete a media retention policy. |
api/v2/recording/mediaretentionpolicies/{policyId} | GET | recording:retentionPolicy:view | qualityAdmin | View a media retention policy. |
api/v2/recording/mediaretentionpolicies/{policyId} | PATCH | recording:retentionPolicy:edit | qualityAdmin | Edit a media retention policy. |
How can I prepare for the feature removal?
If we identify your organization as one that needs to be fixed, a Genesys employee will reach out to you. However, Genesys only becomes aware that an organization needs to be fixed based on user activity, so we may not be able to identify all potentially affected organizations and users. An administrative user from your organization should review the configuration of your organization’s roles and ensure that users who need the listed functionality have roles with the correct permissions.
What if I need help or have questions?
For information on how to contact support, see Genesys Cloud Customer Care.
[NEXT] Was this article helpful?
Get user feedback about articles.