CommunityHire an ExpertSign Up
Advanced Sign-in OptionsOpenId Single Sign-on
Advanced Sign-in Options

OpenId Single Sign-on

Setting up authentication with OpenId.

OpenId Single sign on block

OpenId Single sign on block

Using this block, you can enable your users to sign in with their OpenId credentials. To be able to use the block, you first need to integrate the OpenId platform that you use for user management and authentication. We’ll find out how to do that next.

Configuring OpenId settings

OpenID Connect (OIDC) is an open authentication protocol that extends the OAuth 2.0 protocol, adding an identity layer to it. There are a number of services that use the OpenId technology. Softr can be integrated with any platform using the OpenID standard. One such platform is Outseta membership software. Let’s use Outseta as an example for how to set up OpenID in your Softr app.

If you use Outseta as your user management and authentication solution, you can integrate it with Softr, allowing your users to log into your Softr app with their Outseta credentials. The integration steps are pretty simple and straightforward, so let’s start.

Getting the Callback URL

First, let’s copy the Callback URL from our OpenId Settings. We are going to use it in our Outseta account, so let’s switch there for a moment.

Adding an OAuth Client in Outseta

First, we need to add an OAuth Client in our Outseta account. To do that, we need to navigate to Settings => Integrations => OAuth and hit Add OAuth Client.

Adding OAuth Client

Adding OAuth Client

In the pop-up that follows, we are going to add a Name for the client, paste the Callback ID we had copied earlier from our Softr app։ The Logout Redirect URL can be left blank.

Configuring OAuth client

Configuring OAuth client

After completing those, click Add, and the pop-up will expand, showing your Integration Details.

Integration details

Integration details

Here, you need the Client Id and Client Secret values.

Adding Client Id and Secret on Softr

Now we are going to add the Client Id and Client Secret values, which we obtained in the previous step, in our Softr app’s OpenId Settings.

Adding ID and secret

Adding ID and secret

After completing this, Save your settings, and you’re done. Now, you can use the OpenId SSO Softr block to allow your users log in with their Outseta credentials.

Testing the Integration

Let’s pick a user from our Outseta contacts and try logging in with this user’s credentials on Softr. You can learn about user authentication, how users can sign up and create passwords, and more here.

Below, you can see a contact that has passed authentication and has a password.

A contact in Outseta

A contact in Outseta

Now, we can use this contact’s email and password to log into our Softr app through the OpenId login block. First, let’s set up the OpenId block.

Adding the OpenId Signin block

Adding the OpenId Signin block

We can modify the layout of the block as well as change the page after signin, but we are going to leave it as it is. Now, let’s publish our app and try logging in with the Outseta user we mentioned earlier.

Testing signin

Testing signin

As you can see, we’re able to log in and out successfully.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.