(→service-client-api.accepted-web-content-origins) |
(→service-client-api.accepted-web-content-origins) |
||
| Line 6: | Line 6: | ||
* Valid Values: A comma-separated list of URLs or '*' — for example: '<nowiki>http://my-web-server-1,http://my-web-server-2</nowiki>' or '*'. | * Valid Values: A comma-separated list of URLs or '*' — for example: '<nowiki>http://my-web-server-1,http://my-web-server-2</nowiki>' or '*'. | ||
* Changes take effect: When the session is started or restarted. | * Changes take effect: When the session is started or restarted. | ||
| − | * Description: | + | * Description: Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self explanatory keywords: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'interaction.getInteractions', 'interaction.getByInteractionId', 'interaction.getByBundleId', 'interaction.getByCaseId', 'interaction.attachUserData', 'interaction.updateUserData', 'interaction.deleteUserData', 'voice.dial', 'voice.startCallRecording', 'voice.stopCallRecording', 'voice.pauseCallRecording', 'voice.resumeCallRecording' and 'email.create'. |
| − | |||
| − | Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self explanatory keywords: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'interaction.getInteractions', 'interaction.getByInteractionId', 'interaction.getByBundleId', 'interaction.getByCaseId', 'interaction.attachUserData', 'interaction.updateUserData', 'interaction.deleteUserData', 'voice.dial', 'voice.startCallRecording', 'voice.stopCallRecording', 'voice.pauseCallRecording', 'voice.resumeCallRecording' and 'email.create'. | ||
*:For example, the value for the option <tt>service-client-api.accepted-web-content-origins</tt> could now be: <tt><nowiki>http://my-web-server0, http://my-web-server1 (*), http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*)</nowiki></tt> | *:For example, the value for the option <tt>service-client-api.accepted-web-content-origins</tt> could now be: <tt><nowiki>http://my-web-server0, http://my-web-server1 (*), http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*)</nowiki></tt> | ||
*:In this example, everything is allowed for the <tt><nowiki>http://my-web-server0</nowiki></tt> and <tt><nowiki>http://my-web-server1</nowiki></tt> domains, but for the <tt><nowiki>http://my-web-server2</nowiki></tt> domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial', 'voice.startCallRecording', 'voice.stopCallRecording', 'voice.pauseCallRecording', 'voice.resumeCallRecording' and 'email.create'. So, in addition to filtering by origin, you can also filter by API with a wildcard in in parentheses after the allowed origin. | *:In this example, everything is allowed for the <tt><nowiki>http://my-web-server0</nowiki></tt> and <tt><nowiki>http://my-web-server1</nowiki></tt> domains, but for the <tt><nowiki>http://my-web-server2</nowiki></tt> domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial', 'voice.startCallRecording', 'voice.stopCallRecording', 'voice.pauseCallRecording', 'voice.resumeCallRecording' and 'email.create'. So, in addition to filtering by origin, you can also filter by API with a wildcard in in parentheses after the allowed origin. | ||
| + | *:This option cannot be overridden and must be set in the '''WWEWS Cluster''' application. | ||
<section end="service-client-api.accepted-web-content-origins"/> | <section end="service-client-api.accepted-web-content-origins"/> | ||
<section begin="service-client-api.default-filter-type"/> | <section begin="service-client-api.default-filter-type"/> | ||
Revision as of 14:23, July 10, 2015
Service Client API
service-client-api.accepted-web-content-origins
- Default Value: An empty string
- Valid Values: A comma-separated list of URLs or '*' — for example: 'http://my-web-server-1,http://my-web-server-2' or '*'.
- Changes take effect: When the session is started or restarted.
- Description: Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self explanatory keywords: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'interaction.getInteractions', 'interaction.getByInteractionId', 'interaction.getByBundleId', 'interaction.getByCaseId', 'interaction.attachUserData', 'interaction.updateUserData', 'interaction.deleteUserData', 'voice.dial', 'voice.startCallRecording', 'voice.stopCallRecording', 'voice.pauseCallRecording', 'voice.resumeCallRecording' and 'email.create'.
- For example, the value for the option service-client-api.accepted-web-content-origins could now be: http://my-web-server0, http://my-web-server1 (*), http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*)
- In this example, everything is allowed for the http://my-web-server0 and http://my-web-server1 domains, but for the http://my-web-server2 domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial', 'voice.startCallRecording', 'voice.stopCallRecording', 'voice.pauseCallRecording', 'voice.resumeCallRecording' and 'email.create'. So, in addition to filtering by origin, you can also filter by API with a wildcard in in parentheses after the allowed origin.
- This option cannot be overridden and must be set in the WWEWS Cluster application.
Comments or questions about this documentation? Contact us for support!