@tripleslate/provenance
v0.13.0
Published
server-side SvelteKit auth
Downloads
900
Readme
provenance
Server-side OAuth/OIDC implementation for SvelteKit
features
- Create a
handle
for programmatically defining auth functionality in server hooks- handle requests to redirectUri, login, and logout routes
- refresh access tokens (if refresh tokens used by the provider)
- add a session object to
event.locals
- track the referrer for redirect after login
- Provide a
protectRoute
function for redirecting user without session to login - Expose a callback to include extra information in the stored cookie session given tokens data
installation
npm i --save-dev @tripleslate/provenance
usage
See the example project to see the following writeup in action.
include vite plugin
Include provenance
in the vite plugin pipeline. It will generate a light "runtime"
that forms the bridge between your project's version of sveltekit
and the provenance
core logic.
vite.config.ts
import { defineConfig } from 'vite';
import { sveltekit } from '@sveltejs/kit/vite';
import { provenance } from '@tripleslate/provenance/vite';
export default defineConfig({
// provenance first
plugins: [provenance(), sveltekit()]
});
src/lib/server/PROVENANCE.ts
will be written on vite dev server start and build and should be checked in. This output file location can be customized and optionally output in js.
create auth object
src/lib/server/auth.ts
github
import { provenance } from './PROVENANCE';
import { github } from '@tripleslate/provenance/providers';
import { GH_CLIENT_ID, GH_CLIENT_SECRET } from '$env/static/private';
export const auth = provenance(
github({
clientId: GH_CLIENT_ID,
clientSecret: GH_CLIENT_SECRET
})
);
keycloak
import { provenance } from './PROVENANCE';
import { keycloak } from '@tripleslate/provenance/providers';
import { KC_BASE, KC_REALM, KC_CLIENT_ID, KC_CLIENT_SECRET } from '$env/static/private';
export const auth = provenance(
keycloak({
base: KC_BASE,
realm: KC_REALM,
clientId: KC_CLIENT_ID,
clientSecret: KC_CLIENT_SECRET
})
);
match the App
interfaces to your provider and session callback
You will not be able to access session data from locals if your App.Session
interface does not match the provider
and sessionCallback
passed to $provenance.provenance
(see "create auth object").
src/app.d.ts
declare global {
namespace App {
interface Session {
accessToken: string;
}
// interface Error {}
// interface Locals {}
// interface PageData {}
// interface Platform {}
}
}
export {};
Above example applies to github
provider. Refer to the fields in the Session
generic parameter on other providers.
Note that Locals
does not need to be defined, provenance
provides a default session
field of type App.Session | null
.
If an app defines other Locals
fields, they can be defined here without redefining session
on Locals
as typescript will merge the two declarations of the interface.
intialize handle hook
src/hooks.server.ts
import { auth } from '$lib/server/auth';
export const handle = auth.handle;
protect a route
src/routes/protected/+page.server.ts
import { protectRoute } from '@tripleslate/provenance/initiatives';
import { auth } from '$lib/server/auth';
export const load = async (event) => {
const session = await protectRoute(auth.createContext)(event);
return {
session
};
};
Note that handle
in hooks.server.ts
is not invoked during client side routing (typically, navigating to a page without a +page.server.ts
after first load). This means that protecting a route with auth.protectRoute
and accessing (up to date) session information must be done in a +page.server.ts
load, not a +page.ts
load.