For example, consider the Mix application "My Omni-Channel Application", which has two environments: DEV and PROD:Įach environment has its own app ID: DEMO-OMNICHANNEL-APP-DEV and DEMO-OMNICHANNEL-APP-PROD, and each app ID has its own set of client credentials.īecause client credentials are linked to an app ID, they provide access to the resources associated to this app ID.Ĭlient IDs for the runtime environment can use these scopes: asr, nlu, dlg, tts, log, asr.wordset, and nlu.wordset. These credentials (that is, the client ID and client secret) are linked to an application ID, which identifies an environment in a Mix application. To access the runtime services and logs, client applications must provide a valid access token that is created using credentials generated from the Mix.dashboard Manage tab. The client credentials to use depend on the integration point. mix-api: Provides access to the Mix.api endpoints and tooling resources.Ĭlient credentials consist of a client ID and a client secret.nlu.wordset: Allows client applications to upload NLU wordsets.asr.wordset: Allows client applications to upload ASR wordsets.tts: Provides access to the TTSaaS runtime API and resources.dlg: Provides access to the DLGaaS runtime API and resources.nlu: Provides access to the NLUaaS runtime API and resources.asr: Provides access to the ASRaaS runtime API and resources.Scope is an OAuth 2.0 mechanism that determines what information the authorized application has access to. Tooling environment: To access the Mix tooling environment, applications provide an access token created using client credentials generated from the Mix.dashboard Profile page.Īs per the OAuth 2.0 standard, there are two important concepts related to authorization: Scopes and client credentials.Runtime environment: To access the ASR, NLU, Dialog, and TTS runtime services as well as runtime logs, applications provide an access token created using client credentials generated from the Mix.dashboard Manage tab.
There are two integration points that require authorization in Mix: To access the Mix runtime and tooling environments, all client applications must provide a valid access token. Nuance Mix uses the OAuth 2.0 protocol for authorization.
0 kommentar(er)
