Skip to content
This repository has been archived by the owner on Jul 22, 2021. It is now read-only.



Folders and files

Last commit message
Last commit date

Latest commit



33 Commits

Repository files navigation


-- a nodejs client for Solid --

NOTE: This is an experimental branch that provides a plugin system including support for using solid-client-authn-node. For the time being, to use with NSS or PSS, skip this next session and got straight to the old docs.

If you want to use ESS or CSS, here's how:

1. get a cookie (do this once, then it's good for several weeks)

From the command-line,

  • Change to the ./node_modules/@inrupt/solid-client-authn-node/example/bootstrappedApp/src/,

  • Run the bootstrap.js script. It will prompt you for user name and identity provider, then show you a URL. Go to that URL in your browser and follow the steps to login. Once you've logged in, you should see a message telling you to close the login window, and back on the command line you should see a cookie with the tokens and secrets you need to login. Copy the cookie text and save it in a safe place.

2. use the cookie to login

Retrieve the cookie as a json string from wherever you stored it in step #1. Then use it in a script or app like this (replacing the $COOKIE varibales with the ones from the cookie):

const {SolidNodeClient} = require('solid-node-client');
const client = new SolidNodeClient({ handlers : 
  { https: 'solid-client-authn-node' }
      clientName: $COOKIE.clientName,
        clientId: $COOKIE.clientId,
    clientSecret: $COOKIE.clientSecret,
    refreshToken: $COOKIE.token,
      oidcIssuer: $COOKIE.oidcIssuer
}).then( (session) => {
if( ) {
  console.log(`Successfully logged in!`)
  // client.fetch() will now be an authenticated fetch on ESS/CSS

That's all!

Working with plugins

Solid-Node-Client comes with default handlers for three types of fetches, so a call to new SolidNodeClient() with no arguments is the equivalent of doing this:

    const client = new SolidNodeCient({ handlers : {
      https    : 'solid-auth-fetcher',  // authenticated web fetches
      file     : 'solid-rest-file',     // local file system fetches
      fallback : 'node-fetch',          // all other fetches

Users may specify 'solid-client-authn-node' as the https fetcher and may also spcify a handler for mem as 'solid-rest-mem' (this means that mem://foo/bar/ is an in-memory simulated container accessible as a serverless pod).

Users may also specify any of the fetchers as objects that they have imported and instantiated. So if you have a new auth package you could do this:

    const client = new SolidNodeCient({ handlers : {
      https    : new yourCustomAuthLibrary() // authenticated web fetches

This library provides access to Solid from the command line and from local scripts and apps which either run in the console or in a local browser based context like electron. It can be used to move resources back and forth between a local commputer and one or more pods, carry out remote operations on pods, and can also treat your local file system as a serverless pod.

Solid-Node-Client uses solid-auth-fetcher to provide session management and fetching for https: URLs and uses solid-rest to provide solid-like fetches on file: and other non-http URLs. It supports login and authenticated fetches to NSS servers. Support for login to other servers will be added in the future.

Solid-node-client can be used stand-alone, or can be used with rdflib, solid-file-client, and most other Solid apps. See creating a serverless pod for additional details.

As of version 1.2.0, solid node client now supports multiple logins from the same script. See below for details


Stand alone usage :

import { SolidNodeClient } from 'solid-node-client';
const client = new SolidNodeClient();

async function main(){
    let response = await client.fetch('');
    console.log(await response.text())
    let session = await client.login();
    if( session ) {
        console.log (`logged in as <${session.webId}>`);
        response = await client.fetch('');
        console.log(await response.text())

Usage with rdflib :

import {SolidNodeClient} from 'solid-node-client';
import * as $rdf from 'rdflib';
const client = new SolidNodeClient();
const store   = $rdf.graph();
const fetcher = $rdf.fetcher(store,{fetch:client.fetch.bind(client)});  
    // now all rdflib methods support file:// requests in nodejs

async function main(){
    let session = await login();  // may be omitted if you don't need authentication
    // now all rdflib methods support authenticated http: requests in nodejs


1. install the app

  npm install

2. give the app permission

Skip this step if you don't need authenticated access to a pod. To get authenticated access to a pod, you will need to add "https://solid-node-client" as a trusted app on that pod or the portion of it you want to access. See how to make an app trusted for how to do this.



Logs the user in to a Solid pod and returns an authenticated session. Credentials for the login may be set as environment variables in your operating system or passed in the options.

If these variables are part of your environment, you can use the login() method without arguments.

  • SOLID_IDP // the server root e.g. (no trailing slash)
  • SOLID_USERNAME // your username on the server
  • SOLID_PASSWORD // your password on the server
  • SOLID_DEBUG // set this if you want to output extended login and session debugging

If you don't have those environment variables set or if you wish to override them, you can set them in the arguments to login().

   let session = await client.login({
       idp : "https://yourIdentityProvider",
       username : "yourUsername",
       password : "yourPassword",
       debug : true // or false

The session object returned will be a solid-auth-fetcher Session object which has properties loggedIn and webId. See the solid-auth-fetcher docs for further details if you need them.


Logs the user out. This means that authenticated fetches are no longer possible but you can still use unauthenticated fetches.


This method performs CRUD operations as specified in the Solid REST spec. When used with file: URLs, most of the REST spec is followed and, as with http: URLs, the return value is a Response object containing fields such status and statusText and methods such as text(), json(), and headers.get(). See the solid-rest docs for details of how file: URLs are handled.

Here's an example :

// write a resource
let writeResponse = await client.fetch( '', {
  method : "PUT",
  body : "some content to go in the resource",
  headers : { "Content-type" : 'text/plain' }
console.log( writeResponse.status  );  // 201
// now read it
let readResponse = await client.fetch( '' );
// display its contents
console.log( await readResponse.text()  );

Note about Patch

PATCH is supported by solid-node-client, but only if your script imports rdflib and you set the parser option for new SolidNodeClient(). The syntax for PATCH is the same as in rdflib.

import {SolidNodeClient} from 'solid-node-client';
import * as $rdf from 'rdflib';
const client = new SolidNodeClient({parser:$rdf});
// client.fetch() now supports PATCH on file: URLs and all solid-rest backends

It is now possible to login multiple times from the same script. You can create clients authorized for several different identities.

  const client_1 = new SolidNodeClient();
  const client_2 = new SolidNodeClient();
  const client_3 = new SolidNodeClient();
  await client_1.login( siteA_credentials);
  await client_2.login( siteB_credentials);
  // now client_1 is authenticated at siteA;
  //     client_2 is authenticated at siteB;
  //     client_3 is unauthenticated

Working with underlying session objects

The solid-auth-fetcher session and authFetcher objects are available for each client. See the solid-auth-fetcher docs for details :

  if( client.session.loggedIn() ...
  let authFetcher = client.authFetcher ...  

Solid Node Client can access the local file system using file:// URLs without using a server. In most respects, it will treat the file system as a pod. To get the full benefit of this, it's best to create some local files such as a profile, a preferences file, and type indexes. You can create them manually or copy them from a remote pod, but the easiest thing to do is use the built-in createServerlessPod method.

import {SolidNodeClient} from 'solid-node-client';
const client = new SolidNodeClient();

The code above will create a profile, preferences and other key pod resources in the named folder. Your profile will be located at '/home/jeff/myPod/profile/card' and your preferences file will be located at '/home/jeff/myPod/settings/prefs.ttl'. You can now use a file:// URL to refer to your local webId: file:///home/jeff/myPod/profile/card#me. As with a server-based pod, this webId is the starting point for any app that wants to follow its nose through your local file system.


All of the session management is from Jackson Creed's solid-auth-fetcher. The login is from Michiel de Jong's solid-crud-tests.

Copyright and License

copyright © 2020, Jeff Zucker, may be freely distributed with the MIT license


a nodejs client for Solid







No packages published


  • JavaScript 67.9%
  • TypeScript 32.1%