Meraki cloud application

1. Sign in to your Google Admin console.

   Sign in using an account with super administrator privileges (does not end in @gmail.com).

2. In the Admin console, go to Menu  AppsWeb and mobile apps.
3. Click Add appSearch for apps.
4. Enter Meraki in the search field.
5. In the search results, hover over the Meraki SAML app and click Select.
6. On the Google Identity Provider details page, copy the X.509 certificate and use it to calculate fingerprint using SHA-1 algorithm.
7. Click Continue.
8. On the Service provider details page, edit the ACS URL, replacing {consumer-url-provided-by-sp} with the Meraki-provided Consumer URL. 
9. On the Attribute Mapping page, click the Select field menu and map the following Google directory attributes to their corresponding Meraki attributes:
    

   Google directory attribute	Meraki attribute
   Role > Role in Meraki	role
   Basic Information > First Name	username

10. (Optional) To enter group names that are relevant for this app:

    1. For Group membership (optional), click Search for a group, enter one or more letters of the group name, and select the group name.
    2. Add additional groups as needed (maximum of 75 groups).
    3. 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.

11. Click Finish.

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  Settings.
4. Under SAML Configuration from the SAML SSO list, select SAML SSO enabled.
5. In the X.509 cert SHA1 fingerprint field, enter the SHA-1 certificate fingerprint you calculated in Step 1 above.
6. Click Save Changes.

1. Sign in to your Google Admin console.

   Sign in using an account with super administrator privileges (does not end in @gmail.com).

2. In the Admin console, go to Menu  AppsWeb and mobile apps.
3. Select Meraki.
4. Click User access.

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

6. (Optional) To turn a service on or off for an organizational unit:

   1. At the left, select the organizational unit.
   2. To change the Service status, select On or Off.
   3. 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.
7. (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.
8. Ensure that your Meraki user account email IDs match those in your Google domain.

Note: Meraki only supports IdP initiated SSO. You can’t use SSO if you sign in directly to Meraki.

1. Sign in to your Google Admin console.

   Sign in using an account with super administrator privileges (does not end in @gmail.com).

2. In the Admin console, go to Menu  AppsWeb and mobile apps.
3. Select Meraki.
4. At the top left, click Test SAML login. 

   Meraki should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.

You should be automatically redirected to your Meraki account.