@strivacity/sdk-nuxt

A Nuxt 3 module that integrates Strivacity's policy-driven authentication journeys into your application using the OAuth 2.0 PKCE flow. Supports redirect, popup, native, and embedded modes.

See our Developer Portal to get started with developing with the Strivacity product.

Overview

This SDK allows you to integrate Strivacity's policy-driven journeys into your Nuxt 3 application. It registers itself as a Nuxt module and automatically provides the useStrivacity composable and StyLoginRenderer component throughout your application without needing explicit imports. The SDK uses the OAuth 2.0 PKCE flow to authenticate with Strivacity. For detailed configuration options, available modes, and advanced usage refer to the @strivacity/sdk-core documentation.

Demo Application

• Example app

Requirements

• Nuxt: 3+

Install

npm install @strivacity/sdk-nuxt

Usage

Initialization

Register the SDK as a Nuxt module in nuxt.config.ts:

// nuxt.config.ts
export default defineNuxtConfig({
	modules: ['@strivacity/sdk-nuxt'],
	strivacity: {
		mode: 'redirect', // or 'popup', 'native', 'embedded'
		issuer: 'https://<YOUR_DOMAIN>',
		scopes: ['openid', 'profile'],
		clientId: '<YOUR_CLIENT_ID>',
		redirectUri: '<YOUR_REDIRECT_URI>',
	},
});

Use the auto-imported useStrivacity composable in any component to access authentication state:

<script setup>
const { loading, isAuthenticated, idTokenClaims } = useStrivacity();
</script>

Redirect / Popup mode

In redirect mode the user is taken to the identity provider in the same window; in popup mode authentication happens in a popup. Both are initiated the same way from code.

Login page example

<script setup>
import { onMounted } from 'vue';

const { login } = useStrivacity();

onMounted(() => {
	login();
});
</script>

<template>
	<section>
		<h1>Redirecting...</h1>
	</section>
</template>

Callback page example

The callback page handles the response from the identity provider. It calls handleCallback() and redirects to /profile on success:

<script setup>
import { onMounted } from 'vue';

const router = useRouter();
const { handleCallback } = useStrivacity();

onMounted(async () => {
	try {
		await handleCallback();
		await router.push('/profile');
	} catch (error) {
		console.error('Error during callback handling:', error);
	}
});
</script>

<template>
	<section>
		<h1>Logging in...</h1>
	</section>
</template>

Profile page example

<script setup>
const { loading, isAuthenticated, accessToken, accessTokenExpired, accessTokenExpirationDate, idTokenClaims, refreshToken } = useStrivacity();
</script>

<template>
	<section>
		<h1 v-if="loading">Loading...</h1>
		<dl v-else>
			<dt><strong>accessToken</strong></dt>
			<dd>
				<pre>{{ JSON.stringify(accessToken) }}</pre>
			</dd>
			<dt><strong>refreshToken</strong></dt>
			<dd>
				<pre>{{ JSON.stringify(refreshToken) }}</pre>
			</dd>
			<dt><strong>accessTokenExpired</strong></dt>
			<dd>
				<pre>{{ JSON.stringify(accessTokenExpired) }}</pre>
			</dd>
			<dt><strong>accessTokenExpirationDate</strong></dt>
			<dd>
				<pre>{{ accessTokenExpirationDate ? new Date(accessTokenExpirationDate * 1000).toLocaleString() : JSON.stringify(null) }}</pre>
			</dd>
			<dt><strong>claims</strong></dt>
			<dd>
				<pre>{{ JSON.stringify(idTokenClaims, null, 2) }}</pre>
			</dd>
		</dl>
	</section>
</template>

Logout page example

The postLogoutRedirectUri parameter is optional and specifies where users are redirected after logout. This URI must be configured in the Admin Console as an allowed post-logout redirect URI.

<script setup>
import { onMounted } from 'vue';

const router = useRouter();
const { isAuthenticated, logout } = useStrivacity();

onMounted(async () => {
	if (isAuthenticated.value) {
		await logout({ postLogoutRedirectUri: location.origin });
	} else {
		await router.push('/');
	}
});
</script>

<template>
	<section>
		<h1>Logging out...</h1>
	</section>
</template>

Component example

<script setup>
import { computed } from 'vue';

const { isAuthenticated, idTokenClaims, login, logout } = useStrivacity();
const name = computed(() => `${idTokenClaims.value?.given_name} ${idTokenClaims.value?.family_name}`);
</script>

<template>
	<div v-if="isAuthenticated">
		<div>Welcome, {{ name }}!</div>
		<button @click="logout()">Logout</button>
	</div>
	<div v-else>
		<div>Not logged in</div>
		<button @click="login()">Log in</button>
	</div>
</template>

Native mode

In native mode the auto-imported StyLoginRenderer component renders the authentication UI inline using your custom widget components. You can define custom components for each input type; see Example widgets.

The example widgets use SCSS for styling and Luxon for date handling:

npm install sass luxon
npm install --save-dev @types/luxon

import CheckboxWidget from './checkbox.widget.vue';
import DateWidget from './date.widget.vue';
import InputWidget from './input.widget.vue';
import LayoutWidget from './layout.widget.vue';
import MultiSelectWidget from './multiselect.widget.vue';
import PasscodeWidget from './passcode.widget.vue';
import LoadingWidget from './loading.widget.vue';
import PasswordWidget from './password.widget.vue';
import PhoneWidget from './phone.widget.vue';
import SelectWidget from './select.widget.vue';
import StaticWidget from './static.widget.vue';
import SubmitWidget from './submit.widget.vue';

export const widgets = {
	checkbox: CheckboxWidget,
	date: DateWidget,
	input: InputWidget,
	layout: LayoutWidget,
	loading: LoadingWidget,
	passcode: PasscodeWidget,
	password: PasswordWidget,
	phone: PhoneWidget,
	select: SelectWidget,
	multiSelect: MultiSelectWidget,
	static: StaticWidget,
	submit: SubmitWidget,
};

Login page example

The login page extracts session_id and optionally language from the URL on load, cleans up the URL, and passes them to the renderer. When a session_id is present the renderer calls startSession(sessionId) to resume the existing flow instead of starting a new one. When a language parameter is present it is passed to the renderer which uses it for the authentication UI and emits the resolved language back via v-model:language.

<script setup lang="ts">
import { ref } from 'vue';
import type { FallbackError, LoginFlowState } from '@strivacity/sdk-nuxt';
import { widgets } from '~/components/widgets';

const router = useRouter();
const sessionId = ref<string | null>(null);
const language = ref<string | null>(null);

if (window.location.search !== '') {
	const url = new URL(window.location.href);
	sessionId.value = url.searchParams.get('session_id');

	if (url.searchParams.has('language')) {
		language.value = url.searchParams.get('language');
	}

	url.search = '';
	history.replaceState({}, '', url.toString());
}

const onLogin = async () => {
	await router.push('/profile');
};

const onFallback = (error: FallbackError) => {
	if (error.url) {
		window.location.href = error.url.toString();
	} else {
		alert(error);
	}
};

const onError = (error: string) => {
	alert(error);
};

const onGlobalMessage = (message: string) => {
	alert(message);
};

const onBlockReady = ({ previousState, state }: { previousState: LoginFlowState; state: LoginFlowState }) => {
	console.log('previousState', previousState);
	console.log('state', state);
};
</script>

<template>
	<StyLoginRenderer
		v-model:language="language"
		:widgets="widgets"
		:session-id="sessionId"
		@fallback="onFallback"
		@login="onLogin"
		@error="onError"
		@global-message="onGlobalMessage"
		@block-ready="onBlockReady"
	/>
</template>

Callback page example

When a session_id is present in the URL the native flow is resumed by forwarding it to the login page. Otherwise the standard handleCallback() path is used:

<script setup>
import { onMounted, computed } from 'vue';

const query = computed(() => Object.fromEntries(new URLSearchParams(window.location.search)));
const router = useRouter();
const { handleCallback } = useStrivacity();

onMounted(async () => {
	const url = new URL(location.href);
	const sessionId = url.searchParams.get('session_id');

	if (sessionId) {
		await router.push(`/login?session_id=${sessionId}`);
	} else {
		try {
			await handleCallback();
			await router.push('/profile');
		} catch (error) {
			console.error('Error during callback handling:', error);
		}
	}
});
</script>

<template>
	<section v-if="query.error">
		<h1>Error in authentication</h1>
		<div>
			<h4>{{ query.error }}</h4>
			<p>{{ query.error_description }}</p>
		</div>
	</section>
	<section v-else>
		<h1>Logging in...</h1>
	</section>
</template>

Entry page example

The entry page processes flows started by an external process (e.g. password reset) by calling entry() to extract the necessary parameters to resume the flow and forwarding them to the callback page:

<script setup>
import { onMounted } from 'vue';

const router = useRouter();
const { entry } = useStrivacity();

onMounted(async () => {
	try {
		const data = await entry();

		if (data && Object.keys(data).length > 0) {
			await router.push(`/callback?${new URLSearchParams(data).toString()}`);
		} else {
			await router.push('/');
		}
	} catch (error) {
		console.error('Entry failed:', error);
		await router.push('/');
	}
});
</script>

Profile page example

Same as the profile page example in redirect/popup mode.

Logout page example

Same as the logout page example in redirect/popup mode.

Embedded mode

In embedded mode the <sty-login> web component (loaded via bundle.js from the cluster) handles rendering. Import the bundle in a Nuxt plugin to register the Strivacity web components:

// plugins/strivacity-bundle.client.ts
export default defineNuxtPlugin(() => {
	const config = useRuntimeConfig();
	void import(`${config.public.strivacity.issuer}/assets/components/bundle.js`);
});

// nuxt.config.ts
export default defineNuxtConfig({
	modules: ['@strivacity/sdk-nuxt'],
	strivacity: {
		mode: 'embedded',
		issuer: 'https://<YOUR_DOMAIN>',
		scopes: ['openid', 'profile'],
		clientId: '<YOUR_CLIENT_ID>',
		redirectUri: '<YOUR_REDIRECT_URI>',
	},
});

Logging

The SDK supports optional logging to help you debug authentication flows and monitor SDK behavior. You can enable the built-in console logger or provide your own custom logger implementation.

Using the Default Logger

Enable the default console logger by adding the logging option in nuxt.config.ts:

import { DefaultLogging } from '@strivacity/sdk-nuxt';

export default defineNuxtConfig({
	modules: ['@strivacity/sdk-nuxt'],
	strivacity: {
		mode: 'redirect',
		issuer: 'https://<YOUR_DOMAIN>',
		scopes: ['openid', 'profile'],
		clientId: '<YOUR_CLIENT_ID>',
		redirectUri: '<YOUR_REDIRECT_URI>',
		logging: DefaultLogging,
	},
});

Creating a Custom Logger

Implement the SDKLogging interface and pass your class to the logging option:

import type { SDKLogging } from '@strivacity/sdk-nuxt';

export class MyLogger implements SDKLogging {
	xEventId?: string;

	debug(message: string): void {
		console.debug(this.xEventId ? `[${this.xEventId}] ${message}` : message);
	}

	info(message: string): void {
		console.info(this.xEventId ? `[${this.xEventId}] ${message}` : message);
	}

	warn(message: string): void {
		console.warn(this.xEventId ? `[${this.xEventId}] ${message}` : message);
	}

	error(message: string, error: Error): void {
		console.error(this.xEventId ? `[${this.xEventId}] ${message}` : message, error);
	}
}

The SDKLogging interface requires debug, info, warn, and error methods. The optional xEventId property, when set by the SDK, provides a correlation ID to trace related log messages across the authentication flow.

HTTP Client

The SDK uses a built-in fetch-based HTTP client for all requests. You can replace it with your own implementation by extending SDKHttpClient and passing your class via the httpClient option. This is useful when you need to attach custom headers (e.g. x-sty-app-id) to every outgoing request or route traffic through a proxy.

Adding custom headers to every request

// nuxt.config.ts
import { SDKHttpClient, type HttpClientResponse } from '@strivacity/sdk-nuxt';

class CustomHttpClient extends SDKHttpClient {
	async request<T>(url: string, options?: RequestInit): Promise<HttpClientResponse<T>> {
		const mergedOptions: RequestInit = {
			...options,
			headers: {
				'x-sty-app-id': 'my-app',
				...(options?.headers as Record<string, string>),
			},
		};

		const response = await fetch(url, mergedOptions);

		return {
			headers: response.headers,
			ok: response.ok,
			status: response.status,
			statusText: response.statusText,
			url: response.url,
			json: async () => (await response.json()) as T,
			text: async () => await response.text(),
		};
	}
}

export default defineNuxtConfig({
	modules: ['@strivacity/sdk-nuxt'],
	strivacity: {
		// ...other options
		httpClient: CustomHttpClient,
	},
});

Any header you add inside request() is automatically included in every SDK request

CORS configuration

For custom request headers to reach the Strivacity cluster, the cluster must be configured to explicitly allow them. Add the header name(s) to the Access-Control-Allow-Headers list in the cluster settings. Without this, browsers will block the preflight OPTIONS request and the SDK call will fail with a CORS error.

Access-Control-Allow-Headers: x-sty-app-id, <any other custom headers>

API Documentation

useStrivacity composable

useStrivacity<T extends PopupContext | RedirectContext | NativeContext>(): T;

The composable returns a different context type depending on the mode configured in nuxt.config.ts.

Shared properties (all modes)

• sdk: RedirectFlow | PopupFlow | NativeFlow: The underlying SDK flow instance.
• loading: Ref<boolean>: true while the session is being initialized.
• options: SDKOptions: The configured SDK options.
• isAuthenticated: Ref<boolean>: true when the user has a valid session.
• idTokenClaims: Ref<IdTokenClaims | null>: Claims from the ID token, or null if not authenticated.
• accessToken: Ref<string | null>: The current access token.
• refreshToken: Ref<string | null>: The current refresh token.
• accessTokenExpired: Ref<boolean>: true when the access token has expired.
• accessTokenExpirationDate: Ref<number | null>: Expiration timestamp (Unix seconds) of the access token.

Type: RedirectContext

• login(options?: LoginOptions): Promise<void>: Initiates login by redirecting to the identity provider.
• register(options?: RegisterOptions): Promise<void>: Initiates registration using a redirect flow.
• refresh(): Promise<void>: Refreshes the user's session.
• revoke(): Promise<void>: Revokes the current session tokens.
• logout(options?: LogoutOptions): Promise<void>: Logs the user out via redirect.
• handleCallback(url?: string): Promise<void>: Processes the authorization callback after redirect.
• entry(): Promise<Record<string, string>>: Processes an externally-initiated flow URL and returns the parameters needed to resume the flow.

Type: PopupContext

• login(options?: LoginOptions): Promise<void>: Initiates login using a popup window.
• register(options?: RegisterOptions): Promise<void>: Initiates registration using a popup.
• refresh(): Promise<void>: Refreshes the user's session.
• revoke(): Promise<void>: Revokes the current session tokens.
• logout(options?: LogoutOptions): Promise<void>: Logs the user out via popup.
• handleCallback(url?: string): Promise<void>: Processes the authorization callback.
• entry(): Promise<Record<string, string>>: Processes an externally-initiated flow URL.

Type: NativeContext

• login(options?: LoginOptions): Promise<NativeFlowHandler>: Initiates login using the native flow.
• register(options?: RegisterOptions): Promise<NativeFlowHandler>: Initiates registration using the native flow.
• refresh(): Promise<void>: Refreshes the user's session.
• revoke(): Promise<void>: Revokes the current session tokens.
• logout(options?: LogoutOptions): Promise<void>: Logs the user out via redirect.
• handleCallback(url?: string): Promise<void>: Processes the authorization callback.
• entry(): Promise<Record<string, string>>: Processes an externally-initiated flow URL.

StyLoginRenderer component

Auto-imported in native mode to render the authentication UI with your own widget components.

Props

• params?: NativeParams: Additional parameters for the native login flow.
• widgets?: PartialRecord<WidgetType, Vue.Component>: Custom Vue components for each widget type used in the flow.
• sessionId?: string | null: Session ID for resuming an existing authentication session.
• language?: string | null: Language tag (e.g. "en-US") for the authentication UI. Defaults to navigator.language. Supports two-way binding via v-model:language — after the session starts the component emits the resolved language back to the parent. See the Translations page to learn about language precedence implemented by the product.

Events

• @login: Emitted on successful authentication. Receives IdTokenClaims | null.
• @fallback: Emitted when the native flow needs to fall back to redirect. Receives FallbackError with a fallback URL.
• @error: Emitted when an error occurs during authentication.
• @global-message: Emitted when the flow wants to display a global message (e.g. account lockout warning).
• @block-ready: Emitted on flow state transitions. Receives { previousState: LoginFlowState; state: LoginFlowState }. Useful for analytics and custom logging.
• @update:language: Emitted after the session starts with the resolved language string. Used automatically by v-model:language.

Vulnerability Reporting

The Guidelines for responsible disclosure details the procedure for disclosing security issues. Please do not report security vulnerabilities on the public issue tracker.

License

@strivacity/sdk-nuxt is available under the MIT License. See the LICENSE file for more info.

Contributing

Please see our contributing guide.

Migrating to v3.0

Entry API Major Changes

Strivacity SDK's entry() API now returns a structured object instead of a plain string. Check the example above in the usage section for more details.