IMS/1EdTech, the consortium who created and maintains the OneRoster specification, has deprecated OAuth1 for OneRoster connections. Campus supports OAuth 2; not all of our Digital Learning Partners (DLPs) support OAuth 2 yet.
This article provides instructions for migrating DLPs to OAuth 2. General migration instructions are provided first, followed by partner-specific information. Partners receive information in different ways; expand a section below to view more information.
In conjunction with this OAuth change, all Base URLs have been changed. The Base URL is part of the credentials sent to the vendor as part of the configuration process to establish a connection.
The Digital Learning Applications article provides more information about these connections, including instructions for setting them up.
Timeline
Districts have between now and June 30, 2023 to move their connections from OAuth 1 to OAuth 2, or to share the updated Base URLs with partners.
If a connection is not updated by June 30, 2023, the connection will stop working after that date.
Migration Instructions
All connections need to be updated in some way, whether by generating a new connection with OAuth 2 or sharing a new Base URL:
Current connection uses OneRoster 1.1 with OAuth 1*
Current connection uses OneRoster 1.1 with OAuth 2 or OneRoster 1.2
Generate a new connection, selecting either OneRoster 1.2, if supported by the partner, or OneRoster 1.1 with OAuth 2.
Once the new connection is in place, disable the previous connection.
* Most common scenario
Share the updated Base URL with the partner.
All newly-created connections will already use the new Base URL.
This Base URL is updated with the release of Campus.2235. The legacy Base URL for the connection is available in the Legacy Configuration area.
To see the OneRoster and OAuth versions of a connection, click the partner to view their connections. Versions are shown for each connection. Hover over the yellow warning icon for more information about what needs to be updated for the connection.
The OneRoster and OAuth Versions are listed for each connection.
Connection Tracker
To keep track needed updates, click the button to view a list of all connections that have been updated.
A connection with a yellow warning icon indicates that that connection uses OAuth 1 and must be replaced.
A connection with a clickable checkbox only needs to have its new Base URL shared. Once the URL is shared, mark the checkbox to record the connection as updated. Once the checkbox is marked for a connection, the yellow warning is cleared from the partner's connection list.
Open the Connection Tracker to see which connections need to be updated.
D2L does not yet support OAuth 2. Please contact D2L for more information about their plans for transitioning to OAuth 2.
Converge
This vendor has not shared their currently supported version with Infinite Campus. Please contact Converge for more information about their plans for transitioning to OAuth 2.
eDoctrina
eDoctrina does not yet support OAuth 2. Please contact eDoctrina for more information about their plans for transitioning to OAuth 2.
GG4L
Support for OAuth 2 is in place for GG4L. Contact GG4L for more information about migrating to OAuth 2.
Google Classroom
Support for OAuth 2 is in place for Google Classroom. Update credentials in the admin workflow in Google, but do NOT delete existing connections.
Instructure (Kimono and Canvas)
Support for OAuth 2 is in place for Kimono and Canvas. Create a support case with the partner(s) your district uses to manage the transition from OAuth 1 to OAuth 2.
ItsLearning
Support for OAuth 2 is in place for ItsLearning. District users can update their connections via the Imports Manager.
Naiku
Naiku does not yet support OAuth 2. Please contact Naiku for more information about their plans for transitioning to OAuth 2.
Otus
Otus supports OAuth 2. District users should work with Otus's Client Services team via a support request to enable OAuth 2.
SchoolCity
Please contact SchoolCity for more information about their plans for transitioning to OAuth 2.
Schoology
Schoology does not yet support OAuth 2. Please contact Schoology for more information about their plans for transitioning to OAuth 2.
Teams
Teams supports OAuth 2, but it must be enabled on the tenant level by Teams Support as of March 17th, 2022. District users should contact Teams Support for assistance.
Other Vendors
Infinite Campus has been in contact with all of our Digital Learning Partners and they have all committed to supporting OAuth 2 by the June 30, 2023 deadline. For vendors who are not members of the Infinite Campus Digital Learning Partner Program, contact the vendor for more information about how to update connections.
If a vendor does not support OAuth 2 by the deadline or if connections have not been updated, OneRoster connections will stop working.
The OneRoster and OAuth Versions are listed for each connection. 
button to view a list of all connections that have been updated. 
Open the Connection Tracker to see which connections need to be updated. 