atSpark embed test console
Try signing a user in to your embedded dashboards the way your own website will, and check that it behaves safely.
This page runs on
Connect
Tell the console which organization and connection to use. Only the fields for your sign-in method are shown.
More options second user, extra checks, custom address
Open your dashboards
Signs the user in and shows what they would see inside your page.
Nothing open yet. Press Open dashboards to sign the user in.
Second user compare what two people see
Developer tools messages between this page and atSpark
Messages received from atSpark
Check that it is safe
Runs requests that should be refused (wrong secret, unknown site, replayed ticket) and confirms atSpark refuses them. A refusal counts as a pass.
Show individual checks choose which to run
Also check by hand
- Not framed: opening the session link in its own tab must say "This link has expired" and must not use up the ticket.
- Wrong parent site: host this file on an address that is not in Allowed sites, open the dashboards, and the frame must be blocked.
- Different parent than the ticket: get a ticket for site A, then open it from allowed site B. atSpark must show the expired message.
- Revoking access: remove the Allowed site, or turn the connection off, then use an already-issued ticket. It must fail.
- Session expiry: leave a dashboard open past the session lifetime. atSpark sends
atspark:session-expired, and your page must request a new ticket and reload.
See it on a customer site
A sample website with its own header and menu, built from the dashboards the user is allowed to see. atSpark shows only the report area.
Not signed in
If something fails
- Everything is refused (401) or the frame stays blank: this page's address is not in Allowed sites, the connection is off, or the Embedding add-on is off.
- Sign-in is rejected (400): the connection restricts data by attribute and the attributes you entered do not match.
- Tableau says "missing data scope" (403): the connection has no attribute mappings. Tableau needs at least one.
- No
atspark:readymessage: check the browser console for a blocked frame, and that the atSpark address is the real app address. - A ticket works only once and lasts 60 seconds. Reusing it, or reloading inside the frame, fails on purpose. Your page requests a new ticket and reloads the frame.
This console asks for the secret and license key only because it is a test tool. On your real website they stay on your server, and the browser only ever receives the ticket.