Lokalise

This feature is available only on the Enterprise plan and can be purchased as an add-on on the Pro plan.

In this article you'll learn how to set up single <a href="https://docs.lokalise.com/en/articles/3339495-saml-based-single-sign-on-sso">sign-on with Lokalise</a> and Google.

Here's a short video that can help you get started:

To get started, log into Lokalise, click on the avatar in the bottom left corner and choose Team settings:

Then, proceed to the Advanced security tab and tick the Enable SSO field:

Team's domain — enter your Google domain.

SAML 2.0 Endpoint (HTTP) — enter SSO URL from the Google SAML app creation page for example <code>https://accounts.google.com/o/saml2/idp?idpid=123abc</code>. Check the <a href="#h_0e10be849e">next section to learn more</a>.

Identity Provider Issuer — enter the Entity ID value from the Google SAML app’s creation page, for example <code>https://accounts.google.com/o/saml2?idpid=123abc</code>.

Public Certificate — copy this value from the Certificate field when creating a new SAML app on Google. Must begin with <code>-----BEGIN CERTIFICATE-----</code> and end with <code>-----END CERTIFICATE-----</code>.

Sign AuthnRequest is not usually required. If you do need this feature, then tick the corresponding field and copy certificate from Service provider Public Certificate field on Lokalise, and then save it to an <code>.crt</code> file. Then you can import this file to a necessary service.

- Team's domain — enter your Google domain.
- SAML 2.0 Endpoint (HTTP) — enter SSO URL from the Google SAML app creation page for example <code>https://accounts.google.com/o/saml2/idp?idpid=123abc</code>. Check the <a href="#h_0e10be849e">next section to learn more</a>.
- Identity Provider Issuer — enter the Entity ID value from the Google SAML app’s creation page, for example <code>https://accounts.google.com/o/saml2?idpid=123abc</code>.
- Public Certificate — copy this value from the Certificate field when creating a new SAML app on Google. Must begin with <code>-----BEGIN CERTIFICATE-----</code> and end with <code>-----END CERTIFICATE-----</code>.
- Sign AuthnRequest is not usually required. If you do need this feature, then tick the corresponding field and copy certificate from Service provider Public Certificate field on Lokalise, and then save it to an <code>.crt</code> file. Then you can import this file to a necessary service.

If you need to reconfigure the same SSO domain for another Lokalise team, please follow these steps:

Empty all fields within Single sign-on (SSO) section of the Advanced security tab.

Proceed with configuring SSO for the other Lokalise team.

1. Empty all fields within Single sign-on (SSO) section of the Advanced security tab.
2. Uncheck Enable SSO setting.
3. Click on Save.
4. Proceed with configuring SSO for the other Lokalise team.

Please note that after updating the SAML app configuration, it may take some time for your changes to be propagated. Thus please wait a few minutes before testing the SAML authentication with Lokalise.

Proceed to <code>admin.google.com</code>, click Add app &gt; Add custom SAML app.

You'll be presented with the SSO configuration:

- SSO URL — paste this value into the SAML 2.0 Endpoint (HTTP) field on Lokalise.
- Entity ID — paste this value into the Identity Provider Issuer field on Lokalise.
- Certificate — paste this value into the Public Certificate field on Lokalise.

Next, proceed to the Service provider details tab. Fill in the following fields:

- ACS URL — copy the ACS URL Preview value from Lokalise.
- Entity ID — enter <code>https://lokalise.com</code>
- Name ID format — choose email. Must be unique, pseudo-random, and will not change for the user over time — like an employee ID number.

Next, set up Attribute mapping. Click Add mapping and add the following:

- Basic information &gt; First name and enter <code>first_name</code> as the app attribute.
- Basic information &gt; Last name and enter <code>last_name</code> as the app attribute.
- Basic information &gt; Primary email and enter <code>User.Email</code> as the app attribute.

Click Finish to complete the app creation.

- Enter you app name.
- Optionally, upload your app's icon.
- You'll be presented with the SSO configuration:
 - SSO URL — paste this value into the SAML 2.0 Endpoint (HTTP) field on Lokalise.
 - Entity ID — paste this value into the Identity Provider Issuer field on Lokalise.
 - Certificate — paste this value into the Public Certificate field on Lokalise.
- Next, proceed to the Service provider details tab. Fill in the following fields:
 - ACS URL — copy the ACS URL Preview value from Lokalise.
 - Entity ID — enter <code>https://lokalise.com</code>
 - Name ID format — choose email. Must be unique, pseudo-random, and will not change for the user over time — like an employee ID number.
- Next, set up Attribute mapping. Click Add mapping and add the following:
 - Basic information &gt; First name and enter <code>first_name</code> as the app attribute.
 - Basic information &gt; Last name and enter <code>last_name</code> as the app attribute.
 - Basic information &gt; Primary email and enter <code>User.Email</code> as the app attribute.
- Click Finish to complete the app creation.

Once everything is set up, proceed to <code>https://app.lokalise.com/sso</code> and enter user email associated with the Google domain. Upon the first log in, you'll be asked to confirm your email:

Configuration on Lokalise

Configuration on Google

Logging in with SSO