Configure Custom ThingWorx Scope
|
|
If the ThingWorx scopes have not been customized, you can ignore this section.
|
The Experience Service must access ThingWorx on behalf of the user. For example, you may need to retrieve sensor data from ThingWorx to display in a connected experience. To support this, the Experience Service must obtain authorization from the user for the ThingWorx OAuth scope. Therefore, the correct ThingWorx scope must be specified in the Experience Service configuration.
The installer automatically configures the Experience Service to use the default ThingWorx scope (THINGWORX). If your ThingWorx server uses the default scope, no changes are required.
If your
ThingWorx server has been configured to use custom scopes, see the “Authentication” section in
Configuration Parameters for instructions on how to manually configure the appropriate ThingWorx scopes.
To validate what scope your ThingWorx server is using, check the globalScopes parameter in the ResourceServerSettings.json file on your ThingWorx server.
|
|
This manual configuration should be done after you have finished installing the Experience Service.
|
