You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/lti13/getting-started.md
+7-14Lines changed: 7 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,8 @@ Start by navigating to your [LMS vendor's integration section](lms-integration.m
7
7
During the tool registration process, you should obtain the following information which is necessary to complete the setup of the LTI Authenticator plugin:
8
8
9
9
-`issuer`: URL of the LMS platform used for identification
10
-
-`client_id`: opaque ID of the tool registration at the platform
10
+
-`client_id`: opaque ID of the tool registration at the platform.
11
+
You may obtain multiple client IDs, e.g. if you do multiple [single-tenant registrations](https://www.imsglobal.org/spec/lti/v1p3#single-tenant-tool-registered-and-deployed-once) within your LMS with the same JupyterHub instance.
11
12
12
13
```{note}
13
14
If your LMS is not listed feel free to send us a PR with instructions for this new LMS.
@@ -21,14 +22,13 @@ See the [configuration reference](reference) for a complete list of available co
21
22
The required settings to get authentication via LTI 1.3 to work are:
22
23
23
24
-`issuer`: the URL of your LMS platform. If your LMS is served from `https://canvas.instructure.com`, the issuer is `https://canvas.instructure.com`.
24
-
-`client_id`: opaque ID, typically generated by the LMS when a tool is registered there.
25
-
You can specify either a single client ID or a set of client IDs, e.g. if you do multiple [single-tenant registrations](https://www.imsglobal.org/spec/lti/v1p3#single-tenant-tool-registered-and-deployed-once) within your LMS with the same JupyterHub instance.
25
+
-`client_id`: set or list of opaque IDs, typically generated by the LMS when a tool is registered there.
26
26
-`authorize_url`: Authorization endpoint of the LMS platform. The URL to which authorization requests are sent by the authenticator as part of the [OIDC implicit flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/implicit-flow-with-form-post).
27
27
E.g. `https://canvas.instructure.com/api/lti/authorize_redirect`.
28
28
-`jwks_endpoint`: An endpoint of the LMS from which JupyterHub can obtain the [JWKS](https://auth0.com/docs/secure/tokens/json-web-tokens/json-web-key-sets) to verify and decode any received [JWT](https://auth0.com/docs/secure/tokens/json-web-tokens).
29
29
E.g. `https://canvas.instructure.com/api/lti/security/jwks`.
30
30
31
-
A valid minimal configuration in the `jupyterhub_config,py` may look like this
31
+
A valid minimal configuration in the `jupyterhub_config.py` may look like this
Copy file name to clipboardExpand all lines: docs/source/lti13/reference.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ hub:
28
28
| tool_description | No | Description of the tool within the config JSON | `"Launch interactive Jupyter Notebooks with JupyterHub"` |
29
29
| username_key | No | The LTI 1.3 launch parameter that contains the JupyterHub username value | `"email"` |
30
30
| issuer | Yes | The platform's issuer identifier. A case-sensitive URL provided by the platform | |
31
-
| client_id | Yes | The client ID or a list of client IDs identifying the JuyterHub within the LMS platform. Must contain the client IDs created when registering the tool on the LMS platform. Possible values are of type `str` or `set[str]`. | |
31
+
| client_id | Yes | List or set of client IDs identifying the JuyterHub within the LMS platform. Must contain the client IDs created when registering the tool on the LMS platform. Possible values are of type `list[str]` or `set[str]`. | |
32
32
| authorize_url | Yes | Authorization end-point of the platform's identity provider. Provided by the platform. | |
33
33
| jwks_endpoint | Yes | Platform's jwks endpoint. Provided by the platform | |
34
34
| jwks_algorithms | No | List of supported signature methods | `["RS256"]` |
0 commit comments