You can bring your own custom sign up and sign in pages to use with Kinde. Integrate your own designs for the initial sign up and sign in page, and still get the security of Kinde’s auth (and verification) process.

This gives you the best of both worlds: the security of hosted auth, and the ability to customize the sign-up experience for your users.

If you only allow users to sign up and sign in with social authentication - such as Google or Apple - then you can achieve a headless-type experience.

Users sign up or sign in from your custom screen, then get pushed straight through to the social provider’s account selection screen. For example:

If you allow email sign up and sign in, the initial Kinde screen can be bypassed, but the Kinde code verification screen will still appear before sign in is completed.

When a user signs up (say, via email), they do this in fields on your custom sign in screen. Then for verification, they see Kinde’s verification code screen. After that, it’s all you again.

This feature lets you to bypass Kinde’s initial sign in screens, but the following screens are still hosted by Kinde and are part of our secure auth experience.

• Enter password or One-time password (OTP) screens (see example above)
• Multi-factor authentication screens
• The organization switcher (if you support multiple organizations)
• The screen where users can choose to create an account if one was not found

1. Go to Settings > Applications.
2. Select View details on the application you want to switch on custom auth for.
3. Scroll down and switch on the Use your own sign-up and sign-in screens option in the Authentication experience section.
4. Select Save.

Each authentication type you have set up in Kinde has a unique Connection ID attached to it. You need to add this connection ID to your screen design code, so that the Kinde screens get bypassed when users interact.

1. Go to Settings > Authentication.
2. Select Configure on the relevant authentication method tile. For example, the Google tile under the Social connections section.
3. Copy the Connection ID and paste it somewhere you can access later.
4. Select Save or Cancel.
5. Repeat for each authentication method you want to be included on your custom sign in screen.

There are different steps depending on the authentication method you use. Update your code for all that apply.

Add the connection_id to the auth url. Here is an example using React:

<button
    onClick={() =>
        login({
            authUrlParams: {
                connection_id: "conn_6a95dec504d34dc286dc80e8df9f6099"
            }
        })
    }
>
    Sign in with Google
</button>

You can now test if it works by signing in to your project or app.

Add the connection_id and login_hint params to the auth url.

The login_hint enables you to pre-populate the email for the user, skipping the step where they have to enter their identity/email. It also tells us where to send their one time password for passwordless verification.

Here is an example using React.

<button
    onClick={() =>
      login({
        authUrlParams: {
            connection_id: "conn_e5f80aa5258e4685bf629b38003ee954"
            login_hint: "dave@kinde.com"
         }
      })
    }
>
    Sign in with email
</button>

You can now test if it works by signing in to your project or app.

Add connection_id and login_hint params to the auth url.

The login_hint enables you to pre-populate the phone for the user, skipping the step where they have to enter their phone number. It also tells us where to send their one time password for passwordless verification.

The login_hint needs to be in one of these formats phone:<intl_number>:<country_code> or phone:<+intl_number>:<country_code>. The ‘+’ symbol is optional, as long as the country code is included.

Here is an example using React:

<button
    onClick={() =>
      login({
        authUrlParams: {
          connection_id: "conn_e1d49977648149a2a32fde844f1ff9e5"
          login_hint: "phone:+61466043123:au"
        }
      })
    }
>
    Sign in with phone
</button>

You can now test if it works by signing in to your project or app.

Add the connection_id to the auth url. This takes the user directly to the enterprise authentication process. Here is an example using React:

<button
    onClick={() =>
        login({
            authUrlParams: {
                connection_id: "conn_6a95dec504d34dc286dc80e8df9f6099"
            }
        })
    }
>
    Sign in to [project name]
</button>