Aeries SIS has developed an API based on the OneRoster® 1.1 specification. OneRoster is a standard for securely exchanging data between student information systems (SIS) and other applications such as Learning Management Systems (LMS). More information is available on the IMS Global website: http://www.imsglobal.org/activity/onerosterlis
By using the OneRoster standard, Aeries can ensure interoperability with other vendors that have implemented or will implement the same standard.
Note - The Aeries implementation of the OneRoster API does not support grade pass-back for Elementary Schools without a Master Schedule.
Aeries Public Demo
Note: The steps described in this article can only be completed by an Aeries Administrator.
Giving a vendor access to the Aeries OneRoster API is simple. Before you begin, create an entry for the vendor on the Security | API Security page. Instructions can be found in the API Security article.
After an entry for the vendor has been created, continue to work in the Security | API Security page. First, select the vendor created. You will see Product Information listed for that vendor as shown below.
The OneRoster URL can be changed by accessing School Options at the District level.
Select Change on the API Security form then ensure the OneRoster check box is checked to enable the vendor to access the OneRoster API. After checking the box, click the Update button.
After updating, check the box labeled Display Consumer ID & Secret Keys for OneRoster.
Make note of the Consumer ID and Consumer Secret Key that display. The core security of the OneRoster API is different from that of the regular Aeries API. For OneRoster, the vendor will NOT use the Aeries Certificate, but will use the Consumer ID and Secret Key instead.
You will need to provide the 3rd party vendor with three pieces of information:
- Aeries URL: This is the base URL for your Aeries Web application. The website needs to be publicly accessible from outside your local network, it MUST be secured with a digital certificate (HTTPS), it MUST include a sub directory (https://demo.aeries.net/aeries/), and the server MUST support TLS 1.2. If you are uncertain of the base URL, simply browse to your Aeries login page, then copy everything before the last slash (“/”) in the browser’s address bar.
- Consumer ID: The string of letters and numbers, exactly as displayed on the API Security page. The vendor may also refer to this as the “Client ID”.
- Consumer Secret Key: The string of letters and numbers, exactly as displayed on the API Security page. The vendor may also refer to this as the “Client Secret”.
Note: If your Admin and Teacher Portals are not available externally or if they use Integrated Windows Authentication, then it is best to provide the URL of your Student Portal instead. The API works the same regardless of the portal type. In the example below, the Aeries URL is https://demo.aeries.net/aeries/. Make sure to note the case of the URL.
OneRoster API permissions are configured in the same way as permissions for the regular Aeries API. The following is a list of permissions that are needed for the complete set of OneRoster API endpoints that Aeries currently supports. More may be added in the future.
- Student Data
- Student Data
- Gradebook Scores
- Gradebook Category
- Gradebook Assignment
- Teacher Data
- Master Schedule
- Course Data
- School Information
Note: Aeries Hosted customers should contact Aeries Support to have this step verified if this is the first OneRoster connection created by the district to ensure that the correct certificate is selected and that the recycling of the Application Pool can be coordinated.
After completing the steps in the above section on API Security, navigate to the School Info | School Options page to see the OneRoster Settings section. While logged in at the District level, click the Edit/Change button to enter Edit mode. Check the box labeled Enable.
The following warning message will display. Click OK to continue.
Note: As the warning message indicates, these settings will not take effect until the Aeries application is restarted in IIS. This can be accomplished by recycling the Application Pool under which Aeries is running or by resetting IIS. This will terminate all active user sessions, which may result in lost work and therefore is recommended to be done outside regular hours.
Click OK to continue. The following options will display.
|Public URL||Enter the Aeries URL that you determined in a previous step.|
|Signing Certificate||Click the magnifying glass to display a list of available certificates stored on your web server. The Signing Certificate should be set to the valid root CA (Certificate Authority) for your installed SSL certificate.|
Note: Make sure to match the case of the Aeries URL exactly, as certain configurations may require this (e.g. https://aeries.mydistrict.org/aeries vs https://Aeries.MyDistrict.org/Aeries). Also, the Public URL must be a Virtual Directory.
There are additional options that apply to both the OneRoster API and the OneRoster CSV extract. Those options are detailed in the OneRoster v1.1 Configuration article here.