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 WeChat (Native) sign-in experience (user authentication) with Auth.js (Next Auth) and Logto.
Prerequisites
- A running Logto instance. Check out the introduction page to get started.
- Basic knowledge of Auth.js (Next Auth).
- A usable WeChat (Native) account.
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 Traditional web application, simply follow these steps:
- 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.
- In the opening modal, click the "Traditional web" section or filter all the available "Traditional web" frameworks using the quick filter checkboxes on the left. Click the "Auth.js (Next Auth)" framework card to start creating your application.
- 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 Auth.js (Next Auth) with Logtoβ
- In this guide, we assume you have set up Next Auth in your Next.js project. If you haven't, check out the Next Auth documentation to get started.
Installationβ
Install Auth.js via your favorite package manager:
- npm
- pnpm
- yarn
npm i next-auth@beta
pnpm add next-auth@beta
yarn add next-auth@beta
See Auth.js documentation for more details.
Set up Auth.js providerβ
You can find and copy "App Secret" from application details page in Admin Console:

Modify your API route config of Auth.js, add Logto as an OIDC provider:
- Auth.js v5
- Next Auth v4
Setup environment variables:
AUTH_LOGTO_ISSUER=https://xxxx.logto.app/oidc
AUTH_LOGTO_ID=your-logto-app-id
AUTH_LOGTO_SECRET=your-logto-app-secret
import { handlers } from '@/auth';
export const { GET, POST } = handlers;
import NextAuth from 'next-auth';
import Logto from 'next-auth/providers/logto';
export const { handlers, signIn, signOut, auth } = NextAuth({
providers: [Logto],
});
Then you can also add an optional Middleware to keep the session alive:
export { auth as middleware } from '@/auth';
import NextAuth from 'next-auth';
const handler = NextAuth({
providers: [
{
id: 'logto',
name: 'Logto',
type: 'oauth',
// You can get the well-known URL from the Logto Application Details page,
// in the field "OpenID Provider configuration endpoint"
wellKnown: 'https://xxxx.logto.app/oidc/.well-known/openid-configuration',
authorization: { params: { scope: 'openid offline_access profile email' } },
clientId: '<logto-app-id>',
clientSecret: '<logto-app-secret>',
client: {
id_token_signed_response_alg: 'ES384',
},
profile(profile) {
// You can customize the user profile mapping here
return {
id: profile.sub,
name: profile.name ?? profile.username,
email: profile.email,
image: profile.picture,
};
},
},
],
});
export { handler as GET, handler as POST };
- Replace the
wellKnown
URL with your Logto application's "OpenID Provider configuration endpoint". - Replace the
clientId
andclientSecret
with your Logto application's ID and secret. - Customize the
profile
function to map the user profile to the Next Auth user object, the default mapping is shown in the example. - Remember to set the
id_token_signed_response_alg
toES384
.
You can find more details in the Auth.js documentation.
Configure sign-in redirect URIβ
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/
.
Let's switch to the Application details page of Logto Console. Add a Redirect URI http://localhost:3000/api/auth/callback/logto
and click "Save changes".

Implement sign-in and sign-outβ
Implement sign-in and sign-out buttonβ
import { signIn } from '@/auth';
export default function SignIn() {
return (
<form
action={async () => {
'use server';
await signIn('logto');
}}
>
<button type="submit">Sign In</button>
</form>
);
}
import { signOut } from '@/auth';
export function SignOut() {
return (
<form
action={async () => {
'use server';
await signOut();
}}
>
<button type="submit">Sign Out</button>
</form>
);
}
Show sign-in and sign-out button in the pageβ
import SignIn from './components/sign-in';
import SignOut from './components/sign-out';
import { auth } from '@/auth';
export default function Home() {
const session = await auth();
return <div>{session?.user ? <SignOut /> : <SignIn />}</div>;
}
Above is a simple example, you can check the Auth.js documentation for more details.
Checkpointβ
Now, you can test your application to see if the authentication works as expected.
Add WeChat (Native) connectorβ
To enable quick sign-in and improve user conversion, connect with Auth.js (Next Auth) 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:
- Navigate to Console > Connectors > Social Connectors.
- Click "Add social connector" and select "WeChat (Native)".
- Follow the README guide and complete required fields and customize settings.

If you are following the in-place Connector guide, you can skip the next section.
Set up WeChat mobile appβ
Create a mobile app in the WeChat Open Platformβ
You can skip some sections if you have already finished.
Create an accountβ
Open https://open.weixin.qq.com/, click the "Sign Up" button in the upper-right corner, then finish the sign-up process.
Create a mobile appβ
Sign in with the account you just created. In the "Mobile Application" (η§»ε¨εΊη¨) tab, click the big green button "Create a mobile app" (εε»Ίη§»ε¨εΊη¨).

Let's fill out the required info in the application form.

Basic infoβ
Most of them are pretty straightforward, and we have several tips here:
- If you just want to test WeChat sign-in and the app is not on the App Store, in the "App is available" section, choose "No" to skip the "App download link".
- The "App operation flow chart" looks tricky. From our experience, you need to prepare a simple flowchart and several app screenshots to improve the possibility of passing the review.
Click "Next step" to move on.
Platform infoβ
You can configure one or both iOS and Android platforms to integrate Logto with WeChat native sign-in.
iOS app
Check "iOS app" (iOS εΊη¨), then check the target device type of your app accordingly.

If you chose "No" for the App Store availability, you cloud skip filling out the "AppStore download address" here.
Fill out Bundle ID, Test version Bundle ID, and Universal Links (actually, only one link is needed π).
Bundle ID and Test version Bundle ID can be the same value.
WeChat requires universal link for native sign-in. If you haven't set up or don't know it, please refer to the Apple official doc.
Android app
Check "Android app" (Android εΊη¨).

Fill out Application Signing Signature (εΊη¨ηΎε) and Application Package Name (εΊη¨ε ε).
You need to sign your app to get a signature. Refer to the Sign your app for more info.
After finish signing, you can execute the signingReport
task to get the signing signature.
./gradlew your-android-project:signingReport
The MD5
value of the corresponding build variant's report will be the Application Signing Signature (εΊη¨ηΎε), but remember to remove all semicolons from the value and lowercase it.
E.g. 1A:2B:3C:4D
-> 1a2b3c4d
.
Waiting for the review resultβ
After completing the platform info, click "Submit Review" to continue. Usually, the review goes fast, which will end within 1-2 days.
We suspect the reviewer is allocated randomly on each submission since the standard is floating. You may get rejected the first time, but don't give up! State your status quo and ask the reviewer how to modify it.
Enable WeChat native sign-in in your appβ
iOSβ
We assume you have integrated Logto iOS SDK in your app. In this case, things are pretty simple, and you don't even need to read the WeChat SDK doc:
1. Configure universal link and URL scheme in your Xcode project
In the Xcode project -> Signing & Capabilities tab, add the "Associated Domains" capability and the universal link you configured before.

Then goes to the "Info" tab, add a custom URL scheme with the WeChat App ID.

Finally open your Info.plist
, add weixinULAPI
and weixin
under LSApplicationQueriesSchemes
.

We know these actions are not very reasonable, but this is the minimum workable solution we found. See the magical official guide for more info.
2. Add LogtoSocialPluginWechat
to your Xcode project
Add the framework:

And add -ObjC
to your Build Settings > Linking > Other Linker Flags:

The plugin includes WeChat Open SDK 1.9.2. You can directly use import WechatOpenSDK
once imported the plugin.
3. Add the plugin to your LogtoClient
init options
let logtoClient = LogtoClient(
useConfig: config,
socialPlugins: [LogtoSocialPluginWechat()]
)
4. Handle onOpenURL
properly
The function LogtoClient.handle(url:)
will handle all the native connectors you enabled. You only need to call it once.
// SwiftUI
YourRootView()
.onOpenURL { url in
LogtoClient.handle(url: url)
}
// or AppDelegate
func application(_ app: UIApplication, open url: URL, options: /*...*/) -> Bool {
LogtoClient.handle(url: url)
}
Androidβ
We assume you have integrated Logto Android SDK in your app. In this case, things are pretty simple, and you don't even need to read the WeChat SDK doc:
1. Add Wechat Open SDK
to your project
Ensure the mavenCentral()
repository is in your Gradle project repositories:
repositories {
// ...
mavenCentral()
}
Add the Wechat Open SDK to your dependencies:
dependencies {
// ...
api("com.tencent.mm.opensdk:wechat-sdk-android:6.8.0") // kotlin-script
// or
api 'com.tencent.mm.opensdk:wechat-sdk-android:6.8.0' // groovy-script
}
2. Introduce WXEntryActivity
to your project
Create a wxapi
package under your package root and add the WXEntryActivity
in the wxapi
package (Take com.sample.app
as an example):
// WXEntryActivity.kt
package com.sample.app.wxapi
import io.logto.sdk.android.auth.social.wechat.WechatSocialResultActivity
class WXEntryActivity: WechatSocialResultActivity()
// WXEntryActivity.java
package com.sample.app.wxapi
import io.logto.sdk.android.auth.social.wechat.WechatSocialResultActivity
public class WXEntryActivity extends WechatSocialResultActivity {}
The final position of the WXEntryActivity
under the project should look like this (Take Kotlin as an example):
src/main/kotlin/com/sample/app/wxapi/WXEntryActivity.kt
3. Modify the AndroidManifest.xml
Add the following line to your AndroidManifest.xml
:
\<?xml version="1.0" encoding="utf-8"?>
\<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.sample.app">
\<application>
\<!-- line to be added -->
\<activity android:name=".wxapi.WXEntryActivity" android:exported="true"/>
\</application>
\</manifest>
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 WeChat (Native) connector should be available now.
Enable WeChat (Native) connector in Sign-in Experienceβ
Once you create a social connector successfully, you can enable it as a "Continue with WeChat (Native)" button in Sign-in Experience.
- Navigate to Console > Sign-in experience > Sign-up and sign-in.
- (Optional) Choose "Not applicable" for sign-up identifier if you need social login only.
- Add configured WeChat (Native) connector to the "Social sign-in" section.

Testing and Validationβ
Return to your Auth.js (Next Auth) app. You should now be able to sign in with WeChat (Native). 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.