Skip to content


OpenID is a layer on top of the OAuth 2.0 protocol that allows you to authenticate users and get their basic profile from the OAuth provider of your choice, including but not limited to Google, Slack, LINE, etc.

How you configure the OpenID plugin in WeWeb will depend on the OAuth provider you are working with. In this article, we will demonstrate using Google OAuth.

Provider setup

Before you can configure the WeWeb plugin, you'll need the following information from your OAuth provider:

  • the domain WeWeb should send the request to via OpenID
  • a client ID
  • a client secret
  • a scope (i.e. what information you want to get)
  • a response type

How you get this information will depend on your OAuth provider.

To allow users to signup or login with their Google account, you would need to:

New project in Google Cloud Console

Once you've created a project, you'll be able to configure the provider's consent screen and get credentials so WeWeb can make secure requests to the provider via the OpenID plugin.

The OAuth consent screen is the screen the user will see when they choose to connect with the provider.

For example, the Google consent screen looks something like this:

OAuth consent screen example

To configure the Google OAuth consent screen, you'll need to go to APIs & Services > OAuth consent screen:

OAuth consent screen configuration

At that stage, the provider will ask for some information such as:

Branding – For example, what is the name of your application and its logo.

Contacts – For example, a developer and/or support email address.

User type – Whether your app is reserved for people in your company (internal) or open to people outside your organization (external)

Authorized domains – A list of domain names that are authorized to make a request for autentication to the provider. For example,

  • so it works when you're testing inside the WeWeb Editor,
  • to test the auth flow on a published app without a custom domain, and
  • your own custom domain to ensure it works properly on your live app

Scopes – To define what users will be giving access to (e.g. just their basic info or also their calendar).

Test users – A list of test users who can test the app while it's under development.


Depending on the provider, some of these will be optional. What is never optional is listing which domains are authorized to make a call to the provider. Make sure to get those right and don't forget to add your custom domain later if you don't have it from the start.

API keys & credentials

In order for the provider to authorize the call you make through the OpenID plugin in WeWeb, you'll need create OAuth credentials in the provider's interface and copy them in WeWeb when you configure the plugin (but more on that later).

In Google, you can do this by going to APIs & Services > Credentials > Create credentials > OAuth client ID:

OAuth consent screen configuration

At that stage, the provider will ask for information such as:

Name – You will be invited to name the credentials. It doesn't really matter what you name it but it's helpful if it's descriptive enough that you know where you're using them. For example, you could name them: OpenID via WeWeb

Authorized JavaScript origins – A list of all the domains your web-app is hosted on. For example:

  • the WeWeb editor:
  • your app in staging:
  • your app in production:

Authorized redirect URIs – A list of URIs where users can be redirected after being authenticated. For example:

  • the page in the WeWeb editor:
  • the page in the app in staging:
  • the page in production:

These links should correspond to the page where users are redirected after being authenticated through the OpenID plugin in all the environments of your app (e.g. the WeWeb editor, in staging, in production).

It should match the URIs of the page you defined in the OpenID plugin in WeWeb:

Authorized redirect URIs


If you need to update these later, for example when you add a custom domain to your app, keep in mind that it can take 5 minutes up to a few hours for the new settings to take effect:

Update settings in Google Cloud Console

We recommend you stay patient when testing new settings. Testing new settings right away and reverting back because you don't see the difference instantly is a great way to get confused and feel stuck.

Plugin configuration

In WeWeb, you'll find the OpenID plugin in the Plugins > Authentication menu:

OpenID plugin in WeWeb

When you add the plugin, you'll be invited to provide information that will allow WeWeb to make calls on behalf of your app to your OAuth provider:

  • the domain of your OAuth provider
  • the OAuth 2.0 credentials created for your app (i.e. the client ID and client secret)
  • the scope values you want OpenID to return from the User Info endpoint, e.g. profile, email, address, or phone. Learn more about different scope values in OpenID's user docs
  • the response type. Learn more about different OAuth flows in this video by Oracle and through OpenID's user docs

In the example below, you can see:

  • we are working with Google as a provider, and
  • are asking for the user email and profile of the user

OpenID plugin configuration


Once you have told the OpenID plugin how to communicate with your OAuth provider, you will need to define pages where users are redirected:

  • after they sign-in
  • when they are not signed-in

OpenID page redirects

In the example above, we named those pages Post login and Login but we can choose to redirect them to any page we want. For example, we could redirect authenticated users to their profile page and unauthenticated users to the app's home page.

Signup and login flows

Once you've added the OpenID plugin to your WeWeb project, you will get access to dedicated OpenID actions in workflows:

OpenID workflow actions in WeWeb

When you use one of the login actions in a workflow, the user will be automatically redirected to the page you defined in the OpenID plugin after the authentication is successful.

Even if you have a Change page action after the login action in your workflow, the OAuth flow will resolve on the redirect page defined in the plugin and authorized in the provider dashboard.

Advanced redirection

If you want more flexibility on where to redirect authenticated users, you could update a destination page variable before the login action in your workflow to define where the user should be redirected after the login:

Update page redirection variable

Then, on the post-login page, you can trigger a workflow On Page Load that checks the destination page variable to decide if the user should stay on the post-login page or be redirected to another page like the user profile in the example below:

Workflow on page