Single Sign-On

SSO lets users sign in with services like GitHub, Google, Kakao, or Naver. In Akan, you usually only write the callback once and let the service decide whether to sign in or continue signup.

User clicks a social login button.
The provider confirms who the user is.
Akan callback receives the profile.
The service signs in or redirects to signup.

Register Providers

First, register the providers your app supports. Each provider needs credentials from that service's developer console.

Example options

Write A Callback

The callback should stay small. Take the provider profile, find the account id, and pass it to your user service.

`SSO.Google` is a guard. It checks that Google SSO is configured before the login start route or callback runs. The start route redirects to Google, and the callback exchanges Google's `code` for a profile.

Small callback

Account Id

Different providers call the user's identity by different names. Normalize it into one `accountId` before calling your service.

GitHub often uses `username`.
Google often uses the first email address.
Kakao and Naver commonly use `email`.

Normalize provider profile

Redirects

After the callback, the service usually chooses one of three places to go.

Existing user: go to the signed-in page.
New user: go to the signup continuation page.
Error: go to an error page with a clear message.

Tips

Keep provider-specific code inside the callback. Keep sign-in rules inside the service.
Use the same service method after every provider normalizes `accountId`.
Always prepare success, signup, and error redirects before starting SSO.

Single Sign-On

SSO lets users sign in with services like GitHub, Google, Kakao, or Naver. In Akan, you usually only write the callback once and let the service decide whether to sign in or continue signup.

User clicks a social login button.
The provider confirms who the user is.
Akan callback receives the profile.
The service signs in or redirects to signup.

Register Providers

First, register the providers your app supports. Each provider needs credentials from that service's developer console.

Example options

Write A Callback

The callback should stay small. Take the provider profile, find the account id, and pass it to your user service.

Small callback

Account Id

Different providers call the user's identity by different names. Normalize it into one `accountId` before calling your service.

GitHub often uses `username`.
Google often uses the first email address.
Kakao and Naver commonly use `email`.

Normalize provider profile

Redirects

After the callback, the service usually chooses one of three places to go.

Existing user: go to the signed-in page.
New user: go to the signup continuation page.
Error: go to an error page with a clear message.

Tips

Keep provider-specific code inside the callback. Keep sign-in rules inside the service.
Use the same service method after every provider normalizes `accountId`.
Always prepare success, signup, and error redirects before starting SSO.