Using the SAML 2.0 standard, you can configure single sign-on (SSO) for a number of cloud apps. After you set up SSO, your users can use their Google Workspace credentials to sign in to an app using SSO.
Use SAML to set up SSO for LumApps
You must be signed in as a super administrator for this task.
Before you beginLocate your LumApps sign-in page URL. You created the URL when you set up your account. For details, go to LumApps platform creation.
-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu AppsWeb and mobile apps.
-
Click Add appSearch for apps.
- For Enter app name, enter LumApps.
- In the search results, point to LumApps Web (SAML) and click Select.
- In the Google Identity Provider details window, for Option 1: Download IdP metadata, click Download Metadata.
- Click Continue.
Leave the Admin console open. You'll continue with the configuration in the Admin console after the setup steps in the app.
- Open an Incognito browser window, go to the LumApps sign-in page, and sign in with your LumApps administrator account.
- At the top, click Settings Settings.
- For Platform, click Provider settingsIdentity provider.
- Click NewSAML V2.
- For Name, enter a name for your provider.
- For Options, turn on Enable login.
- (Recommended) To quickly create and onboard new users, turn on Allow on-the-fly user creation.
- For Visibility of the login button, choose where you want to show the login button:
- Web & Mobile application
- Web
- Mobile application
- Copy and save the Provider reference.
You need the code to complete the setup in the Admin console. - For Metadata, click Import.
- Go to the metadata file that you downloaded in Step 1, select the file, and click Select.
- Click Save.
- Press Ctrl+Shift+? to open the Advanced Debug info window.
- For Customer, next to the ID number, click Copy and save the ID.
You need the ID to complete setup in the Admin console. - Click anywhere outside of the Advanced Debug info window to close it.
- Return to the Admin console browser tab.
- On the Service provider details page, for Entity ID, replace {customer-id} and {saml-provider-reference} with the values that you copied from LumApps in Step 2.
- (Optional) For Start URL, enter the URL for your LumApps sign-in page using one of the following formats:
- For a vanity URL, use https://custom-name.mydomain.com
- If you don't have a vanity URL, use https://environment.lumapps.com/a/platform/
- Click Continue.
- In the Attribute Mapping window, click Select field and map the following Google directory attributes to their corresponding LumApps attributes. The Primary email, First Name, and Last Name attributes are required.
Google directory attributes LumApps attributes Basic Information > Primary email email Basic Information > First Name firstName Basic Information > Last Name lastName - (Optional) To add additional mappings, click Add Mapping and select the fields that you need to map.
-
(Optional) To enter group names that are relevant for this app:
- For Group membership (optional), click Search for a group, enter one or more letters of the group name, and select the group name.
- Add additional groups as needed (maximum of 75 groups).
- For App attribute, enter the corresponding groups attribute name of the service provider.
Regardless of how many group names you enter, the SAML response includes only groups that a user is a member of (directly or indirectly). For more information, go to About group membership mapping.
- Click Finish.
Before you begin: To turn a service on or off for certain users, put their accounts in an organizational unit (to control access by department) or add them to an access group (to allow access for users across or within departments).
-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu AppsWeb and mobile apps.
- Click LumApps.
- Click User access.
-
To turn a service on or off for everyone in your organization, click On for everyone or Off for everyone, and then click Save.
-
(Optional) To turn a service on or off for an organizational unit:
- At the left, select the organizational unit.
- To change the Service status, select On or Off.
- Choose one:
- If the Service status is set to Inherited and you want to keep the updated setting, even if the parent setting changes, click Override.
- If the Service status is set to Overridden, either click Inherit to revert to the same setting as its parent, or click Save to keep the new setting, even if the parent setting changes.
Note: Learn more about organizational structure.
-
(Optional) To turn on a service for a set of users across or within organizational units, select an access group. For details, go to Use groups to customize service access.
- Ensure that your LumApps user account email domains match the primary domain of your organization’s managed Google Account.
LumApps supports both identity provider-initiated and service provider-initiated SSO.
Verify identity provider-initiated SSO
-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu AppsWeb and mobile apps.
- Click LumApps.
- In the LumApps section, click Test SAML Login.
The app should open in a separate tab. If it doesn’t, troubleshoot the error message and try again. For details on troubleshooting, go to SAML app error messages.
Verify service provider-initiated SSO
- Close all browser windows.
- In an Incognito browser window, open the LumApps sign-in page.
- Click Sign in with name, where name matches the provider name that you added in Step 2.
You should be redirected to the Google sign-in page. - Select your account and enter your password.
After your credentials are authenticated, the app should open.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.