ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos in LTI dev key documentation 

Closes PLAT-5149
flag=none

Test plan:
- browse markdown file on gerrit and observe that changes are correct

Change-Id: I0844bfa4f2dd20324ae98f469f3ddd0a536f7b8d
Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/219503
Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
Tested-by: Jenkins
Reviewed-by: Xander Moffatt <xmoffatt@instructure.com>
QA-Review: Xander Moffatt <xmoffatt@instructure.com>
Product-Review: Jesse Poulos <jpoulos@instructure.com>
This commit is contained in:
Evan Battaglia 2019-12-04 18:22:03 -07:00
parent 21b9d5bab1
commit a72170bac7
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/api/lti_dev_key_config.md
View File

@ -30,7 +30,7 @@ The <a href="http://www.imsglobal.org/spec/security/v1p0/" target="_blank">IMS S
- https://canvas.instructure.com (Production environment launches)
- https://canvas.beta.instructure.com (Beta environment launches)
- https://canvas.beta.instructure.com (Test environment launches)
- https://canvas.test.instructure.com (Test environment launches)
The request also includes a `login_hint` that is passed in the next step. Last, the request include the `target_link_uri` that has been configured on the Developer key; this is later used by the tool as a recommended final redirect.
@ -38,9 +38,9 @@ The <a href="http://www.imsglobal.org/spec/security/v1p0/" target="_blank">IMS S
###Step 2: Authentication Response
To complete authentication, tools are expected to send back an <a href="http://www.imsglobal.org/spec/security/v1p0/#step-2-authentication-request" target="_blank">authentication response</a> to an "OIDC Authorization end-point". This can be a GET or POST. For cloud-hosted Canvas, regardless of the domain used by the client, the endpoint is always:
- `https://canvas.instructure.com/api/lti/authorization_redirect` (if launched from a **production** environment)
- `https://canvas.beta.instructure.com/api/lti/authorization_redirect` (if launched from a **beta** environment)
- `https://canvas.test.instructure.com/api/lti/authorization_redirect` (if launched from a **test** environment)
- `https://canvas.instructure.com/api/lti/authorize_redirect` (if launched from a **production** environment)
- `https://canvas.beta.instructure.com/api/lti/authorize_redirect` (if launched from a **beta** environment)
- `https://canvas.test.instructure.com/api/lti/authorize_redirect` (if launched from a **test** environment)
Among the <a href="<a href="http://www.imsglobal.org/spec/security/v1p0/#step-2-authentication-request" target="_blank">required variables</a> the request should include: