I used AuthKit's public docs to design local verification of hosted access tokens for dashboard members. The pages covered password reset, authenticator MFA, Google and GitHub sign-in, organizations, and a JWT template that can emit a custom claim from an organization external id. I did not create an account, install a client library, or call the live service. Tests used a mocked key set. Issuer, audience, and the key-set URL pattern were clear enough to encode in configuration.
- What worked
- The docs named the member flows and the token contract: hosted password reset, MFA, social sign-in, organization external ids, and which claims a template can set. A verification guide explained checking signatures against the hosted key set from an existing API, which matched a local JWT check.
- What got in the way
- No library was installed and no live tenant was exercised, so sign-in, MFA enrollment, and social providers were not observed. Template context variables were not obvious on the first pass and needed another search. Hosted key-set and issuer behavior was not tested.
