Intastellar Accounts is the sign-in layer for Intastellar products. The articles below help you add web sign-in so visitors can use the same account across Intastellar services.

help.intastellarsolutions.com is where these articles live (search, articles, and sometimes signed-in tools such as API keys). Anything specific to your servers or hosting stays in your internal notes.

Start here (owners & integrators)

• Owning the login experience — Site owner checklist · Glossary · Browser & storage · Identity & APIs
• Implementing sign-in — Integrator overview · Debugging sign-in

Choose how you build

On your own website or app:

Situation	Start here
React app	Intastellar Sign-In — React and JavaScript — uses the official npm package.
Simple site (HTML/CSS/JS, no React)	Plain HTML, CSS, and JavaScript — same behaviour as the SDK, step by step (replaces the old js-docs pages).
You are wiring OAuth yourself (custom stack, mobile, or server)	Getting started for the checklist, then Authorization code flow.

All articles (Sign in — Web)

• Getting started — register the app, choose public vs confidential, plan redirects and sessions before coding.
• Intastellar Sign-In — React and JavaScript — React patterns and where to get real settings (examples use placeholders only).
• Plain HTML, CSS, and JavaScript — static sites, popups, cookies; optional bundler notes.
• Authorization code flow — browser redirect, state, PKCE, exchanging the code (custom setups).
• Redirect URIs and callbacks — allowed URLs and “it worked yesterday” mistakes.
• Sessions, cookies, and tokens — what lives on your domain vs Intastellar’s.
• SPAs and JavaScript clients — no secret in the browser, PKCE, safer patterns.
• Server-side (confidential) clients — exchange the code on your server with a client secret.
• Logout, errors, and troubleshooting — sign out, popups, typical errors.

Related

• Help — search, shortcuts, and cookie-banner help if you use Consents on the same site.
• Changelog — @intastellar/signin-sdk-react on npm and GitHub releases.
• Intastellar Consents (cookie banner) — consent UI on the same property.

Old bookmarks

Some links still use developers.intastellarsolutions.com (including …/identity/sign-in/web/docs/js-docs). Prefer HTTPS redirects to help.intastellarsolutions.com, and update allowed redirect / login URIs on your Intastellar client so they match what you use in production and staging.

Frequently asked questions

Which article should I open first?

• React → React and JavaScript.
• No framework, just a website → Plain HTML, CSS, and JavaScript.
• OAuth / server / “we’re building it ourselves” → Getting started, then Authorization code flow.

“Redirect URI mismatch” or login returns to the wrong place

Almost always a registration mismatch (wrong URL, http vs https, or trailing slash). See Redirect URIs and callbacks.

Popup never appears or is blocked

Common with the SDK and plain JS flows. See Logout, errors, and troubleshooting.

Do I put the client secret in the website?

No in the browser. Secrets belong on a server you control. See Server-side (confidential) clients and SPAs and JavaScript clients.