Skip to main content
Cisco Meraki Documentation

Cisco Secure Connect - Meraki Cloud Authentication


Cisco Secure Connect delivers a turn-key solution that will be bundled with Meraki Cloud Authentication as part of the package. Meraki Cloud Authentication is designed for lab testing and Prof of Value (POV) only as it doesn't require external integrations. It is not recommended to be used in production networks due to the lacking support of user groups and MFA, and it is limited to 200 users only. 

Use Case

  • Customers who don't have an IdP to authenticate users in Secure Connect can leverage Meraki Cloud Authentication as the cloud based authentication.

  • Existing Meraki Cloud Auth customers can continue using Meraki Cloud Authentication with the Secure Connect turn-key offer.


  • API keys should be in place.


1. Go to Secure Connect -> Identities & Connections -> Users, select your identity provider, click Start under "I don't have an Identity Provider".

1.IdP Picker Page.png

2. Then it will direct you to the SCIM Token page, click "Go to Umbrella and generate a SCIM Token" for the next step.

2.SCIM Token Page.png

3. After step 2, you will be landing in Umbrella API Keys page under Admin -> API Keys.

3.Umbrella API Keys Page - 1.png

4. Choose Static Keys and expand Other SCIM IdP, then click Generate Token.

4.Umbrella API Keys Page - 2.png

5. Copy the SCIM token and swivel back to Secure Connect SCIM token page.

Notice: Don't forget to save your SCIM token since the token will only shown once.

5.Umbrella API Keys Page - 3.png

6. Paste the SCIM token and click Next.

6.SCIM Token Page - Token added.png

7. Click + Add User to a add a new user to Meraki Cloud Auth.

7.User Opening Page.png

8. Provide a Name and an Email.  Enable Remote Access "ON" will show if you have Remote Access enabled, otherwise will be grayed out. Click Save to move forward.

8.Add User.png

9. The user shown in the Users page accordingly.

10.Add User Done.png

10. Go to the User's inbox for remote access login information. There is a password and a FQDN for remote worker to login through Secure Client. 

For more details on Remote Access use cases and deployment guide, please click here.

9.Add User email.png

11. If you want to edit a user, click three dots to expand options and choose Edit. (optional)

11.Edit User - 1.png

11. From Edit User page, you can toggle Enable Remote Access ON and OFF based on your own design. (optional)

12.Edit User - 2.png


12. If you want to delete a user, click three dots to expand options and choose Delete. (optional)13.Delete User - 1.png

13. Confirm the user is the one that you want to delete, check the box of "Yes, delete user" and click Delete. (optional)

14.Delete User - 2.png

Deleting User will not disconnect any existing sessions. Session will disconnect based on the configured timeout window. 


  • Was this article helpful?