errors / raas / raas-login-page-instead-of-data

RaaS Returns a Login Page Instead of Report Data

✓ Verified RaaS (Reports as a Service)
The error Expected XML/JSON response but received: <!DOCTYPE html><html><head><title>Workday Sign In</title>...

What it means

The caller wasn't authenticated, so instead of report data the RaaS URL returned Workday's HTML sign-in page. The consuming system then fails parsing 'invalid XML/JSON' — but the real problem is authentication, not the report.

Troubleshooting

  1. Check the auth on the request: Basic auth with user@tenant formatting, or a valid OAuth bearer token — a missing or malformed header silently falls back to the login page.
  2. Confirm the ISU isn't locked out and its password hasn't expired.
  3. Verify the ISU has access to the report: the report must be shared with the ISU (or its group) and enabled for web service access.
  4. Test the exact URL with curl/Postman using the integration's credentials to reproduce outside the consuming system.
⚡ Quick fix

Fix the credential formatting (username@tenant), unlock/reset the ISU if needed, and re-test the URL until raw XML/JSON comes back.

✓ Permanent fix

Switch RaaS consumers to OAuth where possible, monitor for HTML content-type in responses (it always means auth fell through), and document the report-sharing + web-service-enablement steps as part of publishing any new RaaS report.