Skip to main content
For our new friends:

Logto is an Auth0 alternative designed for modern apps and SaaS products. It offers both Cloud and Open-source services to help you quickly launch your identity and management (IAM) system. Enjoy authentication, authorization, and multi-tenant management all in one.

We recommend starting with a free development tenant on Logto Cloud. This allows you to explore all the features easily.

In this article, we will go through the steps to quickly build the GitHub sign-in experience (user authentication) with .NET Core (Blazor WebAssembly) and Logto.

Prerequisites

Create an application in Logto​

Logto is based on OpenID Connect (OIDC) authentication and OAuth 2.0 authorization. It supports federated identity management across multiple applications, commonly called Single Sign-On (SSO).

To create your Single page app application, simply follow these steps:

  1. Open the Logto Console. In the "Get started" section, click the "View all" link to open the application frameworks list. Alternatively, you can navigate to Logto Console > Applications, and click the "Create application" button. Get started
  2. In the opening modal, click the "Single page app" section or filter all the available "Single page app" frameworks using the quick filter checkboxes on the left. Click the ".NET Core (Blazor WebAssembly)" framework card to start creating your application. Frameworks
  3. Enter the application name, e.g., "Bookstore," and click "Create application".

🎉 Ta-da! You just created your first application in Logto. You'll see a congrats page which includes a detailed integration guide. Follow the guide to see what the experience will be in your application.

Integrate .NET Core (Blazor WebAssembly) with Logto​

tip:

Installation​

Add the NuGet package to your project:

dotnet add package Blorc.OpenIdConnect

Add script references​

Include Blorc.Core/injector.js the index.html file:

index.html
<head>
  <!-- ... -->
  <script src="_content/Blorc.Core/injector.js"></script>
  <!-- ... -->
</head>

Register services​

Add the following code to the Program.cs file:

Program.cs
using Blorc.OpenIdConnect;
using Blorc.Services;

builder.Services.AddBlorcCore();
builder.Services.AddAuthorizationCore();
builder.Services.AddBlorcOpenIdConnect(
    options =>
    {
        builder.Configuration.Bind("IdentityServer", options);
    });

var webAssemblyHost = builder.Build();

await webAssemblyHost
    .ConfigureDocumentAsync(async documentService =>
    {
        await documentService.InjectBlorcCoreJsAsync();
        await documentService.InjectOpenIdConnectAsync();
    });

await webAssemblyHost.RunAsync();
info:

There's no need to use the Microsoft.AspNetCore.Components.WebAssembly.Authentication package. The Blorc.OpenIdConnect package will take care of the authentication process.

Configure redirect URIs​

Before we dive into the details, here's a quick overview of the end-user experience. The sign-in process can be simplified as follows:

  1. Your app invokes the sign-in method.
  2. The user is redirected to the Logto sign-in page. For native apps, the system browser is opened.
  3. The user signs in and is redirected back to your app (configured as the redirect URI).

Regarding redirect-based sign-in​

  1. This authentication process follows the OpenID Connect (OIDC) protocol, and Logto enforces strict security measures to protect user sign-in.
  2. If you have multiple apps, you can use the same identity provider (Logto). Once the user signs in to one app, Logto will automatically complete the sign-in process when the user accesses another app.

To learn more about the rationale and benefits of redirect-based sign-in, see Logto sign-in experience explained.

note:

In the following code snippets, we assume your app is running on http://localhost:3000/.

Configure redirect URIs​

Switch to the application details page of Logto Console. Add a redirect URI http://localhost:3000/callback.

Redirect URI in Logto Console

Just like signing in, users should be redirected to Logto for signing out of the shared session. Once finished, it would be great to redirect the user back to your website. For example, add http://localhost:3000/ as the post sign-out redirect URI section.

Then click "Save" to save the changes.

Configure application​

Add the following code to the appsettings.json file:

appsettings.json
{
// ...
IdentityServer: {
  Authority: 'https://<your-logto-endpoint>/oidc',
  ClientId: '<your-logto-app-id>',
  PostLogoutRedirectUri: 'http://localhost:3000/',
  RedirectUri: 'http://localhost:3000/callback',
  ResponseType: 'code',
  Scope: 'openid profile', // Add more scopes if needed
},
}

Remember to add the RedirectUri and PostLogoutRedirectUri to the list of allowed redirect URIs in the Logto application settings. They are both the URL of your WASM application.

Add AuthorizeView component​

In the Razor pages that require authentication, add the AuthorizeView component. Let's assume it's the Home.razor page:

Pages/Home.razor
@using Microsoft.AspNetCore.Components.Authorization
@page "/"

<AuthorizeView>
    <Authorized>
        @* Signed in view *@
        <button @onclick="OnLogoutButtonClickAsync">
            Sign out
        </button>
    </Authorized>
    <NotAuthorized>
        @* Unauthenticated view *@
        <button @onclick="OnLoginButtonClickAsync">
            Sign in
        </button>
    </NotAuthorized>
</AuthorizeView>

Set up authentication​

In the Home.razor.cs file (create it if it doesn't exist), add the following code:

Pages/Home.razor.cs
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Components;
using Microsoft.AspNetCore.Components.Web;
using Blorc.OpenIdConnect;
using Microsoft.AspNetCore.Components.Authorization;

[Authorize]
public partial class Home : ComponentBase
{
    [Inject]
    public required IUserManager UserManager { get; set; }

    public User<Profile>? User { get; set; }

    [CascadingParameter]
    protected Task<AuthenticationState>? AuthenticationStateTask { get; set; }

    protected override async Task OnInitializedAsync()
    {
        User = await UserManager.GetUserAsync<User<Profile>>(AuthenticationStateTask!);
    }

    private async Task OnLoginButtonClickAsync(MouseEventArgs obj)
    {
        await UserManager.SignInRedirectAsync();
    }

    private async Task OnLogoutButtonClickAsync(MouseEventArgs obj)
    {
        await UserManager.SignOutRedirectAsync();
    }
}

Once the user is authenticated, the User property will be populated with the user information.

Checkpoint: Test your application​

Now, you can test your application:

  1. Run your application, you will see the sign-in button.
  2. Click the sign-in button, the SDK will init the sign-in process and redirect you to the Logto sign-in page.
  3. After you signed in, you will be redirected back to your application and see the sign-out button.
  4. Click the sign-out button to clear token storage and sign out.

Add GitHub connector​

To enable quick sign-in and improve user conversion, connect with .NET Core (Blazor WebAssembly) as an identity provider. The Logto social connector helps you establish this connection in minutes by allowing several parameter inputs.

To add a social connector, simply follow these steps:

  1. Navigate to Console > Connectors > Social Connectors.
  2. Click "Add social connector" and select "GitHub".
  3. Follow the README guide and complete required fields and customize settings.
Connector tab
note:

If you are following the in-place Connector guide, you can skip the next section.

Set up GitHub OAuth app​

Step 1: Create an OAuth app on GitHub​

Before you can use GitHub as an authentication provider, you must create an OAuth App on GitHub to obtain OAuth 2.0 credentials.

  1. Go to GitHub and sign in with your account, or create a new account if needed.
  2. Navigate to Settings > Developer settings > OAuth apps.
  3. Click New OAuth App to register a new application:
    • Application name: Enter a descriptive name for your app.
    • Homepage URL: Enter your application's homepage URL.
    • Authorization callback URL: Copy the Callback URI from your Logto GitHub connector and paste it here. After users sign in with GitHub, they'll be redirected here with an authorization code that Logto uses to complete authentication.
    • Application description: (Optional) Add a brief description of your app.
  4. Click Register application to create the OAuth App.
note:

We suggest not checking the box for Enable Device Flow, as users who sign in with GitHub on mobile devices would need to confirm the initial sign-in action in the GitHub mobile app. Many GitHub users do not install the GitHub mobile app on their phones, which could block the sign-in flow. Only enable this if you expect end-users to confirm their sign-in flow through the GitHub mobile app. See details about device flow.

For more details on setting up GitHub OAuth Apps, see Creating an OAuth App.

Step 2: Configure your Logto connector​

After creating the OAuth app in GitHub, you'll be redirected to a details page where you can copy the Client ID and generate a Client secret.

  1. Copy the Client ID from your GitHub OAuth app and paste it into the clientId field in Logto.
  2. Click Generate a new client secret in GitHub to create a new secret, then copy and paste it into the clientSecret field in Logto.
  3. Click Save and Done in Logto to connect your identity system with GitHub.
warning:

Keep your Client secret secure and never expose it in client-side code. GitHub client secrets cannot be recovered if lost - you'll need to generate a new one.

Step 3: Configure scopes (Optional)​

Scopes define the permissions your app requests from users and control which data your app can access from their GitHub accounts.

Use the Scopes field in Logto to request extra permissions from GitHub. Choose one of the following approaches based on your needs:

Option 1: No extra API scopes needed​

  • Leave the Scopes field in your Logto GitHub connector blank.
  • The default scope read:user will be requested to ensure Logto can get basic user info (e.g., email, name, avatar) properly.

Option 2: Request additional scopes at sign-in​

  • Browse all available GitHub scopes for OAuth apps and add only the scopes your app needs.
  • Enter all desired scopes in the Scopes field, separated by spaces.
  • Any scopes you list here override the defaults, so always include the authentication scope: read:user.
  • Common additional scopes include:
    • repo: Full control of private repositories
    • public_repo: Access to public repositories
    • user:email: Access to user email addresses
    • notifications: Access to notifications
  • Ensure all scopes are spelled correctly and valid. An incorrect or unsupported scope will result in an "Invalid scope" error from GitHub.

Option 3: Request incremental scopes later​

  • After the user signs in, you can request additional scopes on demand by reinitiating a federated social authorization flow and updating users' stored token set.
  • These additional scopes do not need to be filled in the Scopes field in your Logto GitHub connector, and can be achieved through Logto's Social Verification API.

By following these steps, your Logto GitHub connector requests exactly the permissions your app needs - no more, no less.

tip:

If your app requests these scopes to access the GitHub API and perform actions, make sure to enable Store tokens for persistent API access in Logto GitHub connector. See the next section for details.

Step 4: General settings​

Here are some general settings that won't block the connection to GitHub but may affect the end-user authentication experience.

Sync profile information​

In the GitHub connector, you can set the policy for syncing profile information, such as user names and avatars. Choose from:

  • Only sync at sign-up: Profile info is fetched once when the user first signs in.
  • Always sync at sign-in: Profile info is updated every time the user signs in.

Store tokens to access GitHub APIs (Optional)​

If you want to access GitHub APIs and perform actions with user authorization (whether via social sign-in or account linking), Logto needs to get specific API scopes and store tokens.

  1. Add the required scopes following the instructions above.
  2. Enable Store tokens for persistent API access in the Logto GitHub connector. Logto will securely store GitHub access tokens in the Secret Vault.
note:

When using a GitHub OAuth App as described in this tutorial, you cannot get a refresh token from GitHub because its access token does not expire unless the user manually revokes it. Therefore, you do not need to add offline_access in the Scopes field — doing so may cause an error.

If you want the access token to expire or use refresh tokens, consider integrating with a GitHub App instead. Learn about the differences between GitHub Apps and OAuth Apps.

Step 5: Test your integration (Optional)​

Before going live, test your GitHub integration:

  1. Use the connector in a Logto development tenant.
  2. Verify that users can sign in with GitHub.
  3. Check that the correct scopes are being requested.
  4. Test API calls if you're storing tokens.

GitHub OAuth Apps work with any GitHub user account immediately - there's no need for test users or app approval like some other platforms.

Save your configuration​

Double check you have filled out necessary values in the Logto connector configuration area. Click "Save and Done" (or "Save changes") and the GitHub connector should be available now.

Enable GitHub connector in Sign-in Experience​

Once you create a social connector successfully, you can enable it as a "Continue with GitHub" button in Sign-in Experience.

  1. Navigate to Console > Sign-in experience > Sign-up and sign-in.
  2. (Optional) Choose "Not applicable" for sign-up identifier if you need social login only.
  3. Add configured GitHub connector to the "Social sign-in" section.
Sign-in Experience tab

Testing and Validation​

Return to your .NET Core (Blazor WebAssembly) app. You should now be able to sign in with GitHub. Enjoy!

Further readings​

End-user flows: Logto provides a out-of-the-box authentication flows including MFA and enterprise SSO, along with powerful APIs for flexible implementation of account settings, security verification, and multi-tenant experience.

Authorization: Authorization defines the actions a user can do or resources they can access after being authenticated. Explore how to protect your API for native and single-page applications and implement Role-based Access Control (RBAC).

Organizations: Particularly effective in multi-tenant SaaS and B2B apps, the organization feature enable tenant creation, member management, organization-level RBAC, and just-in-time-provisioning.

Customer IAM series Our serial blog posts about Customer (or Consumer) Identity and Access Management, from 101 to advanced topics and beyond.