jac-cl-auth

Import jacLogin and jacSignup from @jac/runtime and await both in order. jacSignup returns a dict with a success key, while jacLogin returns a bool, so check signup_result["success"] and the login boolean separately.

Wrap protected pages in the AuthGuard component from @jac/runtime with a redirect prop, typically in a layout file for a route group. For one-off cases, use an inline jacIsLoggedIn() check returning a Navigate component.

jacSignup creates the account but does not establish a session. You must await jacLogin with the same credentials before any def:priv call, otherwise the request reaches the server without the session cookie and returns 401 Unauthorized.

jacSignup returns a dict shaped {"success": bool, ...} which is always truthy, so if not signup_result never detects failure. Check the success key explicitly with if not signup_result["success"].

Yes. Configure the provider under [scale.sso.google] in jac.toml on the server, then call await jacSsoLogin("google") on the client, which returns a bool once the token lands. Callback pages can use jacSetToken to store a token directly.

In client Jac, var = await fn() can compile to a tightly scoped JS let, causing ReferenceError at the later if-check. Pre-declare the variable with a type and default at the top of the function, then assign the awaited result.