AI Assistant
Help Center AI Assistant is now available
Got questions about Lark? Use our AI chat to find the answers.
00:00
Click and hold to drag
Got It
Try Now
Admin | Configure SAML 2.0 SSO login (Okta or Google)

Admin | Configure SAML 2.0 SSO login (Okta or Google)

4 min read
Available with these plans:
Starter
Basic
Pro
Enterprise
To upgrade your Lark Plan or for more information, contact Support or your Customer Success Manager. The Lark Basic plan supports only specific countries and regions.
I. Intro
🔖
Who can perform these steps: Primary administrators.
Single sign-on (SSO) allows a user to use one set of login credentials to access multiple trusted applications within the organization. Once the primary administrator has enabled this function and configured the settings in the Lark Admin Console, users can select the SSO option when logging in. They'll be able to use the organization domain name and their credentials with the SSO provider to log in to Lark.
Lark supports Security Assertion Markup Language (SAML) 2.0 authentication.
II. Steps
Before enabling SSO, administrators must configure the authentication method. Lark provides two authentication options: SAML authentication and Google account authentication.
For SAML authentication, you can allow members to sign in with Okta, Azure, OneLogin, or other SAML 2.0 identity providers. This article uses Okta as an example.
Configure Okta
Prerequisite: You must have the organization domain name to configure Okta. You can find it in the Lark Admin Console > Settings > Organization Info.
  1. Create a new application
  1. Log in to Okta and click Admin in the upper-right corner.
  • 250px|700px|reset
    image.png
  1. Once logged in, click Applications > Applications. Click Add Application in the upper-left corner.
250px|700px|reset
250px|700px|reset
  1. Click Create New App in the upper-right corner.
  • 250px|700px|reset
  1. Select Web and SAML 2.0 in the pop-up window, and click Create.
  • 250px|700px|reset
  1. In the General Settings window, enter Lark in the App name field and click Next.
  • 250px|700px|reset
  1. According to the organization domain type, enter the following links to the corresponding fields on the SAML Settings page.
  • Domain
    xxx.larksuite.com
    xxx.sg.larksuite.com
    xxx.jp.larksuite.com
    Single sign on URL
    https://www.larksuite.com/suite/passport/authentication/idp/saml/call_back
    https://www.sg.larksuite.com/suite/passport/authentication/idp/saml/call_back
    https://www.jp.larksuite.com/suite/passport/authentication/idp/saml/call_back
    Audience URI
    https://www.larksuite.com
    https://www.sg.larksuite.com
    https://www.jp.larksuite.com
  • 250px|700px|reset
  1. Scroll down, click Add Another to add a new attribute statement, and add a user.email row. Click Next.
250px|700px|reset
250px|700px|reset
  1. Select the options of I'm an Okta customer adding an internal app and This is an internal app that we have created and click Finish.
  • 250px|700px|reset
  1. Go to Applications > Applications > Assignments, click Assign to add members that will need to use this application.
  • 250px|700px|reset
  1. Go to Applications > Applications > Sign On and click View Setup Instructions to get the Lark configurations.
  • 250px|700px|reset
  • The three parameters below will be used in the Lark Admin Console.
  • 250px|700px|reset
  1. Configure the Lark Admin Console.
  1. Go to the Lark Admin Console > Security > Account Security > SSO account login. Click SAML Authentication and enter the three parameters taken from Okta. Then click Verify and Save.
  • 250px|700px|reset
  1. Confirm the configuration information in the pop-up window, and click Save and Enable.
  1. Click Enable login with Okta account.
  • 250px|700px|reset
Configure Google
  1. Go to the Lark Admin Console > Security > Account Security > SSO account login.
  1. Click Edit Current Settings, and select Google account.
  • 250px|700px|reset
  • Note:
  • For members already in the organization, make sure that their Contact email (Organization > Member and Department > Members) matches the Google account they will log in to. If needed, click Details > Edit Basic Info and update the Email field to update Contact email for a member.
  • 250px|700px|reset
  • For members that haven't joined the organization, click Organization > Member and Department > Members Add Members to add them, and enter their Google account email as Contact email.
  • 250px|700px|reset
  1. Click Log in to Google account and enter your Google admin account's address in the new window. Once you've logged in, you'll return to the SSO account login screen.
  • 250px|700px|reset
  1. Confirm all the details on the page are correct, and click Save configuration.
  1. Read the dialog box carefully. Click Enable to apply the configuration.
  • 250px|700px|reset
Note: If you click Cancel, you'll save the configuration but SSO won't be enabled. You can return to the page later and click Enable login with Google account to enable it.
Enable SSO login
Go to the Lark Admin Console > Security > Account Security > SSO account login and turn on SSO.
250px|700px|reset
III. FAQs
How do members sign in with SSO?
Once the administrator has set up SSO, members can choose to log in with SSO on their login page.
  1. Click or tap Continue with SSO and enter the organization's domain.
  1. Enter the login credentials for the SSO provider, such as Okta or Google.
  • Google: Use the credentials for Google Workspace.
  • Okta: Use the credentials for Okta.
250px|700px|reset
image.png
Why can't members sign in with SSO?
It's possible that their Contact email in Lark is different from the address registered with the identity provider (IdP), such as Google or Okta. To verify members' information, go to the Lark Admin Console > Organization > Member and Department > Members and check the Contact email field. If needed, click Details > Edit Basic Info and update the Email field to update Contact email for a member.
Why can't the administrator invite members after SSO is enabled?
It's possible that the members' Contact email in Lark doesn't match the email returned by the IdP (Identity Provider). When the administrator invites members through the invitation code, QR code, or invite link, the invitation may fail because the member enters an email that is not associated with the IdP to sign in with SSO.
Written by: Lark Help Center
Updated on 2024-11-25
How satisfied are you with this content?
Thank you for your feedback!
Need more help? Please contact Support.
0
rangeDom
rangeDom
rangeDom
rangeDom