Web sign-in
The public SDK's default entries provide resource and lifecycle clients. They do not replace your application's OIDC login library, callback handler, or session store.
Use a maintained OIDC implementation
Use Authorization Code with PKCE S256. Register an exact application origin and redirect URI. Generate one-use state and nonce, persist a bounded authorization transaction server-side, and validate the returned issuer, client, signature, audience, state, nonce, times, and the applicable token-binding claims through the maintained library and accepted provider profile.
Do not accept an issuer, redirect destination, product, or expected actor from arbitrary callback/request fields. Reject stale, replayed, mismatched, cancelled, and unsupported callback transactions.
Create the application session
Only admit an application session after callback validation and your explicit product membership checks. Keep session identifiers, tokens, and refresh credentials out of browser-readable storage and logs. Use a secure, HttpOnly, host-only cookie with the appropriate SameSite/CSRF policy for your application. Bound its lifetime to the accepted session/token policy.
Connect the verified actor
A product connection uses a separately registered resource client and a token intended for the Identity API. Retain the original verified actor server-side, and require the resource ceremony to match that actor before calling connectProduct.
import { IdentityProductUserClient } from '@tracecove/identity';
const client = await IdentityProductUserClient.connect(userConfiguration);
const connection = await client.connectProduct({
accessToken: verifiedResourceAccessToken,
expectedActor: { subject, brokerSessionId, authTime },
idempotencyKey: durableCommandKey,
});The variables represent independently validated server state, not fields to copy from a browser. Configuration for the default resource profile requires connections:write, the exact Identity API audience, and no client secret.
Keep sign-out scopes distinct
Application sign-out invalidates that application's session. It does not by itself prove that another product session or provider session ended. Account-wide commands and their provider completion require the selected environment's explicit capability and acceptance. Do not present an app-local result as universal logout.
Hosted preview
Hosted staging has a tested reference HTTP login/callback and app sign-out flow using synthetic accounts. A complete browser journey, actual product adoption, and production readiness are separate evidence scopes. Preview registration is arranged with Tracecove; the documentation host does not provide a public sign-in endpoint.
Public preview 0.7.0-preview.1 · Not production ready · Status and releases