Altium 365 Auth¶
Client libraries for Altium 365 authentication — OAuth2/OpenID Connect with PKCE, the Altium ActionWait desktop sign-in flow, workspace token-exchange, refresh/revocation, and Gov Cloud — built to a single language-neutral specification and held to one shared conformance suite.
The spec is the source of truth; each library is a hand-written, idiomatic implementation that is validated by the same vectors. Change the contract once, and every library's CI proves it still conforms.
Get started¶
Pick the flow that matches your application:
- Desktop / on-prem / native (can't host a redirect) → Desktop & on-prem apps — browser sign-in with PKCE over ActionWait.
- Web / server backends (host a redirect) → Web & server apps — the standard authorization-code redirect flow.
New to Altium Identity? Start with the Overview, then Register your application.
Libraries¶
Full API reference and examples for each library are on this site (the Libraries tab):
| Library | Docs |
|---|---|
@altium-developer/a365-auth |
TypeScript |
Altium.Auth |
.NET |
Both are in preview — the API may change as the spec and libraries evolve.
How it stays in sync¶
The conformance vectors are the enforcement layer: every library
runs the same spec/conformance/vectors.json and asserts the same requests and
outcomes, so the implementations can't drift. The normative behavior lives in the
integration spec.
Topics¶
- Gov Cloud — Commercial vs Gov and the
secure=1two-token model - Access token claims — what's inside a token (
iss,workspaceId,secure, scopes)