Branding
Hosted OAuth applications
Register a meaningful application name, icon/logo, website, privacy URL, terms URL, and exact redirect URIs in OAuth Clients. These identify your app during sign-in and consent. The management API accepts name, icon, uri, logoUri, tosUri, policyUri, contacts, and themeOrigin alongside the client registration fields.
A custom theme origin is client metadata used by the hosted flow; it is not authorization to load arbitrary scripts or change the issuer's trust boundary. Use an origin you control and test the actual login/consent UI after changing it. See client registration.
Self-hosted issuer branding
The auth server's lib/brand-config.ts exposes a small BrandConfig with name and optional logoUrl:
| Environment variable | Effect |
|---|---|
NEXT_PUBLIC_BRAND_NAME | Display name; default Sigma Auth |
NEXT_PUBLIC_BRAND_LOGO_URL | Optional custom logo URL |
The old example exporting navigation links, copyright, and React logo elements from that file did not match the implementation. Legal text, email branding, navigation, and product copy have their own source files and require a deliberate source change.
Theme colors use the CSS variables in app/globals.css; preserve the current color format and light/dark variants. Email colors are generated in lib/brand.ts. Test contrast, keyboard focus, logo dimensions, and both themes before deployment.