OpenID Connect Clients & Solid Pods


Situation Analysis

The notion of a ubiquitous Read-Write Web lies at the core of the Solid Platforms value proposition, courtesy of its ability to provide a Javascript-based framework for developing, deploying, and interacting with applications and services where the following items are loosely-coupled:

  1. Identity – WebID
  2. Identification – WebID-Profile Document (your credentials reside here)
  3. Authentication – OpenID Connect or WebID-TLS protocols (for authenticating your credentials)
  4. Authorization – WebACLs (fine-grained Access Controls)
  5. Application Logic
  6. Data Access & Storage

That said, appreciating what it the decoupling outlined above offers requires the support of easy to understand demo collection oriented towards practical utility – without deep dives into code.

Earlier today, I published a blog post that demonstrates how our Virtuoso Platform (Multi-Model RDBMS and Middleware Hybrid) enables the following, courtesy of its use of the Solid Framework:

  • Provide Access to Privileged Linked Data Transformation Services exposed by a SPARQL Query Service Endpoint to Identities associated with an WebACL

  • Ditto with regards to a Smart Agent Service that generates REST-ful interaction Consoles from APIs documented using RDF (leveraging terms from Vocabulary) or the OpenAPI standards


In either case, user registration isn’t required due to the fact that existing Solid Pods (e.g., from the Solid Community, Inrupt, OpenLink [1][2] etc…) function as Identity Providers that are loosely-coupled with the Generic OpenID Connect Provider built into Virtuoso’s Authentication Protocol Virtualization Layer.