Home > Enterprise Mobility Management > Device Enrollment > SM Enrollment Authentication

SM Enrollment Authentication

To provide a layer of security regarding which devices are able to enroll in a Systems Manager (SM) network, authentication using either Active Directory (AD) or Meraki users/owners can be used. This article will cover how to implement each potential option.

 

There are multiple methods which can be used for performing device enrollment authentication:

  • Managed: Use meraki hosted accounts: Meraki user/owner accounts are used.
  • Active Directory: Use your own Active Directory Server: Authenticate against an Active Directory Server not located in the cloud
    • AD via MX Security Appliance: Authentication requests are proxied through an MX security appliance configured for AD integration.
    • AD via SM Agent: Authentication requests are proxied through a Windows PC/Server or macOS client with the SM Agent installed.
  • Google: Sign in with Google: Authenticate against Google's native Oauth endpoint for use in conjunction with G Suite
  • Microsoft: Authenticate with Microsoft Azure Active Director: Authenticate against Microsoft's Azure Cloud-Hosed Active Directory Soultion
  • OpenID Connect: Use your own OpenID Connect server: Authenticate against any 3rd-party device or service which supports the OpenID Standard

For an additional security, you may want to enable enrollment auto-quarantine to manually approve devices before they can receive your Systems Manager profiles and apps.

iOS devices enrolling through DEP currently do not support enrolling with Azure AD, OpenID, and Google Oauth enrollment authentication. Note that these three methods will also not provide any Group metadata like local Active Directory integration will. 

If you are using a Google Account Bind in conjunction with Android For Work (configured on the Organization > MDM page), Google authentication is not available as it is already being used as part of the AFW enrollment process, and any selection made here would be for use in conjunction with this mechanism.  

 

For each option, begin by navigating to Systems manager > Configure > General > User authentication settings. Then, refer to the appropriate section below to complete the configuration.

Managed Authentication with Meraki Users/Owners

This option utilizes the list of users/owners on the Configure > Owners page in a Systems Manager network. This is best for smaller deployments, or cases where a list of owners is already actively maintained.

  1. Set Authentication settings to "Managed".
  2. Click Save Changes.

 

In order to change/add/delete users, use the Configure > Owners page.

Active Directory via MX Appliance

With this option, any enrollment authentication requests will be proxied through an MX security appliance that is configured for AD integration. This works well when an MX in this configuration is already deployed, or one is available where AD authentication can be enabled.

To configure Active Directory via MX appliance:

  1. Set Authentication settings to "Active Directory".
  2. Set AD gateway type to "Meraki".
  3. Select the desired MX appliance as the Gateway network.
  4. Click Save Changes.

 

Users attempting to enroll devices will now be required to authenticate using their Active Directory username and password. The username should be specified as the user's Active Directory name, not including the domain name (e.g. "testuser," not "domain/testuser")

Note: All communication between an MX security appliance and an Active Directory server will be encrypted using TLS. If AD integration has not yet been configured on the MX, please refer to steps 1-4 of the knowledge base article on configuring Active Directory for Group Policy.

 

Also Note: Users *may* in some AD configurations be able to successfully authenticate using the domain/testuser or testuser@domain.tld formats, but doing so may result in some features not functioning as expected.  

Active Directory via SM Agent

With this option, any enrollment authentication requests will be proxied to an Active Directory server through a Windows device with the Systems Manager agent installed. This Windows device can be a user desktop, or an AD server. However, it must be enrolled in the Systems Manager network, have the SM agent installed (MDM > Add Devices > Windows), and not have any firewall settings preventing it from communicating with the AD server.

To configure Active Directory via SM agent:

  1. Set Authentication settings to "Active Directory".
  2. Set AD gateway type to "SM agent".
  3. Specify the following information regarding the AD server:
    Short domain: The domain users will be authenticated against.
    Server IP: The IP address of the AD server to use.
    LDAP port: Port on the AD server that will be listening for LDAP requests. Default is 3268.
    Domain admin/Password: Username and password of an administrator for this domain.
  4. Select one or more Gateway machines. These are the devices that the enrollment authentication requests will be proxied through. They must have reachability to the AD server provided above.
  5. Click Save Changes.

 

If issues are encountered, ensure that the AD server used has the Global Catalog role enabled. Particularly if multiple domains are configured.

Note: Communication between the Gateway machines and the AD server is not encrypted. Therefore, it is strongly recommended that only the AD server being queried be used as a Gateway machine, in order to keep communication local.

 

Sign in with Google

Oauth against Google is as easy as filling in the allowed Google domain in the specified field. Note that certain enrollment methods like Apple DEP, or Windows profile installation, will not support Google authentication.

 

 

If you have Android For Work bound under Organization > MDM to a Google Domain, Google Authentication will autopopulate to this domain, and this field will not editable as seen in the screenshot above

Azure Active Directory Sign-In

  1. Login to your Microsoft Azure portal.
  2. Select "Azure Active Directory" in the side menu.
  3. Under "Manage" select "Properties". Copy and paste your "Directory ID" into the "Active Directory" field below.
  4. Under "Manage" select "App registrations".
  5. Select "Add" and add a new app of type "Native". The application name will be the name displayed to your users when logging in. Enter "merakismoauth://com.meraki.pcc" for the Redirect URI. Add a second URI, "https://m.meraki.com", after the app is created.
  6. Copy and paste your app's "Application ID" into the "Application Client ID" field below.
  7. >Under "Required permissions" in the newly created app make sure the following permissions are added:
    • "Windows Azure Active Directory" -> "Sign in and read user profile"
    • "Windows Azure Service Management API" -> "Access Azure Service Management as organization users"

 

OpenID Connect 

The OpenID Connect option allows you to point Dashboard/your users at your custom Oauth/OpenID endpoint.  Fill the information from your endpoint into the appropriate fields, but take care to note the following:

 

  • Whitelist "merakismoauth://com.meraki.pcc" and "https://m.meraki.com" as valid redirect URIs for authentication requests.
  • The token endpoint should include the ID token in the "id_token" field in its response to a valid request.
  • The ID token should have an "email" claim that specifies the e-mail address of the authenticated user.
  • The token endpoints should return the public key(s) used to sign ID tokens. Here are sample response formats Systems Manager expects:
You must to post a comment.
Last modified
14:48, 14 Jul 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.

Article ID

ID: 1268

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case