SpiderPublish just leveled up. The Authentication category in the section library now gives you designable login, forgot-password, and reset-password pages that don't just look the part — they actually sign people in. Real app, real login.
One brick, two identity worlds
Each Authentication component renders a single <spideriq-auth> element with a closed shadow DOM, so the password field is never readable from the host page. A required auth_target prop decides what the form signs into: “dashboard” signs a user into the SpiderIQ dashboard, while “site_members” signs into your site’s own members area. Two separate identity worlds, one designable brick.
Sign-in works end to end now
This is the part that changed. With auth_target=“dashboard”, a login brick on your own domain now logs a user straight into the SpiderIQ dashboard. Under the hood, a credential check returns a single-use, short-lived one-time code, which a host-only handoff trades for a first-party session on the dashboard origin — no shared cross-domain cookies, ever. OAuth always runs on the central origin, and the closed shadow root keeps the password unreadable by your page.
The page itself is 100% yours: design the chrome — layout, hero, branding, background, copy — however you like, and embed the brick where the form goes. Only the form interior is styled, through theme tokens.
How to add one
Browse the library (category=authentication), drop spideriq/auth-login onto a /login page, set auth_target, theme it to match your brand, then publish and deploy. Pair it with the forgot-password and reset-password bricks for the full flow.
What will you build?
A members-only area behind your content. A branded login that opens straight into the dashboard. A full agency front door on your own domain. Real app, real login — what will you build with SpiderPublish?