Svelte and specifically, SvelteKit is an open source web framework that makes developing web applications easier.
In this article we’ll be using Keycloak to quickly augment an application with user management and SSO. We will demonstrate the integration by securing a page for logged-in users. This quickly provides a jump-off point to more complex integrations.
Phase Two
is a Keycloak as a Service provider enabling SaaS builders to accelerate time-to-market with powerful enterprise features like SSO, identity, and user management features. Phase Two enhances Keycloak through a variety of open-source extentions for modern SaaS use cases. Phase Two supports both hosted and on-premise deployment options.
What is Keycloak?
Keycloak has been a leader in the Identity and Access Management world since its launch almost 8 years ago. It is an open-source offering under the stewardship of Red Hat
INFO
If you just want to skip to the code, visit the Phase Two Remix example. We also have a plain React example.
TOC
Keycloak Setup
SvelteKit
Setting up a Keycloak Instance
TIP
If you already have a functioning Keycloak instance, you can skip to the next section.
Keycloak Setup Details
Rather than trying to set up a “from scratch” instance of Keycloak, we’re going to short-circuit that process by leveraging a Phase Two free Keycloak starter instance. The Starter provides a free hosted instance of Phase Two’s enhanced Keycloak ready for light production use cases.
Visit the sign-up page.
Enter an email, use a Github account, or use an existing Google account to register.
Follow the register steps. This will include a sign-in link being sent to your email. Use that for password-less login.
After creating an account, a realm is automatically created for you with all of the Phase Two enhancements. You need to create a Deployment in the Shared Phase Two infrastructure in order to gain access to the realm. Without a deployment created, the Create Shared Deployment modal will automatically pop up.
Create a Shared Deployment by providing a region (pick something close to your existing infrastructure), a name for the deployment, and selecting the default organization that was created for you upon account creation. Hit “Confirm” when ready. Standby while our robots get to work generating your deployment. This can take a few seconds.
After the deployment is created and active, you can access the Keycloak Admin console by clicking “Open Console” for that deployment. Open it now to see the console.
At this point, move on to the next step in the tutorial. We’ll be coming back to the Admin Console when its time to start connecting our App to the Keycloak instance.
Setting up an OIDC Client
We need to create a OpenID Connect Client in Keycloak for the app to communicate with.
Details
Keycloak’s docs provide steps for how to create an OIDC client and all the various configurations that can be introduced. Follow the steps below to create a client and get the right information necessary for app configuration.
Open the Admin UI by clicking Open Console in the Phase Two Dashboard.
Click Clients in the menu.
Click Create client.
Leave Client type set to OpenID Connect.
Enter a Client ID. This ID is an alphanumeric string that is used in OIDC requests and in the Keycloak database to identify the client.
Supply a Name for the client.
Click Next.
Under the Capability Config section, leave the defaults as selected. This can be configured further later.
Client authentication to Off.
Authorization to Off.
Standard flow checked. Direct access grants checked. All other items unchecked.
Click Next.
Under Login settings we need to add a redirect URI and Web origin in order. Assuming you are using the example application:
URI and Origin Details
The choice of localhost is arbitrary. If you are using an example application running locally, this will apply. If you are using an app that you actually have deployed somewhere, then you will need to substitute the appropriate URI for that.
Valid redirect URI (allows redirect back to application)
http://localhost:3000/*
Web origins (allows for Token auth call)
http://localhost:3000
Click Save
OIDC Config
Details
We will need values to configure our application. To get these values follow the instructions below.
Click Clients in the menu.
Find the Client you just created and click on it. In the top right click the Action dropdown and select Download adapter config.
Select Keycloak OIDC JSON in the format option. The details section will populate with the details we will need.
Note the realm, auth-server-url, and resource values.
Adding a Non-Admin User
INFO
It is bad practice to use your Admin user to sign in to an Application.
Since we do not want to use our Admin user for signing into the app we will build, we need to add another non-admin user.
Details
Open the Admin UI by clicking Open Console in the Phase Two Dashboard.
Click Users in the menu.
Click Add user.
Fill out the information for Email, First name, and Last name. Click Create.
We will now set the password for this user manually. Click Credentials (tab) and click Set Password. Provide a password for this user. For our use case, as a tutorial, you can leave “Temporary” set to “Off”.
Click Save and confirm the password by clicking Save password
Setting up a SvelteKit Project
INFO
We will use the Phase Two SvelteKit example code here, but the logic could easily be applied to any existing application.
Clone the Phase Two example repo.
Open the SvelteKit folder within /frameworks/sveltekit.
Run npm install and then npm run dev. This example leverages @auth/sveltekit to provide HOC support.
The project makes use of the following SvelteKit items: hooks, components, layout, and @auth/sveltekit module. We’ll review each in kind.
We’ll review where we configure out Keycloak instance. Open the src/auth.ts file. This is a server only file. We will be updating a few values from the prior section where we set up our OIDC client. Taking the values from the OIDC Client Config section, set those values in the code. While it is recommended to use Environment variables for the secret, for the purpose of this tutorial, paste in the Client secret from the OIDC client creation section for the value of clientSecret.
const authjsSecret =
“f18d48ce9bea32e44b5591b2c89185729d4559435f77ca76872a83a0850563a4“;
const realm = “shared-deployment-001“;
const kcConfig = {
// Use Environment Variables AUTH_KEYCLOAK_ISSUER in prod
issuer: `https://usw2.auth.ac/auth/realms/${realm}`,
// Paste “Client id” here. Use Environment Variables AUTH_KEYCLOAK_ID in prod
clientId: “reg-example-1“,
// Paste “Client secret” here. Use Environment Variables AUTH_KEYCLOAK_ISSUER in prod
clientSecret: “CLIENT_SECRET“,
};
Those are used to popluate the config for the provider Keycloak:
trustHost: true,
secret: authjsSecret,
providers: [Keycloak(kcConfig)],
});
Next, let’s review the hooks (src/hooks.server.ts) file. This imports the handle method by the src/auth.ts and re-exports it. This allows the hooks to act as a middleware and include the authentication status of the user in each request.
To retrieve the authentication status of the user in server-side rendering on the index route, it’s using the +layout.server.ts file. It retrieves the authentication status via the getSession function from SvelteKit Locals set by src/hook.server.ts.
export const load: LayoutServerLoad = async (event) => {
const session = await event.locals.getSession();
return {
session,
};
};
The server-side authentication data is then accessed inside the +page.svelte, and then passed onto the user (src/components/user.svelte) component as follows:
import User from “$components/user.svelte“;
import type { LayoutServerData } from “./$types.js“;
export let data: LayoutServerData;
</script>
// … Rest of the index route … // <User data={{ user: data?.session?.user,
status: Boolean(data?.session), }} />
The props, user and status represent the user information object and whether the user is signed in, respectively.
At this point our entire application will be able to access all information and methods needed to perform authentication. View src/components/user.svelte for exactly how the code is authenticating your user. The sections rendering the Log in and Log out buttons are conditional areas based on the authenticated context. The buttons invoke server-side APIs provided by @auth/sveltekit.
The logic using the authenticator to conditionally determine the Authenticated state, can be used to secure routes, components, and more.
Open localhost:3000. You will see the Phase Two example landing page. You current state should be Not authenticated. Click Log In. This will redirect you to your login page.
INFO
Use the non-admin user created in the previous section to sign in.
Enter the credentials of the non-admin user you created. Click Submit. You will then be redirected to the application. The Phase Two example landing page now loads your Authenticated state, displaying your user’s email and name.
Neat! If you clear the browser state for that tab, then you will have to be redirected away to sign-in again.
Learning more
Phase Two’s enhanced Keycloak provides many ways to quickly control and tweak the log in and user management experience. Our blog has many use cases from customizing login pages, setting up magic links (password-less sign in), and Organization workflows.
