Authenticated embeds via SSO
What it does
An SSO endpoint creates an embedded session for a user you've already authenticated, so an embedded agent knows who it's talking to.
Before this
An expansion. Embeds could already require a login. What they could not do was accept one you had already performed, so your signed-in users signed in a second time to talk to the agent.
Why it matters
Your app's logged-in users don't have to log in a second time, and the agent can safely personalise on identity you vouched for.
How it works
Your site signs a token for a user it has already authenticated; Pickaxe verifies it against a public key you registered and opens an embedded session as that user. No second login, and the agent knows who it is talking to.
- Where
- Settings → Deploy → Embed SSO.
- WordPress
- A connector plugin you install, then finish setup from its Connect to Pickaxe button.
- Any other host
- Manual mode: configure the issuer, key ID, public key, and allowed origins yourself.
- Plan
- Pro.
Identity you vouched for is what makes personalisation safe. Without it, an embedded agent either treats everyone as anonymous or trusts whatever the page tells it about who is watching.