connections.yaml
.
connections.yaml
file.
<workday-app-id>
- The ID of the Workday web page that hosts the embedded chat.{tenant-id}
- The tenant ID of the Microsoft Entra.connections.yaml
file. See Importing Connection using a Connection file for more information.
<workday-app-id>
- The ID of the Workday web page that hosts the embedded chat.<env>
- The environment type, draft or live.<token-url>
- Token URL provided in your Workday API registration.grant_type
. You can remove the requested_token_use
and requested_token_type
from the code.
<workday-app-id>
- The ID of the Workday web page that hosts the embedded chat.<env>
- The environment type, draft or live.{tenant-id}
- The tenant ID of the Microsoft Entra.<entra-client-id>
- The Client ID of the Microsoft Entra.<entra-client-secret>
- The Client Secret of the Microsoft Entra.orchestrate tools import
command with the --app-id
argument to associate the Workday connection with the tool. See the steps:
<workday-app-id>
- The ID of the Workday web page that hosts the embedded chat.<path-to-file>
- The path, name, and extension of the file<workday-app-id>
- The ID of the Workday web page that hosts the embedded chat.<env>
- The environment type, draft or live.<client-id-workday>
- Client ID provided in your Workday API registration.<token-url>
- Token URL provided in your Workday API registration.createJWT.js
and embed.html
files. You can use the examples that are provided in the following tabs as templates for each file.<wo_tenant_id>
and <sso_token>
with appropriate information.Parameter | Description |
---|---|
<wo_tenant_id> | Your watsonx Orchestrate tenant ID. |
<sso_token> | The SSO token obtained from the Entra ID. |
Issue | Possible cause | Resolution |
---|---|---|
401 Unauthorized | Invalid SAML assertion or client credentials | Check your app’s API client credentials |
invalid_grant | Redirect URI mismatch | Verify your IDP app settings |
No response in embedded chat | Chat not embedded correctly | Verify the script and app ID |