This guide connects a browser application to AuthOS. It assumes installation and platform setup are already complete and deliberately does not repeat those operator procedures.
Prerequisites
- A reachable AuthOS base URL supplied by the platform operator
- Node.js 18 or newer and npm
- A registered organization and service for this application
- Allowed browser origins and callback URLs that match the development or production application URL
Choose one client
| Application | Integration entry | Use it when |
|---|---|---|
| React or Next.js client components | @drmhse/authos-react |
You want React providers and sign-in components. |
| Vue 3 or Nuxt | @drmhse/authos-vue |
You want Vue application integration. |
| Framework-agnostic browser code | @drmhse/sso-sdk |
You want direct typed SDK calls and session handling. |
Choose exactly one primary client for the first integration. Pin its exact pre-1.0 version rather than depending on an unconstrained upgrade.
Connect the application
- Follow the linked package entry to install the selected client.
- Put the public AuthOS base URL in the client-side environment configuration.
For example, a Next.js client component can read
NEXT_PUBLIC_AUTHOS_URL; never expose an API key or client secret there. - Initialize the provider or SDK client with that base URL.
- Add one sign-in surface and complete one authentication flow.
- Reload the application and verify that the expected session behavior is restored. Use SDK error handling for failures instead of adding host-installation troubleshooting here.
Completion check
- The browser application reaches the intended AuthOS instance.
- A test user can complete sign-in for the registered organization and service.
- Reload behavior matches the selected client’s documented session behavior.
- Browser configuration contains no server-side API key or client secret.