This feature is not yet available on Hanko Cloud.


  1. You need a Hanko Cloud account and a project. Learn more on how to set them up here.
  2. You need a LinkedIn account. You can create an account here.

Get your provider redirect URL

When creating an LinkedIn application, you need to provide a redirect URL that determines where the third party provider redirects after a successful login. This redirect URL consists of the base URL of the Hanko API and the /thirdparty/callback endpoint. You can always view your redirect URL in the Hanko Cloud Console:

  1. Sign in to
  2. Select your Organization.
  3. Select your Project.
  4. In the left sidebar, click Settings, then select Identity providers.
  5. Find your redirect URL in the Redirect URL input.
Hanko Callback URL

You need the redirect URL for creating a new LinkedIn application in the next step and configuring your credentials with Hanko (you will also configure the remaining configuration options visible in the above screen in this step).

Create a new LinkedIn application

  1. Navigate to and log in to the LinkedIn developer portal.
  1. Click on the Create app button.
create linkedin app
  1. Enter your application name in App name.
  2. Enter your LinkedIn company page url in LinkedIn Page or create one.
  3. (Optional) Enter your privacy policy page url in Privacy policy URL.
  4. Upload a logo for your application.
  5. Accept the terms and conditions.
  6. Click on the Create app button.
product list
  1. Search for the Sign In with LinkedIn using OpenID Connect card from the product list.
  2. Click Request access.
request access for sign in
  1. Accept the terms and conditions.
  2. Click on the Request access Button.
  3. The card should now show as added product.
  4. Click on Auth and scroll to OAuth 2.0 settings
OAuth 2.0 settings
  1. Click on the pencil next to Authorized redirect URLs for your app
  2. Click on + Add redirect URL
  3. Enter the Redirect URL you obtained in the first step as the value.
  4. Click on the Update button.

Get your client ID and secret

You can view the client ID as well as the secret of your app in the Auth tab on your app page. You will need this when configuring your credentials with Hanko

Client ID and Secret

Configure credentials with Hanko

  1. In the Hanko Cloud Console, navigate to your project Settings and select Identity providers.
  2. Configure the following:
Hanko Callback URL
  • Error Redirect URL: This is the URL target in your frontend the Hanko API redirects to if an error occurs during third party sign-in. If your frontend uses the hanko-elements web components, this URL should be the URL of the page that embeds the web component such that errors can be processed properly by the web component.

  • Allowed Redirect URL: This is the URL target in your frontend the Hanko API is allowed to redirect to after third party authentication was successful. If your frontend uses the hanko-elements web components, this URL should be the URL of the page that embeds the web component.

    The allowed redirect URL supports wildcard matching through globbing:

    • https://* matches and
    •* matches URLs like and
    • Use ** to act as a super-wildcard/match-all.
  1. In the Providers section, select LinkedIn and use the Enable provider toggle to enable the provider.
  2. Provide the Client ID and Client Secret you obtained in one of the previous section in the remaining inputs.
  3. Click Save.

Frontend integration

To enable a login with LinkedIn in your frontend application we recommend using either our pre-built UI as provided by the @teamhanko/hanko-elements package or building a custom UI using the @teamhanko/hanko-frontend-sdk.

We recommend following one of our quickstart guides to integrate the <hanko-auth> component from our @teamhanko/hanko-elements package in your frontend application . On successful integration, the component will display a button for signing in with LinkedIn in the login view of the component.

Make sure to configure the page the web component is embedded on as your error redirect URL as well as an allowed redirect URL (see the previous step).

On successful authentication with the provider, the backend issues a session cookie and the web component continues the usual component flow on success. Errors that occur during third party provider authentication are also picked up and displayed in the web component accordingly.