Every app needs authentication and authorization. Logto is an Auth0 alternative designed for modern apps and SaaS products.
In this article, we will go through the steps to quickly build the Naver sign-in experience (user authentication) with .NET Core (Blazor WebAssembly) and Logto.
Prerequisites
- A running Logto instance. Check out the introduction page to get started.
- Basic knowledge of .NET Core (Blazor WebAssembly).
- A usable Naver account.
Create an application in Logto
In you browser, open a new tab and enter the link of Logto Admin Console.
Once the page is loaded, in the "Get Started" section click the View all
link to open the application framework list page.
Choose your application type
In the opening modal, scroll to 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.
Enter application name
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 Logto SDK
- The following demonstration is built on .NET Core 8.0 and Blorc.OpenIdConnect.
- The .NET Core sample projects are available in the GitHub repository.
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:
<head>
<!-- ... -->
<script src="_content/Blorc.Core/injector.js"></script>
<!-- ... -->
</head>
Register services
Add the following code to the Program.cs
file:
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();
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:
- Your app invokes the sign-in method.
- The user is redirected to the Logto sign-in page. For native apps, the system browser is opened.
- The user signs in and is redirected back to your app (configured as the redirect URI).
Regarding redirect-based sign-in
- This authentication process follows the OpenID Connect (OIDC) protocol, and Logto enforces strict security measures to protect user sign-in.
- 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.
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
.
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:
{
// ...
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:
@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:
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:
- Run your application, you will see the sign-in button.
- Click the sign-in button, the SDK will init the sign-in process and redirect you to the Logto sign-in page.
- After you signed in, you will be redirected back to your application and see the sign-out button.
- Click the sign-out button to clear local storage and sign out.
Open your .NET Core (Blazor WASM) app to test if the integration works. When you click the "Sign In" button, the page should be redirected to a Logto sign-in page, and you should be able to create a new account by entering username and password and complete the sign-in process.
Add Naver connector
To add a social connector, go to the "Connector" tab in the Admin Console, then click on "Social connectors". From there, click "Add social connector".
In the openning modal, select "Naver" and click "Next".
On the next page, you will see a two-column layout with the README content on the left and configuration on the right.
Feel free to follow the README file in place or read the following section to complete the configuration process. If you follow the in-place guide, you can skip the next section.
Set up Naver login
Developer Site Only Korean Support Now
Currently Naver Developers
site only supports Korean. Please consider use a translator.
For the Production
- For the production, you have to get review from Naver team.
Otherwise, only registered users can sign in.
- You can add a tester from
맴버관리(Member Manage)
menu.
- You can add a tester from
- To get a review, please check
애플리케이션 개발 상태(Application Devlopment Status)
fromAPI 설정(API Setting)
from your application project setting.
Set up a project in the Naver Developers
- Visit the Naver Developers and sign in with your Naver account.
- Click the Application -> 어플리케이션 등록 from the menu to create new project.
- Follow the instruction below to create application.
Application Name (어플리케이션 이름)
- Type your application name on
어플리케이션 이름
(This name is shown while a user sign in.)
API Usage (사용 API)
- Choose
네이버 로그인(Naver Login)
for사용 API(API Usage)
- Check
이메일 주소(Email Address), 별명(Nickname), 프로필 사진(Profile Image)
as필수(Neccessary)
from권한(Role)
(You can check추가(Add)
as optional these options, but you cannot get the information from the user.)
Sign in Open API Service Environment (로그인 오픈 API 서비스 환경)
- For
로그인 오픈 API 서비스 환경(Sign in Open API Service Environment)
, add two environmentPC웹(PC Web)
and모바일웹(Mobile Web)
.
PC Web (PC 웹)
- For
서비스 URL(Service URL)
, typehttp(s)://YOUR_URL
(ex. https://logto.io) - For
네이버 로그인(Naver Login) Callback URL
, typehttp(s)://YOUR_URL/callback/connector_id
(e.g. https://logto.io/callback/connector_id)
Mobile Web (Mobile 웹)
- For
서비스 URL(Service URL)
, typehttp(s)://YOUR_URL
(ex. https://logto.io) - For
네이버 로그인(Naver Login) Callback URL
, typehttp(s)://YOUR_URL/callback/connector_id
(e.g. https://logto.io/callback/connector_id)
⚠️ Caution
The
connector_id
can be found on the top bar of the Logto Admin Console connector details page.
Configure Logto
Config types
Name | Type |
---|---|
clientId | string |
clientSecret | string |
clientId
clientId
is Client ID
of your project.
(You can find it from 애플리케이션 정보(Application Info)
of your project from Naver developers.)
clientSeceret
clientSecret
is Client Secret
of your project.
(You can find it from 애플리케이션 정보(Application Info)
of your project from Naver developers.)
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 Naver connector should be available now.
Enable Naver connector in Sign-in Experience
Switch to the "Sign-in experience" tab, then click the "Sign-up and sign-in" tab.
If it's the first time you enter the tab, you will see a quick introduction about Sign-in Experience and its basic configuration.
Select "None" for the "Sign-up identifier" to provide minimum sign-up effort for Naver sign-in, which may increase your conversion rate.
In the "Social sign-in" section, add "Add Social Connector" and choose "Naver". Then you should be able to see a button with text "Continue with Naver" in the preview section.
Finally, click "Save changes" on the bottom right corner.
Testing and Validation
Return to your .NET Core (Blazor WebAssembly) app. You should now be able to sign in with Naver. Enjoy!
Further readings
Protect your API For native and single page apps, you'll need to call one or more API endpoints to retrieve and update data.
Learn more about identifying who's who and keeping your API secure.
User management We know you care about user management and activities, as we also do.
Learn more about how to know your users and see the figures like DAU and MAU graphically.
Localization From one regional business to a global corporate, the willingness to offer the best user experience won't change.
You can change current language phrases or add a new language without friction.
Customer IAM series Our serial blog posts about Customer (or Consumer) Identity and Access Management, from 101 to advanced topics and beyond.