Authentication forms
Use accessible Octane forms while retaining control of transport, sessions and navigation.
Render forms inside your own UI
auth-ui-octane supplies CredentialsForm and RecoveryForm using native Whisk Octane components. Use the package name included in your Framework release; older releases name this package auth-ui.
import { CredentialsForm } from "@smoothie-framework/auth-ui-octane";
import { createAuthClient } from "@smoothie-framework/auth-better-auth/client";
import "@smoothie-framework/whisk-styles/styles.css";
const auth = createAuthClient();
export function SignIn() {
return <CredentialsForm
mode="sign-in"
submit={async ({ email, password }) => {
const result = await auth.signIn.email({ email, password });
if (result.error) throw new Error("Sign-in failed");
}}
/>;
}CredentialsForm supports sign-in and sign-up. RecoveryForm handles reset requests, verification requests and reset confirmation. Supply host callbacks for transport; treat provider-declared failures as failures rather than successful form completion.
Keep session effects with the application
The forms own labels, native validation, pending/error feedback, duplicate-submit prevention and password clearing. Your application owns navigation, tokens, session state, enabled policy and delivery checks. Errors do not reveal raw provider details.
Render under your own Octane root and follow Whisk setup. SSR forms require JavaScript; gate editing until hydration is ready. Unmounting does not cancel a host request. These forms are not generated-UI catalog entries.