Info |
---|
This is a DRAFT. This is going to be the main document, which can then be turned into slides for a presentation |
1 LMOD Introduction
Note |
---|
TODO Joe |
2 Authentication/Authorization
...
The other way to authenticate a user to Touchstone in a web app is using cross-origin AJAX requests. The web page served by the application tells the user's browser to contact the API directly via AJAX. This requires that LMOD's servers white-list the consuming application for cross-origin requests. The AJAX requests need to set the withCredentials flag to true. Additionally, the application may need to get the user to authenticate to Touchstone and then redirect back to the application. We support this by providing a login redirector. Say the app is located at https://google.com. Then the url https://mv-ezproxy-com.ezproxyberklee.flo.org/Shibboleth.sso/Login?target=%2Fcrossdomain%2Floginredirect%3Fhttps%253A%252F%252Fgoogle.com will authenticate the user to learning modules and redirect them back to google.com (note that "https://google.com" has been percent-encoded twice to make it the authentication and cross-domain redirects. We have used this method inside our student dashboard code.
2.2.2 Application Certificate
...
2.3 Roles and Authorization
The
Note |
---|
TODO Joe |
3 External Data Feeds
Note |
---|
TODO Qing |
4 LMOD APIs
4.1 Membership API
Note |
---|
TODO Qing |
4.1.1 Example
4.1.2 Intended Use Cases
...
4.1.4 Full Documentation link
4.2 Course Guide API
Note |
---|
TODO Qing |
4.2.1 Example
4.2.2 Intended Use Cases
...
4.2.4 Full Documentation link
4.3 Gradebook API
Note |
---|
TODO Robin |
4.3.1 Example
4.3.2 Intended Use Cases
...
4.3.4 Full Documentation link
4.4 Calendar API
Note |
---|
TODO Joe |
4.4.1 Example
4.4.2 Intended Use Cases
...
4.4.4 Full Documentation link
4.5 Materials API
Note |
---|
TODO Ajay |
4.5.1 Example
4.5.2 Intended Use Cases
...
4.5.4 Full Documentation link
4.6 Forum/Announcement API
Note |
---|
TODO Joe |
4.6.1 Example
4.6.2 Intended Use Cases
...