npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

simple-keycloak-adapter

v0.0.5

Published

This is a Node module to streamline Keycloak integration Node+Express based services. It's intended to abstract some of the boilerplate necessary to protect Express endpoints when using a Keycloak instance for SSO, but does still require some configurati

Downloads

24

Readme

Simplified Keycloak Adapter

This is a Node module to streamline Keycloak integration Node+Express based services. It's intended to abstract some of the boilerplate necessary to protect Express endpoints when using a Keycloak instance for SSO, but does still require some configuration to specify which instance to target.

Installation

Edit, this is now on NPM!

npm install simple-keycloak-adapter --save

Setup

Setup will depend on which Keycloak client you are using to protect your endpoints. Each Keycloak client has an installation JSON file whose corresponding object you can just drop into this. Assuming you're using a client called my-client on some realm my-realm running locally on port 8080, your first step will be something like:

const keycloakHelper = require("simple-keycloak-adapter");

app.use(keycloakHelper.init({
    realm: "my-realm",
    authServerUrl: "http://localhost:8080/auth",
    client: "my-client"
}));

where app is the typical Express application instance. Once this is in place, subsequent routes can be protected individually:

app.get("/protected", keycloakHelper.protect(), (req, res, next) => res.send("protected endpoint!"))

or through a catchall that will protect all routes declared after it:

app.use(keycloakHelper.protect());

Example

For a full example using the above blocks:

const keycloakHelper = require("simple-keycloak-adapter");
const app = require("express")()

// Initialize our middleware
app.use(keycloakHelper.init({
    realm: "my-realm",
    authServerUrl: "http://localhost:8080/auth",
    client: "my-client"
}));

// Set up two routes, with the root being unprotected
app.get("/", (req, res, next) => res.send("unprotected endpoint!"))
app.get("/protected", keycloakHelper.protect(), (req, res, next) => res.send("protected endpoint!"))

// Start our server
app.listen(3000, () => console.log("listening on 3000!"))

Optional Syntax

For clarity and as the underlying keycloak-connect library depends on hyphenated property names ("auth-server-url"), there are aliases provided. When you pass one of these aliased versions, they will be assigned to their syntactically-correct equivalent before being passed to Keycloak.

| Adapter Property | Keycloak Property | |:----------|:------| | client| resource| | authServerUrl| auth-server-url| | bearerOnly| bearer-only| | confidentialPort| confidential-port| | publicClient| public-client| | sslRequired | ssl-required |

Logout and Redirect endpoints

By default, the middleware will react to a specified path and treat that as a logout request. We default this to /logout, but this can be set manually during the .init() call. For example, something whose base was /registry might use the following endpoints:

app.use(keycloakHelper.init(config.keycloak, "/registry/logout", "/registry"))

where the first argument is the logout route and the second is where unauthorized users will be directed.

Access Denial Handler

You can supply another optional argument to that .init() call to specify how a denied request should proceed. By default, this just redirects the user to the root path, but you can supply your own:

let logoutHandler = (req, res, next) => res.send("unauthorized!");
app.use(keycloakHelper.init({ ... }, "/logout", "/", logoutHandler))