Extend Orchestration Fails To Get ISU Token From Octopaas With Status 303
What does "Extend Orchestration Fails To Get ISU Token From Octopaas With Status 303" mean in Workday Extend?
An Extend orchestration step that calls a Workday API as an Integration System User could not get a token for that ISU. The ISU itself can sign in; the token service for the app redirected instead of issuing a token, usually because the API client linked to the ISU for this tenant is stale or not valid here.
Quick fix
Have a Developer Site Company Administrator delete the API client for this app and tenant in the Console, create a new one from the ISU row in App Manager, authorize the tenant on it, and rerun.
Permanent fix
Treat the ISU API client as part of each promotion: one client per app, environment and tenant, created from App Manager after the ISU is assigned and authorized for that tenant in the Console. When an ISU is removed from an app, delete its client in the Console at the same time.
Troubleshooting
- Run the Signons and Attempted Signons report for the ISU. A successful sign-in at launch time means the account, password, MFA and authentication policy are fine, so stop changing them.
- In App Manager, open the app and check the Integration System Users section: the ISU row should show a Client ID.
- On the Developer Site Console under API Clients, find the client for this app, environment and tenant. Confirm it exists only once and that the tenant is in its Authorized Tenants.
- If the app was promoted to this tenant and the client predates the promotion, or the ISU was removed and added again, the client in the Console may be orphaned. Delete that one client (leave other environments alone), then use Create API Client on the ISU row in App Manager.
- Authorize the tenant on the new client and launch the integration again.