OAuth2

<a name="top"></a>

<a href="http://oauth.net/2" target="_blank">OAuth2</a> is a protocol designed to let third-party applications authenticate to perform actions as a user, without getting the user's password. Canvas uses OAuth2 (specifically <a href="http://tools.ietf.org/html/rfc6749" target="_blank">RFC-6749</a>) for authentication and authorization of the Canvas API. Additionally, Canvas uses OAuth2 for <a href="https://www.imsglobal.org/activity/learning-tools-interoperability" target="_blank">LTI Advantage</a> service authentication (as described in the <a href="https://www.imsglobal.org/spec/security/v1p0/" target="_blank">IMS Security Framework</a>). <a name="top"></a>

Accessing the Canvas API

• Storing Tokens
• Manual Token Generation
• Oauth2 Flow
  • Getting OAuth2 Client ID/Secret
  • Step 1: Redirect users to request Canvas access
  • Step 2: Redirect back to the request_uri, or out-of-band redirect
    • Note for native apps
  • Step 3: Exchange the code for the final access token
• Using an Access Token to authenticate requests
• Using a Refresh Token to get a new Access Token
• Logging Out
• Endpoints
  • GET login/oauth2/auth
  • POST login/oauth2/token
  • DELETE login/oauth2/token
  • GET login/session_token

Accessing LTI Advantage Services

• Step 1: Developer Key Setup
• Step 2: Request an Access Token
• Step 3: Use the access token to access LTI services

Accessing the Canvas API <a name="accessing-canvas-api"></a>

<small><a href="#top">Back to Top</a></small>

Storing Tokens <a name="storing-access-tokens"></a>

<small><a href="#top">Back to Top</a></small>

When appropriate, applications should store the token locally, rather than requesting a new token for the same user each time the user uses the application. If the token is deleted or expires, the application will get a 401 Unauthorized error from the API, in which case the application should perform the OAuth flow again to receive a new token. You can differentiate this 401 Unauthorized from other cases where the user simply does not have permission to access the resource by checking that the WWW-Authenticate header is set.

Storing a token is in many ways equivalent to storing the user's password, so tokens should be stored and used in a secure manner, including but not limited to:

• Don't embed tokens in web pages.
• Don't pass tokens or session IDs around in URLs.
• Properly secure the database or other data store containing the tokens.
• For web applications, practice proper techniques to avoid session attacks such as cross-site scripting, request forgery, replay attacks, etc.
• For native applications, take advantage of user keychain stores and other operating system functionality for securely storing passwords.

Manual Token Generation<a name="manual-token-generation"></a>

<small><a href="#top">Back to Top</a></small>

For testing your application before you've implemented OAuth, the simplest option is to generate an access token on your user's profile page. Note that asking any other user to manually generate a token and enter it into your application is a violation of <a href="https://www.instructure.com/policies/api-policy">Canvas' API Policy</a>. Applications in use by multiple users <b>MUST</b> use OAuth to obtain tokens.

To manually generate a token for testing:

1. Click the "profile" link in the top right menu bar, or navigate to /profile
2. Under the "Approved Integrations" section, click the button to generate a new access token.
3. Once the token is generated, you cannot view it again, and you'll have to generate a new token if you forget it. Remember that access tokens are password equivalent, so keep it secret.

Oauth2 Flow <a name="oauth2-flow"></a>

<small><a href="#top">Back to Top</a></small>

Your application can rely on canvas for a user's identity. During step 1 of the web application flow below, specify the optional scope parameter as scope=/auth/userinfo. When the user is asked to grant your application access in step 2 of the web application flow, they will also be given an option to remember their authorization. If they grant access and remember the authorization, Canvas will skip step 2 of the request flow for future requests.

Canvas will not give a token back as part of a userinfo request. It will only provide the current user's name and id.

Getting OAuth2 Client ID/Secret <a name="oauth2-flow-0"></a>

If your application will be used by others, you will need to implement the full OAuth2 token request workflow, so that you can request an access token for each user of your application.

Performing the OAuth2 token request flow requires an application client ID and client secret. To obtain these application credentials, you will need to register your application. The client secret should never be shared.

For Canvas Cloud (hosted by Instructure), developer keys are <a href="https://community.canvaslms.com/t5/Admin-Guide/How-do-I-manage-developer-keys-for-an-account/ta-p/249" target="_blank">issued by the admin of the institution</a>.

<b>NOTE for LTI providers:</b> Since developer keys are scoped to the institution they are issued from, tool providers that serve multiple institutions should store and look up the correct developer key based on the launch parameters (eg. custom_canvas_api_domain) sent during the LTI launch.

For <a href="https://github.com/instructure/canvas-lms/wiki" target="_blank">open source Canvas users</a>, you can <a href="https://community.canvaslms.com/t5/Admin-Guide/How-do-I-manage-developer-keys-for-an-account/ta-p/249" target="_blank">generate a client ID</a> and secret in the Site Admin account of your Canvas install.

Step 1: Redirect users to request Canvas access <a name="oauth2-flow-1"></a>

<small><a href="#top">Back to Top</a></small>

A basic request looks like:

See GET login/oauth2/auth for details.

Step 2: Redirect back to the request_uri, or out-of-band redirect <a name="oauth2-flow-2"></a>

<small><a href="#top">Back to Top</a></small>

If the user accepts your request, Canvas redirects back to your request_uri with a specific query string, containing the OAuth2 response:

The app can then extract the code, and use it along with the client_id and client_secret to obtain the final access_key.

If your application passed a state parameter in step 1, it will be returned here in step 2 so that your app can tie the request and response together, whether the response was successful or an error occurred.

If the user doesn't accept the request for access, or if another error occurs, Canvas redirects back to your request_uri with an error parameter, rather than a code parameter, in the query string.

A list of possible error codes is found in the RFC-7649 spec.

Note for native apps <a name="oauth2-flow-2.1"></a>

<small><a href="#top">Back to Top</a></small>

Canvas redirects to a page on canvas with a specific query string, containing parameters from the OAuth2 response:

At this point the app should notice that the URL of the webview has changed to contain <code>code=<code></code> somewhere in the query string. The app can then extract the code, and use it along with the client_id and client_secret to obtain the final access_key.

Step 3: Exchange the code for the final access token <a name="oauth2-flow-3"></a>

<small><a href="#top">Back to Top</a></small>

To get a new access token and refresh token, send a POST request to login/oauth2/token with the following parameters:

Note that the once the code issued in step 2 is used in a POST request to this endpoint, it is invalidated and further requests for tokens with the same code will fail.

Using an Access Token to authenticate requests <a name="using-access-tokens"></a>

<small><a href="#top">Back to Top</a></small>

Once you have an OAuth access token, you can use it to make API requests. If possible, using the HTTP Authorization header is recommended.

OAuth2 Token sent in header:

curl -H "Authorization: Bearer <ACCESS-TOKEN>" "https://canvas.instructure.com/api/v1/courses"

Sending the access token in the query string or POST parameters is also supported, but discouraged as it increases the chances of the token being logged or leaked in transit.

OAuth2 Token sent in query string:

curl "https://canvas.instructure.com/api/v1/courses?access_token=<ACCESS-TOKEN>"

Using a Refresh Token to get a new Access Token <a name="using-refresh-tokens"></a>

<small><a href="#top">Back to Top</a></small>

Access tokens have a 1 hour lifespan. When the refresh flow is taken, Canvas will update the access token to a new value, reset the expiration timer, and return the new access token as part of the response. When refreshing tokens the user will not be asked to authorize the application again.

To refresh the access token, send a POST request to login/oauth2/token with the following parameters:

The response to this request will not contain a new refresh token; the same refresh token is to be reused.

Logging Out

<small><a href="#top">Back to Top</a></small>

To logout, simply send a DELETE request to login/oauth2/token

Accessing LTI Advantage Services <a name="accessing-lti-advantage-services-link"></a>

<small><a href="#top">Back to Top</a></small>

Step 1: Developer Key Setup <a name="developer-key-setup"></a>

<small><a href="#top">Back to Top</a></small>

Step 2: Request an access token <a name="request-access-token"></a>

<small><a href="#top">Back to Top</a></small>

Step 3: Use the access token to access LTI services <a name="use-access-token"></a>

<small><a href="#top">Back to Top</a></small>

Once you have an access token, you can use it to make LTI service requests. The access token must be included as a Bearer token in the Authorization header:

curl -H "Authorization: Bearer <ACCESS-TOKEN>" "https://<canvas_domain>/api/lti/courses/:course_id/names_and_roles"

The following endpoints are currently supported:

Names and Role Provisioning Services

• <a href="names_and_role.html" target="_blank">Names and Role API</a>

Assignment and Grade Services

• <a href="line_items.html" target="_blank">Line Items</a>
• <a href="score.html" target="_blank">Score</a>
• <a href="result.html" target="_blank">Result</a>