Troubleshooting

Diagnose customer integration issues

Use this guide when an Aura Home embed does not load, authenticate, render, or pass launch validation in a customer portal.

Quick Checks

  1. Open the configured baseUrl directly in a browser tab.
  2. Confirm the portal page, runtime, SDK assets, and identity endpoints all use HTTPS.
  3. Check the browser console for CSP, framing, mixed-content, or certificate errors.
  4. Confirm the token callback returns a valid OIDC/JWT token.
  5. Listen for SDK loaded, ready, configAck, tokenProvided, and error events.

Symptoms and Fixes

SymptomLikely CauseFix
Iframe is blankRuntime URL is wrong, blocked, or not allowed to frame.Open baseUrl directly, check runtime allowlists, and inspect browser console framing errors.
SDK cannot find containerAuraHome.init runs before the container exists.Create <div id="aura-home"></div> before initialization or initialize after the component mounts.
ready never firesRuntime loaded but did not complete SDK handshake.Check allowedOrigin, runtime availability, and console errors inside the iframe if accessible.
SSO returns 401Missing, expired, or invalid token.Validate iss, aud, sub, exp, signature, and runtime OIDC configuration.
SAML works but Aura Home is anonymousSAML session was not bridged into an OIDC/JWT token.Exchange the SAML session through the customer identity gateway and return the OIDC/JWT token from getToken.
Mixed-content warningOne script, iframe, API, stylesheet, or image uses HTTP.Move all integration URLs to HTTPS.
Certificate warningExpired certificate, wrong SAN, or incomplete chain.Renew or reissue the certificate and serve the full chain from the edge.
Theme does not applyThe requested theme.id is not allowed, CSS variable names are invalid, or hosted stylesheet is blocked.Confirm the runtime allowlist or dashboard-published appearance profile, use variables starting with --, and allow the stylesheet URL in CSP.

Debug Event Snippet

const aura = AuraHome.init({
  container: "#aura-home",
  baseUrl: "https://aura.customer-domain.com/",
  allowedOrigin: "https://aura.customer-domain.com",
  auth: {
    mode: "oidc",
    getToken: async () => customerIdentity.getIdToken()
  }
});

["loaded", "ready", "configAck", "tokenProvided", "error"].forEach((eventName) => {
  aura.on(eventName, (event) => {
    console.info("[Aura Home]", eventName, event);
  });
});

What to Send Cadisa Support

  • Portal URL and Aura Home runtime URL.
  • Environment name: development, staging, or production.
  • Browser console errors, with tokens and secrets removed.
  • Network status for the iframe runtime and SDK assets.
  • Token claim summary: issuer, audience, expiry, and subject presence only. Do not send raw tokens.