BuckeyePass Integration Overview
This overview is meant to provide system and/or application owners with all the steps necessary to add multi-factor authentication to their existing authentication process.
NOTE: Please click on any of the steps below to view more detailed information.
Engagement Form
System Owners have the ability to submit a BuckeyePass engagement form in Service Now. Depending on the implementation, the BuckeyePass team may reach out to System Owners as well. In either scenario, a Service Now ticket to the BuckeyePass Integration service must be submitted to start the process.
Review
The BuckeyePass team will review all engagement forms to ensure all required information is captured properly. If needed, the BuckeyePass team will circle back with the system owners for clarifications or corrections.
Kickoff Meeting
The kickoff meeting will be held once a Service Now form has been received. System Owners, technical contacts, and the BuckeyePass team will be invited to attend. This meeting is meant to:
- Cover the submitted form
- Go over any communication needs
- Gather a current user list for your system
- Establish target dates
- Answer any existing questions
- Gather any questions to escalate to the vendor
Please note: If a user list is available ahead of time it can be sent to BuckeyePass@osu.edu with the Service Desk ticket number in the subject line. Once this meeting is complete, the API keys needed to integrate with BuckeyePass will be provided to the proper contacts, and work can begin to implement the solution. The BuckeyePass team will be available for further meetings or emails if any roadblocks or issues are encountered along the way.
Implementation
The technical contacts will be responsible for most of the implementation process. System owners and technical contacts may need to engage the BuckeyePass team for further clarification or to escalate any roadblocks to the vendor. The method to engage the vendor is through the BuckeyePass team.
Choose an integration type from the list below for detailed instructions on implementing Duo.
Please note: If you would like a full list of all supported systems please review the Vendor Documents.
Go or No Go Meeting
This can be in the form of an email confirmation or quick meeting depending on the size and criticality of the system. If change requests need to be in place for go live then this information can be captured during the meeting.
Go Live
Go live is the actual implementation of the BuckeyePass solution. All impacted parties should be informed and required processes for production changes should be followed.
Service Now Ticket Closed
The BuckeyePass Integration is considered complete at this point so the Service Now ticket can be marked complete. The entire process is considered complete.