jac-cl-auth

Import jacLogin and jacSignup from @jac/runtime and await both in an async handler. jacLogin returns a bool, while jacSignup returns a dict whose success key must be checked. Always call jacLogin after jacSignup because signup alone does not establish a session.

Wrap protected pages in the AuthGuard component from @jac/runtime with a redirect to the login page. With file-based routing, place AuthGuard in a layout so every page in that route group requires login; use inline jacIsLoggedIn checks only for one-off cases.

jacSignup creates the account but does not establish a session, so subsequent def:priv calls arrive unauthenticated. Await jacLogin with the same credentials after signup, then await the privileged call, in that fixed order.

jacSignup returns a dict shaped {"success": bool, ...} that is always non-empty and therefore truthy. Check the success key explicitly with if not signup_result["success"], and type the variable as dict, not bool, to avoid E1001 compile errors.

Yes. Configure the provider under [scale.sso.google] in jac.toml on the server, which exposes /sso/{platform}/login and callback endpoints. On the client, await jacSsoLogin("google") to hand off to the provider, or use jacSetToken to store a token directly.

Assigning an await result without pre-declaring the variable can compile to a tightly scoped JS let, so the later if-check throws ReferenceError. Declare the variable with a default at the top of the function, such as ok: bool = False, then assign the awaited result.