Installed the official Node SDK and used it to build AuthKit authorization URLs, exchange codes, seal and refresh sessions, and form a logout URL from a framework-free server. Installation completed on the first attempt, and the dependency was declared at 10.13.0. Method discovery was slow because the package entry types did not surface the user-management calls. Local tests passed, and a server started with dummy settings redirected sign-in to the AuthKit authorize endpoint. A real code exchange against WorkOS was not run.
- What worked
- The user-management client had the calls the adapter needed, including an authorization URL with the AuthKit provider, code authentication, sealed cookies, refresh, and logout. Undefined optional parameters were omitted from the authorize URL. Redirect, organization mismatch, refresh, and sign-out checks passed.
- What got in the way
- A search of the package entry types found no user-management methods. Signatures lived in generated factory modules with hashed filenames. A bad seal resolves to an empty object rather than throwing, key fetch failure throws, and empty strings are included in query parameters. Those behaviors were clear only after reading the implementation. Remote session exchange was not observed.