openidAuthentication

Authentication is the process of verifying the identity of an agent. To access private data, you must authenticate as an agent who has been granted appropriate access to that data.

Authentication Flows

Solid authentication is based on the Solid-OIDCarrow-up-right specification. Solid-OIDCarrow-up-right builds upon the OpenID Connectarrow-up-right standards, which itself builds on the OAuth 2.0arrow-up-right authorization framework.

For applications implementing Authorization Code Flowarrow-up-right:

  1. The application starts the login process by sending the user to the user’s Solid Identity Provider.

  2. The user logs in to the Solid Identity Provider.

  3. The Solid Identity Provider sends the user back to your application, where the application handles the returned authentication information to complete the login process.

For applications implementing Client Credentialsarrow-up-right flow:

  1. The application (such as a single-user script) logs in, on behalf of the user who registered the client, by sending its client credentials to its Solid Identity Provider (i.e., where the user registered the client).

  2. The Solid Identity Provider returns the tokens to the app.

Inrupt Client Libraries

Inrupt provides the following libraries for authentication:

  • solid-client-authn-browser to authenticate in a browser.

  • solid-client-authn-node to authenticate in Node.js.

chevron-rightNote about Client IDshashtag

In Solid-OIDCarrow-up-right (i.e., in OAuth 2.0arrow-up-right and OpenID Connectarrow-up-right), an application identifies itself using a client identifier (Client ID)arrow-up-right.

A Client ID can be:

Inrupt’s client libraries provide login APIs that supports:

Authentication in Solid can be performed:

See these direct guides for more information.

Last updated