Meraki cloud application

You must be signed in as a super administrator for this task.

With Security Assertion Markup Language (SAML), your users can sign in to enterprise cloud applications with their Google Cloud credentials.

Set up SSO via SAML for Meraki

Meraki requires an X.509 certificate fingerprint, rather than an X.509 certificate. Before proceeding with the configuration steps, use a conversion utility to convert the X.509 certificate downloaded in step 1 into an X.509 certificate fingerprint.

Note: Before performing these steps, you need to create a new custom attribute in the Google Admin console called Role, which you’ll map to the role in Meraki.

Step 1: Set up Google as a SAML identity provider (IdP)
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the plus (+) icon at the bottom right. 
  4. Locate and click Meraki in the application list.
  5. On the Google IDP Information page, download the Certificate.
  6. Click Next.

    The Basic information window shows the Application name and Description seen by users.

  7. Click Next.
  8. On the Service Provider Details page, edit the ACS URL {consumer-url-provided-by-sp} with the Meraki provided Consumer URL
  9. On the Attribute Mapping page, set Select category and Select user field values as follows for the listed attributes:
Application attribute Select category Select user field
username Basic Information First Name
role Role Role in Meraki
  1. Click Finish.
Step 2: Set up Meraki as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to https://meraki.cisco.com with your organization’s Meraki administrator account.
  3. Go to Organization and then Settings.
  4. Under SAML Configuration from the SAML SSO list, select SAML SSO enabled.
  5. In the X.509 cert SHA1 fingerprint field, provide the X.509 certificate fingerprint of the Google IdP certificate.
  6. Click Save Changes.
Step 3: Enable the Meraki app
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Select Meraki.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. To turn on or off a service only for users in an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. To keep the service turned on or off even when the service is turned on or off for the parent organizational unit, click Override.
    4. If the organization's status is already Overridden, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. Ensure that your Meraki user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working

Meraki supports IdP initiated access only. SP initiated access is not supported. This can be verified by launching the app from the Google Admin Console.

Was this helpful?
How can we improve it?