Add 2-Step to your Campus Application or Service

Overview

If you would like to integrate a service that does not use Single Sign On with MFA (CalNet 2-Step), please review the following requirements and procedures.

Integration Requirements

• Review Documentation: Refer to the Duo documentation for your specific service. Look for the integration guide that matches the application you wish to protect.
• Identifier Standard: Only CalNet IDs will be used as the account name in Duo. Ensure your service requires users to authenticate using their standard CalNet ID.
• Staging Environment: We will provide an administrator account in a staging environment where you can configure your service and add test users. Review the vendor guide on how to create your application for technical steps.
• Feature Restrictions: For initial rollouts, we cannot accommodate the use of Duo groups or aliases. Do not utilize these features during configuration.
• Production Migration: Once your testing is complete and successful, we will copy your configuration from staging to the main production environment.

Administrative Responsibilities

• Adoption: Application owners are responsible for user adoption, including all communication, outreach, and consulting for their specific user base.
• Technical Support: You are responsible for providing direct support to your users for login issues related to your specific application. The general campus Help Desk only provides support for users managing their devices within the CalNet Account Manager.

How to Request Integration

To initiate an integration request, contact calnet-admin@berkeley.edu with the following details:

• Information about the service you want to enable.
• Planned implementation date.