providers/naver
Built-in Naver integration.
NaverProfile
https://developers.naver.com/docs/login/profile/profile.md
Extends
Record<string,any>
Properties
message
message: string;response
response: {
age: string;
birthday: string;
birthyear: string;
email: string;
gender: "F" | "M" | "U";
id: string;
mobile: string;
name: string;
nickname: string;
profile_image: string;
};age?
optional age: string;birthday?
optional birthday: string;birthyear?
optional birthyear: string;email?
optional email: string;gender?
optional gender: "F" | "M" | "U";id
id: string;mobile?
optional mobile: string;name?
optional name: string;nickname?
optional nickname: string;profile_image?
optional profile_image: string;resultcode
resultcode: string;default()
default<P>(options): OAuthConfig<P>Add Naver login to your page.
Setup
Callback URL
https://example.com/api/auth/callback/naver
Configuration
import Auth from "@auth/core"
import Naver from "@auth/core/providers/naver"
const request = new Request(origin)
const response = await Auth(request, {
providers: [Naver({ clientId: NAVER_CLIENT_ID, clientSecret: NAVER_CLIENT_SECRET })],
})Resources
Notes
By default, Auth.js assumes that the Naver provider is based on the OAuth 2 specification.
💡
The Naver provider comes with a default configuration. To override the defaults for your use case, check out customizing a built-in OAuth provider.
Disclaimer If you think you found a bug in the default configuration, you can open an issue.
Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec, we might not pursue a resolution. You can ask for more help in Discussions.
Type parameters
| Type parameter |
|---|
P extends NaverProfile |
Parameters
| Parameter | Type |
|---|---|
options | OAuthUserConfig<P> |
Returns
OAuthConfig<P>