As business applications move from on-premises to cloud hosted solutions, users experience password fatigue due to disparate logons for different applications. Single sign-on (SSO) technologies seek to unify identities across systems and reduce the number of different credentials a user has to remember or input to gain access to resources.
While SSO is convenient for users, it presents new security challenges. If a user's primary password is compromised, attackers may be able to gain access to multiple resources. In addition, as sensitive information makes its way to cloud-hosted services it is even more important to secure access by implementing two-factor authentication.
Duo Single Sign-On, now in public beta, is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of Meraki logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Single Sign-On acts as an identity provider (IdP), authenticating your users using existing on-premises Active Directory (AD) or any SAML 2.0 IdP and prompting for two-factor authentication before permitting access to Meraki.
Duo Single Sign-On's public beta is available in Duo Beyond, Duo Access, and Duo MFA plans, which also include the ability to define policies that enforce unique controls for each individual SSO application. For example, you can require that Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing Meraki. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Before configuring Meraki you'll first need to configure Duo Single Sign-On with a working an authentication source.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the "Single Sign-On (hosted by Duo)" entry for Meraki in the applications list. Click Protect to the far-right to start configuring Meraki. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the Meraki page under Metadata later.
Add Duo Single Sign-On as a new SSO provider for Meraki.
Log on to the Meraki as an administrative user and navigate to Organization → Configure → Settings.
Scroll down until you find Authentication.
In the SAML SSO dropdown select SAML SSO enabled the setting will automatically expand.
Make note of the Consumer URL — you will need this information later.
Copy the X.509 cert SHA1 fingerprint from the Duo Admin Panel Certificate Fingerprints section and paste it into the Meraki X509 cert SHA1 fingerprint field.
Copy the SLO logout URL from the Duo Admin Panel Metadata section and paste it into the Meraki SLO logout URL (optional) field.
After you've entered all the required information scroll down and click Save Changes.
Next, create a SAML role in Meraki that uses the SAML provider you just created, and grant Meraki service and resource access to that role.
In the Meraki console navigate to Organization → Configure → Administrators.
Click the Add SAML role button.
Enter a role name in the Role field. Add organization access and permissions to this role as needed. Click the Create admin button when finished.
Click Save changes on the "Administrators" page.
Important: E-mail addresses used for users in your SAML role group cannot exist in Meraki. If an e-mail address already exists, the user will receive an error when attempting to log in via SSO.
Learn more about Meraki SSO at Meraki Support.
Return to the Duo Admin Panel with the Meraki application open. Find the Service Provider section.
Copy the Consumer URL from Meraki SAML Configuration settings page into the Consumer URL field inthe Duo Admin Panel.
Under Role attributes you can type the name of the Meraki role you defined earlier in the Meraki Role field and which users should have access to that role by selecting Duo groups in the Duo Groups field. The members of those groups will be given access to that role in Meraki.
If you have additional Meraki roles you can click the + button next to the "Duo Groups" field to add additional rows.
Meraki uses the Mail attribute when authenticating. We've mapped the <Email Address> bridge attribute to Duo Single Sign-On supported authentication source attributes as follows:
|Bridge Attribute||Active Directory||SAML IdP|
You can adjust additional settings for your new SAML application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy.
Scroll to the bottom of the page and click the Save button.
You can log on to Meraki with IdP-initiated SSO using the IdP-initiated Login URL provided under the "Metadata" section of the Meraki application in the Duo Admin Panel (https://sso-abc1def2.sso.duosecurity.com/saml2/sp/DIABC123678901234567/metadata).
Enter your primary directory logon information and approve Duo two-factor authentication.
Congratulations! Your Meraki console users now authenticate using Duo Single Sign-On.
Meraki does not support SP-initiated SSO login at this time.
To minimize additional Duo two-factor prompts when switching between Meraki and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.
Microsoft's Active Directory Federation Services (AD FS) is a popular choice for SSO because it easily integrates with the AD identity store many organizations already have deployed. Duo's support for cloud applications and SSO drops in to an existing AD FS installation to provide secondary authentication after a user passes primary authentication (successful Active Directory logon).
If you don't already have AD federation running the first step is to install and configure Microsoft AD FS in your organization. Deployment Guides for AD FS versions 2.1, and 3.0/4.0 are available from Microsoft.
Once your AD FS services are up and running, the second step is to configure the SSO partnership between your AD FS service and the external cloud resource, in this case Meraki. Learn more about configuring Meraki SSO with AD FS at the Meraki Support site.
After you have successfully configured and tested AD FS SSO login to Meraki using your AD domain credentials, you can then install the Duo AD FS integration. AD FS protection is included with Duo's paid plans.
With the Duo integration for AD FS installed, users pass primary authentication to the AD FS service as usual. Once primary authentication succeeds, users are forwarded to the Duo service for secondary authentication. After approving logon using one of Duo's authentication methods, the user is fully logged in to Meraki.
Using a third-party SSO provider for cloud application access? Duo partners with leading cloud SSO providers like Okta and OneLogin to secure access with our strong and flexible authentication platform.